This section describes the preparations that are required for backing up and restoring ZFS storage pools.
For details on each procedure and a setup required in advance for using AdvancedCopy Manager, refer to "Chapter 6 Replication" and the "ETERNUS SF Operation Guide for Copy Control Module".
Whereas this document states some typical methods for controlling ZFS for your reference, refer to the operating system manuals for more details on usage.
Point
Below examples of command execution are based on the configurations described for replication operations and AdvancedCopy Manager CCM operations in "G.2.2 System configuration". Adapt any real control actions to your actual configuration.
Implement the following procedures for preparation:
Fetching lists of devices in transaction storage pools
On the business servers, check the devices that constitute the transaction storage pools to be backed up.
[Example]
Check the disk information of the storage pool. In below example, storage pool (STP1) consists of 1 physical disk (c1t1d1).
# zpool status STP1
pool: STP1
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
STP1 ONLINE 0 0 0
c1t1d1 ONLINE 0 0 0
errors: No known data errors
# |
Creation of backup storage pools
On the backup servers, create the backup storage pools to which the snapshots of the transaction storage pools will be backed up.
[Example]
Create a backup storage pool with the same configuration as transaction storage pool (STP1). In below example, the backup storage pool (STP1B) is created on 1 physical disk (c2t1d11).
# zpool create STP1B c2t1d11 # |
Copy settings for backup and restoration
Make the following 3 copy settings:
Copy settings for the backup storage pools and the backup volumes for older generations (for backup)
Copy settings for the backup storage pools and the transaction storage pools (for restoring the latest generations)
Copy settings for the backup volumes for older generations and the transaction storage pools (for restoring older generations)
Use the following combinations to register them in AdvancedCopy Manager:
Used for | Copy source | Copy destination | Group name (ex.) |
|---|---|---|---|
Backup | Backup storage pool | Backup volume for older generations | BKSTP1 |
Restoration of the latest generations | Backup storage pool | Transaction storage pool | R0STP1 |
Restoration of older generations | Backup volume for older generations | Transaction storage pool | R1STP1 |
Device name | Devices to be registered | Example (Note) | |
|---|---|---|---|
Device name | LUN | ||
Transaction storage pool | Devices that you confirmed in "Fetching lists of devices in transaction storage pools" to be devices constituting the transaction storage pool | c1t1d1 | 0x01 |
Backup storage pool | Devices that you created in "Creation of backup storage pools" and constitute the backup storage pool | c2t1d11 | 0x11 |
Backup volume for older generations | Devices you prepared as backup volumes for older generations | c2t1d12s1 | 0x12 |
Note: When using replication management, use device name. When using AdvancedCopy Manager CCM, use LUN number.
Register copy sources indicated at "Copy groups" as copy destination volumes, and copy destinations as copy destination volumes. Then register the devices indicated at "Registered devices" respectively.
Since these are controlled synchronously in processing for backup and restoration, you have to register all devices that constitute a storage pool as a single group. For details on controlling groups, refer to "6.4.7 Creating groups".
[Example]
Specify the source volumes and copy destination volumes to create the 3 groups shown in the chart.
# /opt/FJSVswsrp/bin/swsrpsetvol -Xgroup BKSTP1 /dev/dsk/c2t1d11 /dev/dsk/c2t1d12s1 swsrpsetvol completed # /opt/FJSVswsrp/bin/swsrpsetvol -o BOTH -Xgroup R0STP1 /dev/dsk/c2t1d11@BKSV /dev/dsk/c1t1d1@SV-1 swsrpsetvol completed # /opt/FJSVswsrp/bin/swsrpsetvol -o BOTH -Xgroup R1STP1 /dev/dsk/c2t1d12s1@BKSV /dev/dsk/c1t1d1@SV-1 swsrpsetvol completed # /opt/FJSVswsrp/bin/swsrpvolinfo -L Server Original-Volume Size Replica-Volume Size Copy Op-Server Group BKSV /dev/dsk/c2t1d11@BKSV 4.0 Gbyte /dev/dsk/c2t1d12s1@BKSV 4.0 Gbyte bi-direction original BKSTP1 BKSV /dev/dsk/c2t1d11@BKSV 4.0 Gbyte /dev/dsk/c1t1d1@SV-1 4.0 Gbyte bi-direction both R0STP1 BKSV /dev/dsk/c2t1d12s1@BKSV 4.0 Gbyte /dev/dsk/c1t1d1@SV-1 4.0 Gbyte bi-direction both R1STP1 # |
Register each combination of copy sources and copy destinations.
Since these are controlled synchronously in processing for backup and restoration, you have to register all devices that constitute a storage pool as a single group. For details on controlling groups, refer to "Creating copy groups" and "Adding copy pairs" in the "ETERNUS SF Operation Guide for Copy Control Module".
Creation of copy groups
Create a copy group for each copy setting.
[Example]
Create the 3 copy groups shown in the chart. (Copying type: OPC)
# acgroup create -g BKSTP1 -type OPC -a DX440 Successful completion. # # acgroup create -g R0STP1 -type OPC -a DX440 Successful completion. # # acgroup create -g R1STP1 -type OPC -a DX440 Successful completion. # |
Registration of copy pairs
In the created copy groups, register the combinations of copy sources and copy destinations. Register all devices that constitute a storage pool.
[Example]
In the created copy groups, register each device shown in the chart.
# acpair add -g BKSTP1 -p DX440/0x11:DX440/0x12 Successful completion. # acpair add -g R0STP1 -p DX440/0x11:DX440/0x01 Successful completion. # acpair add -g R1STP1 -p DX440/0x12:DX440/0x01 Successful completion. |
