ReplicationControl FileSystem Option User s Manual (Linux)

Transcription

1 NEC Storage Software ReplicationControl FileSystem Option User s Manual (Linux) IS028-15E

2 NEC Corporation No part of the contents of this book may be reproduced or transmitted in any form without permission of NEC Corporation. The contents of this book may be modified without notice in the future.

3 Preface This manual is bundled with NEC Storage ReplicationControl FileSystem Option to explain, through descriptions and examples, how to use this product. This product provides the following commands for the NEC Storage series disk array subsystems. After performing data synchronization through a file system freeze Command to perform Separate for a disk through the data replication function (ReplicationControl) After performing data synchronization through a file system freeze Command to create a snapshot through the snapshot function (SnapControl) By using these commands, it is not necessary to stop the business applications that are running or perform unmount processing in order to synchronize data at data backup during a file system is being used. This can improve system operability and maintainability. For description of the data replication function and the snapshot function, refer to the NEC Storage Software Data Replication User s Manual (Function Guide) (IS015) and the NEC Storage Software Snapshot User s Manual (Function Guide) (IS030), respectively. For functional description regarding the disaster recovery of the data replication function, refer to the NEC Storage Software Data Replication User s Manual (Disaster Recovery System Installation and Operation Guide) (IS027). Also, refer to the NEC Storage Software Manual Guide (IS901) for a general description of NEC Storage and related manuals. Remarks 1. This manual explains functions implemented by the following program products: NEC Storage Manager and NEC Storage BaseProduct NEC Storage ControlCommand NEC Storage ReplicationControl FileSystem Option NEC Storage DynamicDataReplication NEC Storage RemoteDataReplication NEC Storage DynamicSnapVolume NEC Storage RemoteDataReplication/DisasterRecovery 2. This manual is applicable to the program products of the following versions: NEC Storage Manager Ver9.3 or later NEC Storage BaseProduct Ver9.3 or later NEC Storage ControlCommand on Linux Ver9.3 or later NEC Storage ReplicationControl FileSystem Option on Linux Ver9.3 or later 3. Unless otherwise stated, the NEC Storage Manager is referred to as ism or Storage Manager in the text of this manual. Also, the NEC Storage series disk array subsystem is referred to as a disk array.

4 4. The following descriptions in the text of this manual refer to the corresponding products unless otherwise stated. Description Corresponding Products ControlCommand DymanicDataReplication or DDR DynamicSnapVolume or DSV FileSystem Option PathManager or SPS RemoteDataReplication or RDR RemoteDataReplication/DisasterRecovery NEC Storage ControlCommand (Note) NEC Storage DymanicDataReplication NEC Storage DynamicSnapVolume NEC Storage ReplicationControl FileSystem Option NEC Storage PathManager NEC Storage RemoteDataReplication NEC Storage RemoteDataReplication/DisasterRecovery Note: NEC Storage ControlCommand is a program product that has integrated the following five functions. ReplicationControl SnapControl ReplicationControl/DisasterRecovery ProtectControl PowerControl 5. The following descriptions in the text of this manual refer to the corresponding manuals unless otherwise stated. Description Corresponding Manual Messages Handbook Data Replication User s Manual (Function Guide) Data Replication User s Manual (Installation and Operation Guide for Linux) Data Replication User s Manual (Disaster Recovery System Installation and Operation Guide) Snapshot User s Manual (Function Guide) Snapshot User s Manual (Installation and Operation Guide for Linux) ControlCommand Command Reference Manual Guide PathManager User s Manual (Linux) NEC Storage Software Messages Handbook (IS010) NEC Storage Software Data Replication User s Manual (Function Guide) (IS015) NEC Storage Software Data Replication User s Manual (Installation and Operation Guide for Linux) (IS020) NEC Storage Software Data Replication User s Manual (Disaster Recovery System Installation and Operation Guide) (IS027) NEC Storage Software Snapshot User s Manual (Function Guide) (IS030) NEC Storage Software Snapshot User s Manual (Installation and Operation Guide for Linux) (IS035) NEC Storage Software ControlCommand Command Reference (IS041) NEC Storage Software Manual Guide (IS901) NEC Storage Software PathManager User s Manual (Linux) (IS202) 6. The data replication function and ReplicationControl in this manual refer to the function provided by NEC Storage DynamicDataReplication, NEC Storage RemoteDataReplication, and NEC Storage ControlCommand. The disaster recovery function of the data replication function and ReplicationControl/DisasterRecovery in this manual refer to the function provided by NEC Storage RemoteDataReplication, NEC Storage RemoteDataReplication/DisasterRecovery, and NEC Storage ControlCommand. 7. The snapshot function or SnapControl in this manual refers to the function provided by NEC Storage DynamicSnapVolume and NEC Storage ControlCommand. 8. Trademarks and registered trademarks UNIX is a registered trademark of The Open Group in the United States and other countries. VERITAS, VxVM, VxFS, NetBackup, VERITAS Volume Manager, VERITAS File System, and VERITAS NetBackup are registered trademarks or trademarks of VERITAS Software Corporation in the United States and other countries. Sun is a registered trademark of Sun Microsystems, Inc. in the United States and other countries. Solaris is a trademark or a registered trademark of Sun Microsystems, Inc. in the United States and other

5 countries. Linux is a trademark or registered trademark of Mr. Linus Torvalds in the United States and other countries. Other product names and company names, etc. are trademarks or registered trademarks of the associated companies. 9. This product includes flex ( For details on the license, refer to Appendix C in this manual. 10. In this document, the capacity is calculated based on units of 1024 (for example 1 KB = 1024 bytes) unless otherwise specified. 11. In this document, matters to which careful attention needs to be paid will be described as follows: Be sure to observe the instructions. If the indications are ignored and the system is improperly operated, settings which have been already made might be affected. Type of Indication Type Description Describes contents which require users to pay special attention for operation. 1st Edition in April th Edition in October 2015

6 Contents Chapter 1 Product Overview Introduction Function Overview Data Replication Function Snapshot Function Example of Using Data Replication Function Backup Secondary Use in Search Tasks and Test Tasks Example of Using Snapshot Function Backup Secondary Use in Search Tasks and Test Tasks Example of Using Data Replication Function and Snapshot Function Together Backup Product Configuration Chapter 2 Operating Method Data Replication Function ismrc_fsseparate Command ismrc_fsreplicate Command Snapshot Operations ismsc_fscreate Command ismsc_fsdelete Command Chapter 3 Reference Manual Data Replication Operation ismrc_fsseparate Command ismrc_fsreplicate Command Snapshot Operation ismsc_fscreate Command ismsc_fsdelete Command Chapter 4 Output Messages Data Replication Operation Informational Messages Warning Messages Error Messages Snapshot Operation Informational Messages Warning Messages Error Messages Chapter 5 Notes Data Replication Operations Snapshot Operations Appendix A Volume Layout and Usability Appendix B FileSystem Option Operating Procedures B.1 When Using Data Replication Functions B.2 When Using Snapshot Functions Appendix C License C.1 Flex License Index i

7 Chapter 1 Product Overview Chapter 1 Product Overview 1.1 Introduction Disk arrays have made it possible to perform disk backup online any time that the data replication function or snapshot function is used. However, when data is configured by constructing a file system, the file system that is created on a disk is not necessarily input or output synchronously. Therefore, in order to use RVs or snapshots, it has been necessary to unmount the file system on the MV or BV before separating using the data replication function or creating a snapshot using the snapshot function. FileSystem Option is a software product that performs separation or snapshot creation after automatically performing file system synchronization when a disk is backed up using the data replication function or snapshot function in a disk array. FileSystem Option provides commands that perform separation or snapshot creation after performing data synchronization by VERITAS Volume Manager (hereafter abbreviated as VxVM) disk group in a VxVM environment and by disk in an environment without VxVM through a VERITAS File System (hereafter abbreviated as VxFS) file system freeze. This software also provides commands that perform separation or snapshot creation after performing data synchronization by LVM (hereafter abbreviated as LVM) volume group in the logical volume manager environment and by disk in an environment without LVM through ext3 /ext4 (hereafter abbreviated as ext) and xfs file system freeze. In an environment where the disaster recovery function of data replication is used, it provides commands that perform separation after performing data synchronization by Atomic Groups (hereafter abbreviated as ATgroup) through a VxFS/ext/xfs file system freeze. By using these commands, it is not necessary to halt the business applications that are running or perform unmount processing in order to synchronize data (application static points must be given on the application side to preserve application integrity), which can improve system operability and maintainability. In this document, without VxVM refers to an environment in which VxVM is not used, and with VxVM refers to one in which VxVM is used. In this document, without VxVM/LVM refers to an environment in which VxVM/LVM is not used, and with VxVM/LVM refers to one in which VxVM/LVM is used. 1

8 Chapter 1 Product Overview 1.2 Function Overview Data Replication Function (1) Separation function (File system synchronization + Separation) In a VxFS (with VxVM)/ext (with LVM)/xfs (with LVM) environment, separation can be performed after performing data synchronization through a file system freeze without unmounting the VxFS/ext/xfs file system on a disk group or volume group. In a VxFS (without V xvm)/ext (without LVM)/xfs (without LVM) environment, separation can be performed after performing data synchronization through a file system freeze without unmounting the VxFS/ext/xfs file system on a specified MV. Moreover, by specifying command options, the separated RV can be mounted as a new volume on the same server as the MV. When an ATgroup is specified, the MV/RV pairs in the ATgroup can be separated after data synchronization through a file system freeze without unmounting of the VxFS/ext/xfs file system in the ATgroup. (2) Replication function (Disk synchronization) In a VxFS (with VxVM)/ext (with LVM)/xfs (with LVM) environment, this function replicates from the paired MV configuring the disk group to RV. In a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment, this function replicates from specified MV to RV. Moreover, if the RV is mounted on the same server as the MV, it will replicate after unmounting the file system on the RV. If an error occurred in separation, using this operation restore When an ATgroup is specified, the MV/RV pairs in the ATgroup are replicated. Linux FileSystem Option ControlCommand VxFS (File system management) VxVM (Disk group (DG) management) Separate Disk array Re-replicate DG MV Disk group Freeze Unfreeze Separate Replicate FileSystem Option uses VxVM disk group management functions. RV OS commands from another server can be used to mount and use RV. FS synchronous disk separation Replication function Figure 1-1 Data Replication Function in VxFS (with VxVM) Environment 2

9 Chapter 1 Product Overview Linux FileSystem Option ControlCommand VxFS (File system management) PathManager (Redundant path management) Separate Re-replicate Freeze Unfreeze FSCK Mount (*1) For PathManager installed system, operation is executed by PathManager special file. Disk array MV Separate Replicate RV FS synchronous disk separation Replication function Mount option (*1) Figure 1-2 Data Replication Function in VxFS (without VxVM) Environment Linux FileSystem Option ControlCommand VxFS Separate Re-replicate Freeze Unfreeze VxVM (Disk group (DG) management) Atomic Group FileSystem Option uses VxVM disk group management functions. FS synchronous disk separation Replicate function DG DG MV MV Separate Replicate Disk array DG DG RV RV Main site Backup site Figure 1-3 Data Replication Function for Specified ATgroup (DG) 3

10 Chapter 1 Product Overview Linux FileSystem Option ControlCommand EXT (File system management) LVM (Disk group (VG) management) Separate Disk array Re-replicate VG MV Volume group Freeze Unfreeze Separate Replicate FileSystem Option uses LVM disk group management functions. RV OS commands from another server can be used to mount and use RV. FS synchronous disk separation Replication function Figure1-4 Data Replication Function in ext (with LVM) Environment Linux FileSystem Option ControlCommand EXT (File system management) PathManager (Redundant path management) Separate Re-replicate Freeze Unfreeze FSCK Mount (*1) For PathManager installed system, operation is executed by PathManager special file. Disk array MV Separate Replicate RV FS synchronous disk separation Replication function Mount option (*1) Figure1-5 Data Replication Function in ext (without LVM) Environment 4

11 Chapter 1 Product Overview Linux FileSystem Option ControlCommand EXT Separate Re-replicate Freeze Unfreeze LVM (Disk group (VG) management) Atomic Group FileSystem Option uses LVM disk group management functions. FS synchronous disk separation Replicate function VG VG MV Separate VG VG RV MV Replicate RV Disk array Main site Backup site Figure 1-6 Data Replication Function for Specified ATgroup (VG) Linux FileSystem Option ControlCommand XFS (File system management) LVM (Disk group (VG) management) Separate Disk array Re-replicate VG MV Volume group Freeze Unfreeze Separate Replicate FileSystem Option uses LVM disk group management functions. RV OS commands from another server can be used to mount and use RV. FS synchronous disk separation Replication function Figure1-7 Data Replication Function in xfs (with LVM) Environment 5

12 Chapter 1 Product Overview Linux FileSystem Option ControlCommand XFS (File system management) PathManager (Redundant path management) Separate Re-replicate Freeze Unfreeze For PathManager installed system, operation is executed by PathManager special file. Disk array MV Separate Replicate RV FS synchronous disk separation Replication function Mount option (*1) Figure1-8 Data Replication Function in xfs (without LVM) Environment Linux FileSystem Option ControlCommand XFS Separate Re-replicate Freeze Unfreeze LVM (Disk group (VG) management) Atomic Group FileSystem Option uses LVM disk group management functions. FS synchronous disk separation Replicate function VG VG MV MV Separate Replicate Disk array VG VG RV RV Main site Backup site Figure 1-9 Data Replication Function for Specified ATgroup (VG) 6

13 Chapter 1 Product Overview Snapshot Function (1) Snapshot creation function In a VxFS (with VxVM)/ext (with LVM)/xfs (with LVM) environment, this function creates a snapshot of a BV after performing data synchronization through a file system freeze without unmounting the VxFS/ext/xfs file system on the disk group/volume group. In a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment, this function creates a snapshot of a BV after performing data synchronization through a file system freeze without unmounting the VxFS/ext/xfs file system on the specified BV. Moreover, by specifying command options, it can perform SV and LV link processing after snapshot creation and mount the LV as a new volume on the same server as BV. If an error occurred in snapshot creation, the function performs snapshot creation again after deleting the created snapshot if necessary. (2) Snapshot deletion function In a VxFS (with VxVM)/ext (with LVM)/xfs (with LVM) environment, this function deletes a snapshot of a BV configuring the disk group/volume group. In a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment, this function deletes a snapshot after unmounting LV and unlinking SV and LV if the snapshot to be deleted has been linked and the LV has been mounted on the same server as the VxFS/ext/xfs file system. If SV and LV are linked without being mounted on the same server as the VxFS/ext/xfs file system, it will delete the snapshot after unlinking SV and LV. In other cases, it performs only snapshot deletion. 7

14 Chapter 1 Product Overview Linux FileSystem Option ControlCommand VxFS (File system management) VxVM (Disk group (DG) management) Create/delete snapshots Disk array DG BV Disk group Freeze Unfreeze FileSystem Option uses VxVM disk group management functions. Create snapshots SV Delete snapshots OS commands from another server can be used to mount and use SV. Snapshot function Figure 1-10 Snapshot Function in VxFS (with VxVM) Environment Linux FileSystem Option ControlCommand VxFS (File system management) PathManager Create/delete snapshots Disk array BV Freeze Unfreeze Create snapshots Delete snapshots FSCK Mount (*1) Snapshot function Mount option (*1) Figure 1-11 Snapshot Function in VxFS (without VxVM) Environment SV For PathManager installed system, operation is executed by PathManager special file. 8

15 Chapter 1 Product Overview Linux FileSystem Option ControlCommand XFS (File system management) LVM (Disk group (VG) management) Create/delete snapshots Disk array VG BV Volume group Freeze Unfreeze FileSystem Option uses LVM volume group management functions. Create snapshots SV Delete snapshots OS commands from another server can be used to mount and use SV. Snapshot function Figure 1-12 Snapshot Function in xfs (with LVM) Environment Linux FileSystem Option ControlCommand EXT (File system management) PathManager Create/delete snapshots Freeze Unfreeze Create snapshots FSCK Mount (*1) For PathManager installed system, operation is executed by PathManager special file. Disk array BV Delete snapshots SV Snapshot function Mount option (*1) Figure 1-13 Snapshot Function in xfs (without LVM) Environment 9

16 Chapter 1 Product Overview 1.3 Example of Using Data Replication Function Backup This section explains examples of using data replication function in application to operations that perform backup. (1) Backup from the replication volume to magnetic tapes This is a form of performing backup from a replication volume of a business volume to magnetic tapes. By separating the business volume and replication volume in a period of time when the workload is low, it is possible to create a replication volume and perform backup to magnetic tapes without halting operations. Moreover, since backup is performed from the replication volume, the business volume is not affected during backup. Application server Backup server Tape drive Production task Backup Business volume (MV) Replicate Separate Replication volume (RV) Figure 1-14 Backup from Replication Volume (1) During operation, leave the replication volume (RV) separated from the business volume (MV). (2) When the workload is low, replicate and synchronize the business volume (MV) and replication volume (RV) and then separate them. (3) Using the separated replication volume (RV), backup tasks can be executed concurrently with production tasks. Moreover, after it is backed up, the separated replication volume (RV) can be maintained as a disk backup. 10

17 Chapter 1 Product Overview (2) Disk backup by replication volume This is a form of using a replication volume as a backup of a business volume. By replicating and separating the business volume and replication volume in a time period when the workload is low, a replication volume can be created without halting operations and disks can be used as a backup. Application server Production task Replicate Business volume (MV) Separate Replication volume (RV1) Replication volume (RV2) Replication volume (RV3) Figure 1-15 Using Replication Volume as a Backup (1) During operation, leave the business volume (MV) and the replication volumes (RV1, RV2, and RV3) all separated. (2) When the workload is low, replicate and synchronize the business volume (MV) and replication volume 1 (RV1) and then separate them. (3) Thereafter, execute backup by using replication volume 1 (RV1), replication volume 2 (RV2), and replication volume 3 (RV3) in cyclic use. 11

18 Chapter 1 Product Overview Secondary Use in Search Tasks and Test Tasks Creating a replication of business data makes it possible for the replicated data to be used in search tasks and test tasks on another server. Thus, parallel processing without tasks affecting one another becomes possible. Figure 1-16 Parallel Processing of Test Tasks (1) In the daytime, leave the business volume (MV) and the replication volume (RV) separated. (2) In the nighttime, halt update tasks, replicate and synchronize the business volume (MV) and the replication volume (RV), and then separate them. (3) The business database and replication database can be used concurrently. In this case, the replication database is the previous day s data. 12

19 Chapter 1 Product Overview 1.4 Example of Using Snapshot Function Backup This is a form of using the snapshot function to create multiple generations of replication volumes of the business volume and using disks as backup while also periodically performing backup to magnetic tapes. By creating snapshots from the business volume when the workload is low, replication volumes can be created and backups are maintained without halting operations. Application server Backup server Tape drive Production task Backup Business volume (BV) Create snapshots Replication volume (SV1) Replication volume (SV2) Replication volume (SV3) LV Link latest generation - 1st generation (latest) - 2nd generation - 3rd generation Figure 1-17 Disk Backup and Backup to Magnetic Tapes Using Replication Volumes (1) Using nighttime or another time when the workload is low, periodically (for example once per day) create a snapshot (SV1) from the business volume (BV). Create snapshots by using the replication volumes (SV1, SV2, SV3) in cyclic use. (2) Link the most recently created snapshot (SV1) to the LV and perform backup tasks. Backup tasks can be executed concurrently with production tasks. Moreover, multiple generations of snapshots that have been backed up can be maintained as disk backups. (3) When logically restoring data on a malfunction or application fault, any generation of a disk backup can be used to directly restore data to the business volume (BV) from a snapshot (SV). Thus, a great reduction in data restoration time is possible. 13

20 Chapter 1 Product Overview Secondary Use in Search Tasks and Test Tasks Using a replication of a business database makes it possible for the replication database to be used in search, test, or other tasks on another server. Thus, parallel processing without operations affecting one another becomes possible. It is also possible to use the data of specific dates or times in the past by saving it as multiple generations. Application server 1 Application server 2 Application server 3 Production task Test task Search task Business volume (BV) Replication volume (SV1) LV LV Create snapshots Replication volume (SV2) Link any generation Replication volume (SV3) Replication volume (SV4) Figure 1-18 Parallel Processing by Search Tasks and Test Tasks <Secondary use in search tasks> (1) On a schedule such as once every night, create a snapshot (SV) from the business volume (BV). (2) Select the snapshot (SV) of the necessary generation and use it by linking it to the LV. By applying a transaction log backup to the replication database, it is possible to reflect business database update processing. <Secondary use in test tasks> (1) In the nighttime, halt update tasks and create a snapshot (SV) from the business volume (BV). (2) In the daytime, the business database and replication database can be used concurrently by linking the snapshot (SV) to the LV and using it on another server. In this case, the replication database is the previous day s data. 14

21 Chapter 1 Product Overview 1.5 Example of Using Data Replication Function and Snapshot Function Together Backup This is a form of performing backup by using the data replication function and snapshot function together. Executing backups to RV by the data replication function on a daily or weekly schedule and periodically backing up to tape or other media guards against physical faults such as disk faults. Moreover, executing backups to SV by the snapshot function every few hours guards against logical faults such as file deletion due to a malfunction. By operating using the data replication function and snapshot function together, effects such as the following can be expected. By creating a replication volume using the data replication function, fast restoration on a physical fault is possible by restoring from RV. Moreover, by performing backup to tape or other media using RV, it does not affect operations. By periodically creating a replication volume using the snapshot function and maintaining the latest data, failure can be kept to a minimum by restoring from SV at the time of a logical fault. Moreover, by saving data in generations, it is also possible to return to the data of a specific time in the past. Application server Backup server Tape drive Production task Backup Create snapshots Business volume (MV)/(BV) Replicate Separate Replication volume (SV1) Replication volume (SV2) Replication volume (RV) - 1st generation (Latest) - 2nd generation Replication volume (SV3) - 3rd generation Figure 1-19 Using Data Replication Function and Snapshot Function Together 15

22 Chapter 1 Product Overview 1.6 Product Configuration This product provides the following commands. ismrc_fsseparate: File system synchronous separation in a disk array ismrc_fsreplicate: Replication in a disk array ismsc_fscreate: File system synchronization and snapshot creation in a disk array ismsc_fsdelete: Snapshot deletion in a disk array 16

23 Chapter 2 Operating Method Chapter 2 Operating Method 2.1 Data Replication Function ismrc_fsseparate Command The ismrc_fsseparate command separates the RV that is paired with the MV configuring the disk group/volume group or the MV specified by a special file name or the logical disk name. It is executed by specifying a disk group name in a VxFS (with VxVM)/ext (with LVM)/xfs (with LVM) environment and by specifying the special file name or the logical disk name of the MV in a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment. It can be executed by specifying the PathManager or Device Mapper Multipath (hereafter abbreviated as DM-Multipath) special file name in a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment in which PathManager or DM-Multipath is installed. The ismrc_fsseparate command separates the MVs and RVs in all RDR pairs belonging to the ATgroup by specifying an ATgroup. It performs separation after performing a VxFS file system/ext file system/xfs file system freeze and disk synchronization. The VxFS file system/ext file system/xfs file system is unfrozen after separation ends. While the file system freeze executes, the processing of operations that access the file system is frozen until the file system is unfrozen. Moreover, for a process that is writing to a file on the file system, the content that it writes up until it freezes are synchronized on the disk. (1) When disk group MV/RV are paired one-to-one in VxFS (with VxVM) environment The execution example below is a case in which VxVM volumes lvol1 through lvol3 exist on a logical disk of disk group dg01 configured on MV: mv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. root> /usr/sbin/ismrc_fsseparate -m dg dg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld01 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success 17

24 Chapter 2 Operating Method (2) When disk group MV/RV are paired one-to-many in VxFS (with VxVM) environment When the MV configuring the disk group and RV are paired one-to-many, the separation operation is performed after specifying MV and RV pairs in a pair file. The execution example below is a case in which VxVM volumes lvol1 through lvol3 exist on a logical disk of disk group dg01 configured on MV: mv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. Moreover, the multiple RVs rv_ld01 through rv_ld03 are paired with MV: mv_ld01 and, of these, rv_ld02 is to be separated. root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/ismrc_fsseparate -m dg -f pair_file.txt dg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld02 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success 18

25 Chapter 2 Operating Method (3) When time-out occurs while separating in VxFS (with VxVM) environment When file system synchronization takes time and it exceeds the freeze execution time of the file system (default: 60 seconds), it is displayed as follows. Warning: Sync Timeout! Warning: The pair is still in synchronizing state: sep/exec. Warning: Please check volume pair state. Error: Separate state error on MV: mv_ld01 RV: rv_ld01 ismrc_fsseparate: Separate Failed In such a case, since it is possible that the disk was separated without completing the synchronization of data that was written to the file system, perform replication again using the ismrc_fsreplicate command. Afterwards, specify a value greater than 60 in the -t option and execute the ismrc_fsseparate command again. Moreover, after executing the ismrc_fsseparate command, if the separation of a disk pair does not end even when the separation waiting time per disk (default: 60 seconds) is exceeded, warnings and errors are displayed as shown below. Warning: Sync Timeout! Warning: The pair is still in synchronizing state: sep/exec. Warning: Please check volume pair state. Error: Separate state error on MV: mv_ld01 RV: rv_ld01 ismrc_fsseparate: Separate Failed If the separation of a disk pair just takes time, this error is not a problem since disk separation will be completed with the passage of time. To confirm whether or not there is a disk fault, check the separate state of the disk by using the ismrc_query command or ism client. If the differential quantity of volume is great between MV and RV or the system is in a high load state, try executing after specifying a value greater than 60 in the -t option. The following is a case in which a maximum disk separation waiting time for one disk of five minutes is specified. root> /usr/sbin/ismrc_fsseparate -m dg -t 300 dg01 19

26 Chapter 2 Operating Method (4) When MV/RV are paired one-to-one in VxFS (without VxVM) environment The execution example below is a case in which the VxFS file system that exists on MV: mv_ld01 (logical disk name) is mounted on /mnt1. root> /usr/sbin/ismrc_fsseparate -m ld mv_ld01 *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success Separating MV: mv_ld01 RV: rv_ld01 (5) When MV/RV are paired one-to-many in VxFS (without VxVM) environment When MV and RV are paired one-to-many, they are separated after specifying one pair of MV and RV in options or specifying one or more pairs of MV and RV in a pair file. The execution example below is a case in which the VxFS file system that exists on MV: mv_ld01 (logical disk name) is mounted on /mnt1. Moreover, MV: mv_ld01 and RVs (rv_ld01 through rv_ld03) are paired one-to-many and, of these, rv_ld02 is to be separated. A case of specifying one MV and RV pair in options and that of specifying the MV and RV pair in a pair file are shown. Specifying one MV and RV pair in options root> /usr/sbin/ismrc_fsseparate -m ld -o rvvolume=rv_ld02,rvflg=ld mv_ld01 *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success Separating MV: mv_ld01 RV: rv_ld02 Specifying a pair file root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/ismrc_fsseparate -f pair_file.txt *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success Separating MV: mv_ld01 RV: rv_ld02 20

27 Chapter 2 Operating Method (6) When time-out occurs while separating in VxFS (without VxVM) environment When file system synchronization and disk separation processing take time, and it exceeds the file system freeze execution time (default: 60 seconds), a time-out occurs. This is the same as the case in (3). (7) When mounting RV on same server in VxFS (without VxVM) environment To mount a separated RV as another file system, execute specifying the o mnt option. The execution example below is a case in which MV: mv_ld01 (logical disk name) exists and its file system is mounted on /mnt1. Moreover, the o mnt option mounts the file system on the separated rv_ld01 (logical disk name) on the same server as the MV. root> /usr/sbin/ismrc_fsseparate -m ld -o mnt mv_ld01 *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld01 *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success *** -o mnt option Start /dev/sdx is mounted on /mnt1_tmp1 *** -o mnt option Success The mount point name to be mounted at this time is the one obtained by appending _tmpn (N: Integer > 1) to the mount point name of the file system mounted on the MV side. If multiple RVs are paired with MV and are separated and mounted at the same time, N is assigned values 1, 2, 3. The mount options used at this time are the default options (same as not specifying options in the mount command). If you wish to mount RV using VxFS mount options, try unmounting and remounting. Moreover, if a mount point to which _tmpn (N: Integer > 1) is already appended is in use, executing this command double registers the same mount point. As a result, the originally registered mount point is replaced. Try not to use mount points to which _tmpn is appended in different file systems. 21

28 Chapter 2 Operating Method (8) When specifying ATgroup in VxFS (with VxVM) environment The execution example below is a case in which ATgroup: atg01 is configured by two MVs. MV: mv_ld01 (logical disk name) configures disk group dg01 where VxVM volumes lvol1 and lvol2 exist, which are mounted on /mnt1 and /mnt2, respectively. MV: mv_ld02 (logical disk name) configures disk group dg02 where VxVM volumes lvol3 and lvol4 exist, which are mounted on /mnt3 and /mnt4, respectively. root> /usr/sbin/ismrc_fsseparate -m atg atg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 Freezing /mnt4 *** Freeze Success Info: ATgroup is separating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 Unfreezing /mnt4 *** Unfreeze Success *** Separate Success (9) When specifying ATgroup in VxFS (without VxVM) environment The execution example below is a case in which ATgroup: atg01 is configured by three MVs. VxFS file systems existing on MV: mv_ld01 through mv_ld03 (logical disk name) are mounted on /mnt1 through /mnt3, respectively. root> /usr/sbin/ismrc_fsseparate -m atg atg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 *** Freeze Success Info: ATgroup is separating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 MV: mv_ld03 RV: rv_ld03 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success 22

29 Chapter 2 Operating Method (10) When time-out occurs while separating in ATgroup specification When file system synchronization takes time and it exceeds the freeze execution time of the file system (default: 60 seconds), it is displayed as follows. *** Unfreeze Start Error: ioctl VX_THAW /mnt1: Connection timed out Error: ioctl VX_THAW /mnt2: Connection timed out Error: ioctl VX_THAW /mnt3: Connection timed out Warning: Unfreeze Timeout! Warning: Separate is not correctly done. Warning: You must merge again and please retry Warning: to separate setting larger value of timeout. ismrc_fsseparate: Unfreeze Failed In such a case, since it is possible that the ATgroup was separated without completing the synchronization of data that was written to the file system, perform replication again using the ismrc_fsreplicate command. Afterwards, specify a value greater than 60 in the -t option and execute the ismrc_fsseparate command again. Moreover, after executing the ismrc_fsseparate command, if the separation of ATgroup does not end even when the separation waiting time of ATgroup (default: 60 seconds) is exceeded, warnings and errors are displayed as shown below. Warning: Sync Timeout! Warning: The ATgroup is still in synchronizing state: ATgroup sep/exec. Warning: Please check ATgroup state. Error: Separate state error on ATgroup: atg01. ismrc_fsseparate: Separate Failed If ATgroup separation just takes time, this error is not a problem since ATgroup separation will be completed with the passage of time. To confirm whether or not there is an ATgroup fault, check the separate state of ATgroup by using the ismrc_query command or ism client. If the differential quantity of volume is great between MV and RV or the system is in a high load state, try executing after specifying a value greater than 60 in the -t option. The following is a case in which a maximum waiting time for ATgroup of five minutes is specified. root> /usr/sbin/ismrc_fsseparate -m atg -t 300 atg01 23

30 Chapter 2 Operating Method (11) When volume group MV/RV are paired one-to-one in ext (with LVM)/xfs (with LVM) environment The execution example below is a case in which LVM volumes lvol1 through lvol3 exist on a logical disk of volume group vg01 configured on MV: mv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. root> /usr/sbin/ismrc_fsseparate -m vg vg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 *** Freeze Success *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success Separating MV: mv_ld01 RV: rv_ld01 (12) When volume group MV/RV are paired one-to-many in ext (with LVM)/xfs (with LVM) environment When the MV configuring the volume group and RV are paired one-to-many, the separation operation is performed after specifying MV and RV pairs in a pair file. The execution example below is a case in which LVM volumes lvol1 through lvol3 exist on a logical disk of volume group vg01 configured on MV: mv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. Moreover, the multiple RVs rv_ld01 through rv_ld03 are paired with MV: mv_ld01 and, of these, rv_ld02 is to be separated. root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/ismrc_fsseparate -m vg -f pair_file.txt vg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld02 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success 24

31 Chapter 2 Operating Method (13) When time-out occurs while separating in ext (with LVM)/xfs (with LVM) environment When file system synchronization takes time and it exceeds the freeze execution time of the file system (default: 60 seconds), it is displayed as follows. Warning: Sync Timeout! Warning: The pair is still in synchronizing state: sep/exec. Warning: Please check volume pair state. Error: Separate state error on MV: mv_ld01 RV: rv_ld01 ismrc_fsseparate: Separate Failed In such a case, since it is possible that the disk was separated without completing the synchronization of data that was written to the file system, perform replication again using the ismrc_fsreplicate command. Afterwards, specify a value greater than 60 in the -t option and execute the ismrc_fsseparate command again. Moreover, after executing the ismrc_fsseparate command, if the separation of a disk pair does not end even when the separation waiting time per disk (default: 60 seconds) is exceeded, warnings and errors are displayed as shown below. Warning: Sync Timeout! Warning: The pair is still in synchronizing state: sep/exec. Warning: Please check volume pair state. Error: Separate state error on MV: mv_ld01 RV: rv_ld01 ismrc_fsseparate: Separate Failed If the separation of a disk pair just takes time, this error is not a problem since disk separation will be completed with the passage of time. To confirm whether or not there is a disk fault, check the separate state of the disk by using the ismrc_query command or ism client. If the differential quantity of volume is great between MV and RV or the system is in a high load state, try executing after specifying a value greater than 60 in the -t option. The following is a case in which a maximum disk separation waiting time for one disk of five minutes is specified. root> /usr/sbin/ismrc_fsseparate -m vg -t 300 vg01 25

32 Chapter 2 Operating Method (14) When MV/RV are paired one-to-one in ext (without LVM)/xfs (without LVM) environment The execution example below is a case in which the ext file system that exists on MV: mv_ld01 (logical disk name) is mounted on /mnt1. root> /usr/sbin/ismrc_fsseparate -m ld mv_ld01 *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld01 *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success (15) When MV/RV are paired one-to-many in ext (without LVM)/xfs (without LVM) environment When MV and RV are paired one-to-many, they are separated after specifying one pair of MV and RV in options or specifying one or more pairs of MV and RV in a pair file. The execution example below is a case in which the ext file system that exists on MV: mv_ld01 (logical disk name) is mounted on /mnt1. Moreover, the multiple RVs rv_ld01 through rv_ld03 are paired with MV: mv_ld01 and, of these, rv_ld02 is to be separated. A case of specifying one MV and RV pair in options and that of specifying the MV and RV pair in a pair file are shown. Specifying one MV and RV pair in options root> /usr/sbin/ismrc_fsseparate -m ld -o rvvolume=rv_ld02,rvflg=ld mv_ld01 *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld02 *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success Specifying a pair file root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/ismrc_fsseparate -f pair_file.txt *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld02 *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success 26

33 Chapter 2 Operating Method (16) When time-out occurs while separating in ext (without LVM)/xfs (without LVM) environment When file system synchronization and disk separation processing takes time and it exceeds the freeze execution time of the file system (default: 60 seconds), a time-out occurs. This is the same as the case in (13). (17) When mounting RV on same server in ext (without LVM)/xfs (without LVM) environment To mount a separated RV as another file system, execute specifying the o mnt option. The execution example below is a case in which the MV: mv_ld01 (logical disk name) exists and its file system is mounted on /mnt1. Moreover, the o mnt option mounts the file system on the separated rv_ld01 (logical disk name) on the same server as the MV. root> /usr/sbin/ismrc_fsseparate -m ld -o mnt mv_ld01 *** Separate Start *** Freeze Start Freezing /mnt1 *** Freeze Success Separating MV: mv_ld01 RV: rv_ld01 *** Unfreeze Start Unfreezing /mnt1 *** Unfreeze Success *** Separate Success *** -o mnt option Start /dev/sdx is mounted on /mnt1_tmp1 *** -o mnt option Success The mount point name to be mounted at this time is the one obtained by appending _tmpn (N: Integer > 1) to the mount point name of the file system mounted on the MV side. If multiple RVs are paired with MV and are separated and mounted at the same time, N is assigned values 1, 2, 3. The mount options used at this time are the default options (same as not specifying options in the mount command). If you wish to mount RV using ext/xfs mount options, try unmounting and remounting. Moreover, if a mount point to which _tmpn (N: Integer > 1) is already appended is in use, executing this command double registers the same mount point. As a result, the originally registered mount point is replaced. Try not to use mount points to which _tmpn is appended in different file systems. 27

34 Chapter 2 Operating Method (18) When specifying ATgroup in ext (with LVM)/xfs (with LVM) environment The execution example below is a case in which ATgroup: atg01 is configured by two MVs. MV: mv_ld01 (logical disk name) configures volume group dg01 where LVM volumes lvol1 and lvol2 exist, which are mounted on /mnt1 and /mnt2, respectively. MV: mv_ld02 (logical disk name) configures volume group dg02 where LVM volumes lvol3 and lvol4 exist, which are mounted on /mnt3 and /mnt4, respectively. root> /usr/sbin/ismrc_fsseparate -m atg atg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 Freezing /mnt4 *** Freeze Success Info: ATgroup is separating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 Unfreezing /mnt4 *** Unfreeze Success *** Separate Success (19) When specifying ATgroup in ext (without LVM)/xfs (without LVM) environment The execution example below is a case in which ATgroup: atg01 is configured by three MVs. The ext/xfs file systems existing on MV: mv_ld01 through mv_ld03 (logical disk name) are mounted on /mnt1 through /mnt3, respectively. root> /usr/sbin/ismrc_fsseparate -m atg atg01 *** Separate Start *** Freeze Start Freezing /mnt1 Freezing /mnt2 Freezing /mnt3 *** Freeze Success Info: ATgroup is separating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 MV: mv_ld03 RV: rv_ld03 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success 28

35 Chapter 2 Operating Method ismrc_fsreplicate Command The ismrc_fsreplicate command replicates a separated MV and RV pair. It is executed by specifying a disk group name/volume group name in a VxFS (with VxVM)/ext (with LVM)/xfs (with LVM) environment and by specifying the special file name or the logical disk name of the MV in a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment. It can be executed in a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment in which PathManager or DM-Multipath is installed by specifying the PathManager or DM-Multipath special file name. In a VxFS (without VxVM)/ext (without LVM)/xfs (without LVM) environment, if the RV file system is mounted on the same server as the MV, it will replicate after unmounting the file system on the RV. The ismrc_fsreplicate command replicates the MVs and RVs in all RDR pairs belonging to the ATgroup by specifying an ATgroup. (1) When disk group MV/RV are paired one-to-one in VxFS (with VxVM) environment The execution example below is a case in which VxVM volumes lvol1 through lvol3 exist on a logical disk of disk group dg01 configured on MV: mv_ld01 (logical disk name). root> /usr/sbin/ismrc_fsreplicate -m dg dg01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld01 *** Replicate Success (2) When disk group MV/RV are paired one-to-many in VxFS (with VxVM) environment When the MV configuring the disk group and RV are paired one-to-many, the replication operation is performed after specifying pairs of MV and RV in a pair file. The execution example below is a case in which VxVM volumes lvol1 through lvol3 exist on a logical disk of disk group dg01 configured on MV: mv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. Moreover, the MV: mv_ld01 and RVs (rv_ld01 through rv_ld03) are paired one-to-many and, of these, rv_ld02 is being replicated. root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/ismrc_fsreplicate -m dg -f pair_file.txt dg01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld02 *** Replicate Success 29

36 Chapter 2 Operating Method (3) When time-out occurs while replicating in VxFS (with VxVM) environment If, after executing the ismrc_fsreplicate command, replication of the disk pair does not end even on exceeding the synchronization waiting time for one disk (default: 60 seconds), warnings and errors are displayed as shown below. Warning: Sync Timeout! Warning: The pair is still in synchronizing state: rpl/exec. Warning: Please check volume pair state. Error: Replicate state error on MV: mv_ld01 RV: rv_ld01 ismrc_fsreplicate: Replicate Failed If replication of a disk pair just takes time, this error is not a problem since disk replication will be completed with the passage of time. To confirm whether or not there is a disk fault, check the replicate state of the disk by using the ismrc_query command or ism client. If the differential quantity of volume is great between MV and RV or the system is in a high load state, try executing after specifying a value greater than 60 in the -t option. The following is a case in which a maximum synchronization waiting time for one disk of five minutes is specified. root> /usr/sbin/ismrc_fsreplicate -m dg -t 300 dg01 (4) When MV/RV are paired one-to-one in VxFS (without VxVM) environment The execution example below is a case in which MV: mv_ld01 (logical disk name) and RV: rv_ld01 (logical disk name) are paired and in the separate state. root> /usr/sbin/ismrc_fsreplicate -m ld mv_ld01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld01 *** Replicate Success 30