Oracle ZFS Storage Appliance: How to Setup an Initial Replication From Source to Target Via a Common NFS Mount

Asset ID:	1-71-2120655.1
Update Date:	2017-03-05
Keywords:

Solution Type Technical Instruction Sure

Solution 2120655.1 : Oracle ZFS Storage Appliance: How to Setup an Initial Replication From Source to Target Via a Common NFS Mount

Applies to:

Sun ZFS Storage 7120 - Version All Versions and later
Sun ZFS Storage 7420 - Version All Versions and later
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
7000 Appliance OS (Fishworks)

Goal

The release of 2013.06.05.4.X code, introduced the ability to perform initial replications over NFS. This new feature streamlines the initial replication process by dramatically reducing the amount of time to copy the data.

This document provides a working example of how to configure and run an initial replication over NFS.

Solution

You start off just like you would any other replication - by identifying the target system you will eventually replicate to.

7320-source:> configuration services replication targets target
7320-source:configuration services replication target (uncommitted)> set hostname=192.168.10.15
hostname = 192.168.10.15 (uncommitted)
7320-source:configuration services replication target (uncommitted)> set label=7320-target
label = 7320-target (uncommitted)
7320-source:configuration services replication target (uncommitted)> set root_password=*********
root_password = ********* (uncommitted)
7320-source:configuration services replication target (uncommitted)> commit

Before the replication action can be created, you must set up an NFS server that both the source and target system can access.

It is important to note that the typical roles are now reversed. The ZFS appliance is an NFS client and the staging system is the NFS server.

In this example, the staging system is booting Solaris 11. The applicable edits are made to the dfstab file and the NFS server "service" is started ;

root@t2000# cat /etc/dfs/dfstab
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
# .e.g,
# share -F nfs -o rw=engineering -d "home dirs" /export/home2
share -F nfs -o rw /migrate

root@t2000# svcs svc:/network/nfs/server:default
STATE STIME FMRI
disabled 14:31:54 svc:/network/nfs/server:default

root@t2000# svcadm enable svc:/network/nfs/server:default

root@t2000-bur09-f# svcs svc:/network/nfs/server:default
STATE STIME FMRI
online 12:13:17 svc:/network/nfs/server:default

You can now stage (or export) your project out to the NFS Server. From the BUI, you will set up the export.

setup-export1

NOTE: The parameter 'use_ssl' in the action MUST be disabled - it is enabled by default.

After setting up the export, the pending action is available to send an update.

setup-export2

You can also see this in the CLI :

7320-source:> shares select Dbase replication select action-000
7320-source:shares Dbase action-000> show
Properties:
id = 2bf4d2fd-f337-4ee4-e1a2-b9246d68f936
target = 7320-target
enabled = true
continuous = false
include_snaps = true
max_bandwidth = unlimited
bytes_sent = 0
estimated_size = 0
estimated_time_left = 00:00:00
average_throughput = 0B/s
use_ssl = false
compression = on
export_path = nfs://10.152.224.202/migrate
state = idle
state_description = Idle (export pending)
export_pending = true
offline = false
next_update = Export replication data

A sendupdate is now run. You will see the following file hierarchy created on the staging NFS server :

root@t2000# cd /migrate/rr_updates/6d30424c-6819-ed59-ca78-a8db115d5f5b
root@t2000# ls -l
total 274598
-rw-r--r-- 1 root root 631 Mar 25 13:54 metadata.xml
-rw------- 1 root root 140432737 Mar 25 13:55 stream
-rw------- 1 root root 33 Mar 25 13:55 stream.md5

The BUI on the source 7320 will tell you the export has completed

export-complete

You can now move over to the target system and import your replicated data. From the BUI, you can configure the package for import.

import_package

Similarly, you can import the package from the CLI :

7320-target:shares replication select source-000 select package-000>
7320-target:shares replication source-000 package-001>set import_path=nfs://10.152.224.202/migrate
import_path = nfs://10.152.224.202/migrate (uncommitted)
7320-target:shares replication source-000 package-001> commit
7320-target:shares replication source-000 package-001> show
Properties:
id = 3a5d6b24-2a20-e147-b76e-ab867dec445c
enabled = true
state = receiving
state_description = Importing update
offline = true
import_path = nfs://10.152.224.202/migrate
last_sync = unknown
last_try = unknown
last_result = unknown

This initial replication over NFS is a "one time" configuration. Once the replicated data is imported to the target, the export path is removed from the source.

Any subsequent update is sent (either by scheduled or continuous updates), over the traditional network connection.

Attachments

This solution has no attachment