Top
ETERNUS SF AdvancedCopy Manager 14.2 Operator's Guide

4.8.2 Backup operation in units of physical disks

When the volume group configuration does not satisfy the conditions of operation in units of volume groups, backup can be performed by operation in units of physical disks.

When backup is performed in units of physical disks, volume group integrity must be maintained. Therefore, all the physical disks in the volume group must be operated synchronously.

Point

Refer to "stgxfwcmdispdev (Device information display command)", or the "View Devices Using the Same Copy Area or the Same Logical Group" in the "ETERNUS SF AdvancedCopy Manager User's Guide" for details of how to determine which physical volumes should be operated synchronously.

Note

For operation in a cluster configuration, the device name (/dev/(r)dsk/c#t#d#) of the physical disks that comprise the volume group must be the same at all servers that comprise the cluster, and the ETERNUS disk indicated by the device name must also be the same.

Figure 4.15 Sample configuration for operation in units of physical disks


4.8.2.1 Operational configuration

In order to use a replica volume after replication if the original volume is a volume group, the replica volume must have the same logical volume configuration as the original volume, and must be a volume group of the same physical size.

Figure 4.16 Transaction volume and backup volume


4.8.2.2 Preparations


4.8.2.2.1 Saving the volume group configuration information file

The volume group configuration information file must be restored during backup post-processing.

Confirm that the volume group configuration file has been saved. It is usually saved to the following location:

/etc/lvmconf/<volume-group-name>.conf

4.8.2.2.2 Configuring the transaction volume and backup volume

When configuring the transaction volume and backup volume, specify all of the disks in the volume group.

Example:
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/dsk/c1t0d10
swstdevinfoset completed
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/dsk/c1t0d11
swstdevinfoset completed
# /opt/FJSVswsts/bin/swstdevinfoset -b /dev/dsk/c1t0d20 
swstdevinfoset completed
# /opt/FJSVswsts/bin/swstdevinfoset -b /dev/dsk/c1t0d21
swstdevinfoset completed
#

4.8.2.2.3 Example of a device map file

In the case of a backup of an LVM volume, a device map file must be created. This is because a backup volume with the same volume structure as the transaction volume must be specified.

Example of a device map file
# Transaction volume           Backup volume
/dev/dsk/c1t0d10               /dev/dsk/c1t0d20
/dev/dsk/c1t0d11               /dev/dsk/c1t0d21

For details on device map files, refer to "4.4.10 Preparing a device map file".


4.8.2.3 Backup in units of physical disks

Perform the operation by synchronizing all physical disks in the volume group.

Perform the required pre-processing or post-processing work for each volume group before and after (respectively) the backup. Disable pre-processing and post-processing when operating individual physical disks.

Example of snapshot backup
(Perform preprocessing for the transaction and backup volumes.)
# /opt/FJSVswsts/bin/swstbackup /dev/dsk/c1t0d10 -Xdevmap /acm/devmap.txt
/dev/dsk/c1t0d10 swstbackup completed
# /opt/FJSVswsts/bin/swstbackup /dev/dsk/c1t0d11 -Xdevmap /acm/devmap.txt
/dev/dsk/c1t0d11 swstbackup completed
#
(Perform post-processing for the transaction and backup volumes.)
Example of synchronous backup
(Perform pre-processing for the backup volume.)
# /opt/FJSVswsts/bin/swststartsync /dev/dsk/c1t0d10 -Xdevmap /acm/devmap.txt
/dev/dsk/c1t0d10 swststartsync completed
# /opt/FJSVswsts/bin/swststartsync /dev/dsk/c1t0d11 -Xdevmap /acm/devmap.txt
/dev/dsk/c1t0d11 swststartsync completed
(After state of equivalency upkeep)
(Perform preprocessing for the transaction volume.)
# /opt/FJSVswsts/bin/swstbackup /dev/dsk/c1t0d10
/dev/dsk/c1t0d10 swstbackup completed
# /opt/FJSVswsts/bin/swstbackup /dev/dsk/c1t0d11
/dev/dsk/c1t0d11 swstbackup completed
#
(Perform post-processing for the transaction and backup volumes.)

The table below summarizes the pre-processing and post-processing work to be performed before and after backup.

Table 4.4 Backup pre-processing and post-processing

Pre-processing

Post-processing

Transaction
volume

  1. Ensure data integrity by preventing access to all logical volumes in the volume group.

  2. If file systems are included, unmount all file systems in the volume group.

If file systems are included, remount the volumes that were unmounted by pre-processing.

Backup
volume

  1. Prevent access to all logical volumes in the volume group.

  2. If file systems are included, unmount all file systems in the volume group.

  1. Reconfigure the volume group

  2. If file systems are included, remount the volumes that were unmounted by pre-processing.

Reconfiguring the volume group

Reconfigure the volume group as follows:

  1. Deactivate the volume group.

    # /usr/sbin/vgchange -a n /dev/vg02
    #
  2. Restore volume group configuration information.

    # /usr/sbin/vgcfgrestore -n /dev/vg02 /dev/rdsk/c1t0d20
    # /usr/sbin/vgcfgrestore -n /dev/vg02 /dev/rdsk/c1t0d21
    #
  3. Reactivate the volume group.

    [When cluster operation is enabled]
    # /usr/sbin/vgchange -c y /dev/vg02
    # /usr/sbin/vgchange -a e /dev/vg02
    
    [When cluster operation is disabled]
    # /usr/sbin/vgchange -a y /dev/vg02
    #

Reconfigure shared mode volume groups using the following procedure:

  1. Stop the volume group (on all nodes involved in the transaction).

    # /usr/sbin/vgchange -a n /dev/vg02
    #
  2. Restore the volume group configuration information (on the node where the volume group was created).

    # /usr/sbin/vgcfgrestore -n /dev/vg02 /dev/rdsk/c1t0d20
    # /usr/sbin/vgcfgrestore -n /dev/vg02 /dev/rdsk/c1t0d21
    #
  3. Mark the volume group as shareable (on the node where the volume group was created).

    # /usr/sbin/vgchange -S y -c y /dev/vg02
    #
  4. Start the volume group (on all nodes involved in the transaction).

    # /usr/sbin/vgchange -a s /dev/vg02
    #

4.8.2.4 Restoration in units of physical disks

Perform this operation by synchronizing all physical disks in the volume group.

Perform the required pre-processing or post-processing work for each volume group before and after the restoration respectively. Disable pre-processing and post-processing when using individual physical disks.

Example of restoration
(Perform preprocessing for the transaction and backup volumes.)
# /opt/FJSVswsts/bin/swstrestore /dev/dsk/c1t0d10
/dev/dsk/c1t0d10 swstrestore completed
# /opt/FJSVswsts/bin/swstrestore /dev/dsk/c1t0d11
/dev/dsk/c1t0d11 swstrestore completed

(Perform post-processing for the transaction and backup volumes.)

The table below summarizes the pre-processing and post-processing work to be performed before and after restoration.

Table 4.5 Restoration processing

Pre-processing

Post-processing

Backup
volume

Ensure data integrity by preventing access to all logical volumes in the volume group.

Post-processing is not required.

Restoration
destination
volume

  1. Prevent access to all logical volumes in the volume group.

  2. If file systems are included, unmount all file systems in the volume group.

  1. Reconfigure the volume group

  2. If file systems are included, remount the volumes that were unmounted during pre-processing.

Reconfiguring the volume group

Reconfigure the volume group as follows:

  1. Deactivate the volume group.

    # /usr/sbin/vgchange -a n /dev/vg01
    #
  2. Restore the volume group configuration information.

    # /usr/sbin/vgcfgrestore -n /dev/vg01 /dev/rdsk/c1t0d10
    # /usr/sbin/vgcfgrestore -n /dev/vg01 /dev/rdsk/c1t0d11
    #
  3. Reactivate the volume group.

    [When cluster operation is enabled]
    # /usr/sbin/vgchange -c y /dev/vg01
    # /usr/sbin/vgchange -a e /dev/vg01
    
    [When cluster operation is disabled]
    # /usr/sbin/vgchange -a y /dev/vg01
    #

Reconfigure shared mode volume groups using the following procedure:

  1. Stop the volume group (on all nodes involved in the transaction).

    # /usr/sbin/vgchange -a n /dev/vg01
    #
  2. Restore volume group configuration information (on the node where the volume group was created).

    # /usr/sbin/vgcfgrestore -n /dev/vg01 /dev/rdsk/c1t0d10
    # /usr/sbin/vgcfgrestore -n /dev/vg01 /dev/rdsk/c1t0d11
    #
  3. Mark the volume group as shareable (on the node where the volume group was created).

    # /usr/sbin/vgchange -S y -c y /dev/vg01
    #
  4. Start the volume group (on all nodes involved in the transaction).

    # /usr/sbin/vgchange -a s /dev/vg01
    #