When you design your storage pools and backup operation, pay attention to the following aspects:
Unit of Backup and Restoration: Storage Pool
AdvancedCopy Manager supports backup and restoration only in units of ZFS storage pools (all file systems within a storage pool). Backup and restoration in units of ZFS file systems are not available.
For details, refer to "G.1.1 Units of Backing up".
Version of ZFS Storage Pools
For implementing online backup, ZFS storage pool version of business servers and that of backup servers must be the same. For checking your ZFS storage pool version, refer to the operating system manuals.
[Example]
# zpool upgrade -v This system is currently running ZFS pool version 33. |
Types and Configurations of ZFS Storage Pools
With online backup, you can back up and restore data areas (usual storage pools). For backing up system areas (ZFS root pools), you have to use offline backup.
Online backup supports the following as device that constitutes ZFS storage pools (Physical disks).
Normal devices are supported.
Point
For details on using replication management function, refer to "1.4 Managing Device on AdvancedCopy Manager".
Entire disks (LUs) are supported.
Note
As is constituted with the entire disks (LUs), create storage pools.
Preparing Backup Storage Pool for Backup
As backup targets in online backup, you need to arrange for the following two types of backup targets:
Backup storage pool for backup
Backup volume
A "backup storage pool" serves to store of the latest data generations.
Make sure to arrange for one on the backup server.
The backup storage pool must have the same physical disk configuration (number of disks, sizes, redundant configuration) as the ZFS storage pool that is the backup source. Also, unit of devices that constitute storage pools must be the same.
A "backup volume" is a backup volume for storing the storage pools.
Make sure to arrange for the number of backup generations for the storage pools to be preserved on the backup server.
A backup volume must fulfill the conditions and have a configuration as described below.
For any conditions that are not stated below, depending on the type of device in the backup source volume, refer to "1.4 Managing Device on AdvancedCopy Manager", "Chapter 6 Replication", or the ETERNUS SF AdvancedCopy Manager Operation Guide for Copy Control Module.
Make sure that the backup volume has the same physical disk configuration (number of disks, sizes, and redundant configuration) as the ZFS storage pool that is the backup source.
If a ZFS storage pool consists of multiple physical disks, you have to use a backup volume whose physical disks all have the same size.
If you are using AdvancedCopy Manager CCM, do not connect the backup volume to the server.
When using replication management function, use backup volume as slices.
The combinations of transaction storage pools, backup storage pools and backup volumes are described below.
Function | Device | ||
|---|---|---|---|
Transaction Storage Pools | Backup Volume | ||
Backup Storage Pools | Backup Volume | ||
Replication management | LU | LU | Slice (Note) |
AdvancedCopy Manager CCM | LU | LU | LU |
Note: Define copy source as LU and copy destination as slice, then copy the entire LUs to the slice.
If a backup destination volume is LU, make the disk format of the transaction storage pool the same as that of the backup destination volume as shown below:
If the transaction storage pool is a VTOC-labeled disk, the backup destination volume should also be a VTOC-labeled disk.
If the transaction storage pool is an EFI-labeled disk, the backup destination volume should also be an EFI-labeled disk.
The servers to which to connect the backup volumes, depending on the copying functions to be used, are as shown below.
Backup Target Volume | Copying Function | |
|---|---|---|
Replication Management | AdvancedCopy Manager CCM | |
Backup storage pool | Backup server | Backup server |
Backup volume | Backup server | Do not connect to a server. |
