text
stringlengths 65
20k
|
|---|
See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist. |
It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers . |
It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer. |
Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers . |
The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers. |
During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint . |
Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances. |
Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management . |
If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page. |
Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management . |
See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths. |
Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet. |
Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy. |
A public regional subnet in the VCN, with an associated security list and a route table.Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time. |
Set Up the Disaster Recovery Solution for File Server Perform the following one-time configuration tasks to setup the disaster recovery solution for File Server: 1.Create load balancers in the two OCI regions where your Oracle Integration instances exist.See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP. |
See Create Load Balancers .2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region. |
2.Configure a separate custom hostname for each load balancer.See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values. |
See Configure Custom Hostnames for Load Balancers .3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol. |
3.Configure a common custom endpoint for both the load balancers.See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic. |
See Configure a Common Custom Endpoint .Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file. |
Create Load Balancers Create a public load balancer in both primary and secondary OCI regions to direct traffic to your File Server instances.For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file. |
For more information on load balancer prerequisites, see Load Balancer Management .To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group. |
To create a load balancer: 1.Log in to your Oracle Cloud Infrastructure Console, and select the required region from the Regions drop-down list at the top of the page.2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group. |
2.For the full list of tasks to create a load balancer, see Load Balancer Management .The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period. |
The following steps list the important configurations: a.On the Add Details page of the Create Load Balancer dialog: i.Leave Public and Ephemeral IP Address selected in the visibility type and IP address sections, respectively.Chapter 4 Prerequisites 4-3ii.In the Bandwidth section, choose the required bandwidths.iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit . |
iii.In the Choose Networking section, select the appropriate VCN and subnet.b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page. |
b.On the Choose Backends page, specify the details for the backend set: i.Select the required load balancing policy.ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer. |
ii.Do not add a backend at this time.iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management . |
iii.In the Specify Health Check Policy section: i.In the Protocol field, select TCP.ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it. |
ii.In the Port field, enter the port number of the File Server instance corresponding to the region.iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets . |
iii.Enter the required interval, timeout, and retry values.c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page. |
c.On the Configure Listener page: i.Select TCP as the protocol.ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it. |
ii.Enter 22 as the port on which to listen for incoming traffic.d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left. |
d.On the Manage Logging page: i.Select the compartment in which you want to store the log file.ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends . |
ii.Select the log group in which to store the log file.You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option. |
You can either select the default log group or create a new log group.If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region. |
If you choose to create a new group, enter a name and description for the group.iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add. |
iii.Enter a name for the log file, and choose a retention period.iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record. |
iv.Click Submit .After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required. |
After the system provisions the load balancer, the load balancer record appears on the page.3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions. |
3.Add the IP address of the File Server as a backend to the load balancer.For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider. |
For complete details, see Backend Server Management .a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance. |
a.On the Load Balancers page, click the name of the load balancer record to open it.b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone. |
b.On the Load Balancer Details page, scroll down to the Resources section, and click Backend Sets .The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API. |
The backend set you configured while creating the load balancer is listed on the page.c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it. |
c.Click the name of the backend set to open it.d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers. |
d.On the Backend Set Details page, click Backends in the Resources section on the left.e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance. |
e.Click Add Backends .f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address. |
f.In the Add Backends dialog: i.Select the IP Addresses option.ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain. |
ii.Enter the IP address and port number of the File Server instance corresponding to the region.iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance. |
iii.Click Add.After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances. |
After the load balancer is updated, test your sFTP connection using the load balancers IP address and port number (22).Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-4Note: A Warning indicator may be displayed in the Overall Health field of the load balancer record.If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background. |
If youve already tested the connection, no further action is required.Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider. |
Configure Custom Hostnames for Load Balancers Configure a separate custom hostname for both the load balancer instances, created in your primary and secondary OCI regions.To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target. |
To configure a hostname for a load balancer: 1.Choose a custom hostname for a load balancer instance and register it with a DNS provider.2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API. |
2.After you've acquired a domain, create a DNS record for the load balancer instance.You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers. |
You can create and manage DNS records using an OCI DNS zone.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region. |
a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME. |
See Managing DNS Service Zones for details on creating an OCI DNS zone and adding a record to it.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region. |
b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region. |
c.Add a record in the OCI DNS zone for the corresponding load balancer instance.Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint. |
Enter the following details: Record Type : A IPv4 Address.Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially. |
Name : Optionally, enter a subdomain.Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region. |
Address : Enter the IP address of the corresponding load balancer instance.Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice. |
Configure a Common Custom Endpoint Configure a common custom endpoint for your load balancer instances.A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances. |
A common custom endpoint ensures that applications and users can access File Server with the same URL regardless of which instance is active in the background.To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary. |
To configure a common custom endpoint: 1.Choose a parent custom endpoint for your load balancers and register it with a DNS provider.2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD. |
2.After you've acquired a domain, create a DNS record with the load balancer instance in the primary OCI region as the target.a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized. |
a.Add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub. |
b.After you've created a zone, update your domain to use the OCI DNS nameservers.c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use. |
c.Add a record in the OCI DNS zone for the load balancer instance in the primary OCI region.Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure. |
Enter the following details: Record Type : CNAME.Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants. |
Name : Optionally, enter a subdomain.Chapter 4 Set Up the Disaster Recovery Solution for File Server 4-5Target : Enter the custom hostname of the load balancer instance in the primary OCI region.3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates. |
3.During a failover, update the CNAME record with the custom hostname of the load balancer instance in the secondary OCI region.Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service. |
Note: Using a separate custom hostname for each load balancer makes it easier to identify which load balancer is being used by the final custom endpoint.However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers. |
However, if you do not want to create parent-child custom hostnames for load balancers, you can create one custom hostname and add a DNS A-Record for the load balancer instance in the primary OCI region initially.During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages. |
During a failover, you can update the A-Record with the IP address of the load balancer instance in the secondary OCI region.You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider). |
You can also create and manage DNS records for your DR setup at a DNS provider of your choice.Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts. |
Perform Post-Configuration Tasks Learn how to regularly synchronize data between your File Server instances.After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates. |
After the DR system is setup, you must regularly synchronize data between your File Server instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. |
Automate Metadata Synchronization Monitor Your Instances Automate Metadata Synchronization Keep the user and folder data synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. |
You can use Jenkins or a similar tool to implement CICD for your instances and have the data synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. |
You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. |
See File Server REST Endpoints in REST API for File Server in Oracle Integration Generation 2 for the REST APIs to use.Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing. |
Before you begin the data synchronization, you must perform the following tasks in the secondary File Server instance, either manually or using a script: Replicate the primary instances file structure.Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. |
Replicate the primary instances permission grants.Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. |
Upload all necessary certificates.Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. |
Monitor Your Instances Regularly monitor the health of your active File Server instances.Chapter 4 Perform Post-Configuration Tasks 4-6You can use the OCI health check service or a third-party monitoring service.Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government. |
Additionally, you can define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications. |
Execute Failover Tasks Switch from your primary instance to the standby instance during outages.During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. |
During outages, you can switch from your primary instance to the standby instance by updating the DNS record of the parent or common custom endpoint in the OCI DNS zone (or at your DNS provider).The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. |
The traffic routes to the secondary File Server instance and file replication starts.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. |
After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Chapter 4 Execute Failover Tasks 4-7Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2 E85503-11 December 2022 Oracle Cloud Using the Google Tasks Adapter with Oracle Integration Generation 2, E85503-11 Copyright 2019, 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. |
Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners. |
Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. |
Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. |
The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group. |
If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties. |
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. |
As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience iv Documentation Accessibility iv Diversity and Inclusion iv Related Resources v Conventions v 1 Understand the Google Tasks Adapter Google Tasks Adapter Capabilities 1-1 What Application Version Is Supported? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.