Configuring Remote Replication With Oracle ZFS Storage Appliance Software

Language:

This section describes the steps you must perform before you can configure Oracle ZFS Storage Appliance remote replication with Geographic Edition software. The following procedures are in this section:

How to Create a Role and Associated User for the Primary and Secondary Appliances

If a role and associated user do not yet exist on the source and target appliances, perform this procedure to create them.

Log in to the Oracle ZFS Storage appliance.

Create a role for remote replication.
Configure the role with the following permissions:
- Object nas.*.*.* with permissions clone, destroy, rrsource, rrtarget, createShare, and createProject.
- Object workflow.*.* with permission read.

Create a user for replication that is associated with the role you created in Step 2.

How to Create a Project and Enable Replication for the Project

Log in to the Oracle ZFS Storage appliance on the primary cluster-paris site.
Navigate to Shares > Projects and create the projects that you need for your application.
In each project, create the file systems and LUNs that you need for your application.
Ensure that NFS exceptions and LUN settings are identical on the primary and secondary storage appliances. For more information, see Copying and Editing Actions in Oracle ZFS Storage 7000 System Administration Guide (http://docs.oracle.com/cd/E26765_01/html/E26397/).
For iSCSI LUNs, if you use nondefault targets and target groups, ensure that target groups and initiator groups used by LUNs within the project also exist on the replication target.
These groups must use the same name in the replication target as in the source appliance.

For more information on replicating projects with iSCSI LUNs, see iSCSI Configurations and Replication in Oracle ZFS Storage Appliance Administration Guide (http://docs.oracle.com/cd/E71909_01/html/E71919/goksk.html)
For each project, navigate to Replication, create an action, and enable the action with continuous mode.

Troubleshooting

If you need to stop Oracle ZFS Storage Appliance replication directly from the Oracle ZFS Storage appliance, you must perform the following tasks in the order shown:

Set continuous=false.
Wait for the update to complete.
Set enabled=false to stop replication.

Geographic Edition requires that last_result of replication be a success. Otherwise, adding a project to a Geographic Edition protection group and protection group validation will fail.

How to Configure Oracle Solaris Cluster Resources on the Primary Cluster

This procedure creates Oracle Solaris Cluster resources on the primary cluster for the application to be protected.

Before You Begin

Ensure that the following tasks are completed on the storage appliance:

Replication peers are configured by the storage administrator.
Projects are configured by the storage administrator.
Replication is enabled for the project.
For iSCSI LUNs, if you use nondefault target groups, the target groups and initiator groups used by LUNs within the project also exist on the replication target. In addition, these groups use the same names in the replication target as in the source appliance.
If you use file systems, NFS Exceptions exist for all nodes of both clusters. This ensures that either cluster can access the file systems when that cluster has the primary role.

Create the Oracle Solaris Cluster device groups, file systems, or ZFS storage pools you want to use.
Specify the LUNs or file systems in the Oracle ZFS Storage appliance to be replicated.

For information about creating device groups, file systems, and ZFS storage pools in a cluster configuration, see Oracle Solaris Cluster System Administration Guide.
Create an HAStoragePlus resource or a scalable mount-point resource for the device group, file system, or ZFS storage pool you use.
This resource manages bringing online the Oracle ZFS Storage Appliance storage on both the primary and secondary clusters.

For information about creating an HAStoragePlus or scalable mount-point resource, see Oracle Solaris Cluster Data Services Planning and Administration Guide.

How to Configure Oracle Solaris Cluster Resources on the Secondary Cluster

This procedure creates Oracle Solaris Cluster resources on the secondary cluster for the application to be protected.

Before You Begin

Ensure that the following tasks are completed on the storage appliance:

Replication peers are configured by the storage administrator.
Projects are configured by the storage administrator.
Replication is enabled for the project.
For iSCSI LUNs, if you use nondefault target groups, the target groups and initiator groups used by LUNs within the project also exist on the replication target. In addition, these groups must use the same names in the replication target as in the source appliance.
If you use file systems, NFS Exceptions exist for all nodes of both clusters. This ensures that either cluster can access the file systems when that cluster has the primary role.

On one node of the cluster-newyork (partner) site, create the application group.
The Auto_start_on_new_cluster property must be set to False.
```
phys-newyork-1# clresourcegroup create -p Auto_start_on_new_cluster=False \
application-resource-group
```
Determine whether the replicated project contains any LUNs.
1. On the cluster-paris (primary) site, access the Oracle ZFS Storage Appliance browser user interface (BUI).
2. Navigate to Shares > Projects and select the project being replicated.
If the project contains only file systems, perform the following tasks.
If the project contains any LUNs, skip to Step 4.
1. If replication is not in continuous mode, select Replication for the project and click Update Now or Sync Now.
  This executes a manual replication to synchronize the two sites.
2. On the cluster-newyork (partner) site, access the appliance BUI.
3. Navigate to In Projects > Replica and select the project being replicated.
4. Select Replication for the project and click Clone Most Recently Received Project Snapshot.
  Enter the same project name as on the primary appliance.

If the replicated project contains LUNS, perform the following tasks.
1. Create protection group and add replicated project and resource groups to it.
  See How to Create and Configure an Oracle ZFS Storage Appliance Protection Group.
  
  Note - Resource groups added to the protection group can be empty on the secondary cluster. The storage and application resources will be created on the secondary cluster in subsequent steps.
2. From one node of either cluster, start the protection group globally.
```
# geopg start -e global protection-group
```
3. From one node of either cluster, switch over the protection group to the secondary cluster.
```
# geopg switchover -f -m cluster-newyork protection-group
```
  The project is made local on the secondary storage.
4. On secondary cluster, map iSCSI devices from the project on the secondary storage.
  1. Map the iSCSI devices to the corresponding DID numbers.
  2. Use the cldevice list command to find devices corresponding to the devices being exported from the appliance.
5. Create the Oracle Solaris Cluster device groups or import the ZFS storage pools on the LUNs in the project.
  Specify the LUNs or file systems in the project that is now local on the secondary appliance.
  
  For information about creating device groups and file systems and adding ZFS storage pools in a cluster configuration, see Oracle Solaris Cluster System Administration Guide.
On cluster-newyork, create an HAStoragePlus resource or a scalable mount-point resource for the device group, file system, or ZFS storage pool you use.
This resource manages bringing online the Oracle ZFS Storage Appliance storage on the secondary cluster.

For information about creating an HAStoragePlus or scalable mount-point resource, see Oracle Solaris Cluster Data Services Planning and Administration Guide.
Bring up the application on cluster-newyork that uses the replicated storage and create corresponding cluster resources.
On cluster-newyork, confirm that the application resource group is correctly configured by bringing it online.
```
phys-newyork-1# clresourcegroup online -emM application-resource-group
```
If the replication project contains only file systems, perform the following tasks.
If the project contains any LUNs, skip to Step 9.
1. On a node of the secondary cluster, put the application resource group in the unmanaged state on secondary cluster.
```
phys-newyork-1# clresource disable -g application-resource-group +
phys-newyork-1# clresourcegroup offline application-resource-group
phys-newyork-1# clresourcegroup unmanage application-resource-group
```
2. If you created a file system and it is mounted, unmount the file system.
```
phys-newyork-1# umount /mounts/file-system
```
3. If the Oracle Solaris Cluster device group is online, take it offline.
```
phys-newyork-1# cldevicegroup offline raw-disk-group
```
4. Destroy the clone on the Oracle ZFS Storage appliance.
  1. Access the appliance BUI on the cluster-newyork site.
  2. Navigate to Shares > Projects and select the project that is cloned.
  3. Select Remove or Destroy entry for the cloned project.

If the replicated project contains any LUNs, from one node of either cluster, switch over the protection group to the primary cluster.
This step takes offline the configuration on the secondary cluster and brings it online on the primary cluster.
```
# geopg switchover -f -m cluster-paris protection-group
```

Next Steps

If the replicated project contains any LUNs, initial configuration on the primary and secondary clusters is now complete.
If the replicated project contains only file systems, go to How to Create and Configure an Oracle ZFS Storage Appliance Protection Group.