SuperCluster DR Procedure for App Zones

NOTE: This is a procedure for testing failing over from one SuperCluster to another at a different site - not for the occurrence of an actual DR situation.

This doc is a work in progress - process is still a bit finicky

Pre-work

i) Set up zfs replication isci zone lun and nfs shares

ii) Make sure zone root zpool has different name on source and destination system

iii) Add same IB IP as zfs-sa at source to zfs-sa at destination

iv) Set up key authentication to zfs-sa at destination
v) Create script at source to periodically save zone configs

1. Snap ZFS pool

2. Snap zfs project/shares

3. Share zpool lun

On DR:

a. Create a project to put your clones under

b. List the snapshots on the zpool lun

c. Create the clone off the appropriate snap

4. Share zfs projects/shares

Do this in the GUI, for each project:

- click on Shares

- underneath Shares click on Projects

- underneath Projects click on Replica

- move the mouse over the relevant project and a pencil and trash bin icon will show on the right, click on the pencil

- Click on Replication

- below Replication should be a bunch of icons

- click on the + icon ("Clone most recently received project snapshot")

-  You might get an error at this point. Just try again and again.

- When you get to the screen asking for new project name, use the current project name and add "_DR" and click on Continue.

Or in an actual DR situation:

Instead of the + icon, you break replication. Afterwards you will need to reverse replication before failing back.

5. Import zpool

On destination server:

cfgadm -alv

devfsadm -Cv

zpool import -R / zones

6. Recreate zone

Configure zones

Attach zones

Boot zones