Nec Storage Software Replicationcontrol Filesystem Option User`s

Transcript

NEC Storage Software ReplicationControl FileSystem Option User’s Manual (Linux) IS028-13E ©NEC Corporation 2005-2014 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. 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.1or later  NEC Storage BaseProduct Ver9.1or later  NEC Storage ControlCommand on Linux Ver9.1 or later  NEC Storage ReplicationControl FileSystem Option on Linux Ver9.1 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. The following descriptions in the text of this manual refer to the corresponding products unless otherwise stated. Description Corresponding Products ControlCommand NEC Storage ControlCommand (Note) DymanicDataReplication or DDR NEC Storage DymanicDataReplication DynamicSnapVolume or DSV NEC Storage DynamicSnapVolume FileSystem Option NEC Storage ReplicationControl FileSystem Option PathManager or SPS NEC Storage PathManager RemoteDataReplication or RDR NEC Storage RemoteDataReplication RemoteDataReplication/DisasterRecovery 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 NEC Storage Software Messages Handbook (IS010) Data Replication User’s Manual (Function Guide) NEC Storage Software Data Replication User’s Manual (Function Guide) (IS015) Data Replication User’s Manual (Installation and Operation Guide for Linux) NEC Storage Software Data Replication User’s Manual (Installation and Operation Guide for Linux) (IS020) Data Replication User’s Manual (Disaster Recovery System Installation and Operation Guide) NEC Storage Software Data Replication User’s Manual (Disaster Recovery System Installation and Operation Guide) (IS027) Snapshot User’s Manual (Function Guide) NEC Storage Software Snapshot User’s Manual (Function Guide) (IS030) Snapshot User’s Manual (Installation and Operation Guide for Linux) NEC Storage Software Snapshot User’s Manual (Installation and Operation Guide for Linux) (IS035) ControlCommand Command Reference NEC Storage Software ControlCommand Command Reference (IS041) Manual Guide NEC Storage Software Manual Guide (IS901) PathManager User’s Manual (Linux) 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 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 (http://flex.sourceforge.net/). 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 2005 13th Edition in October 2014 Contents Chapter 1 Product Overview .............................................................................................................................................. 1 1.1 Introduction ................................................................................................................................................................. 1 1.2 Function Overview ...................................................................................................................................................... 2 1.2.1 Data Replication Function ................................................................................................................................... 2 1.2.2 Snapshot Function ............................................................................................................................................... 6 1.3 Example of Using Data Replication Function ............................................................................................................. 9 1.3.1 Backup ................................................................................................................................................................. 9 1.3.2 Secondary Use in Search Tasks and Test Tasks ................................................................................................ 11 1.4 Example of Using Snapshot Function ....................................................................................................................... 12 1.4.1 Backup ............................................................................................................................................................... 12 1.4.2 Secondary Use in Search Tasks and Test Tasks ................................................................................................ 13 1.5 Example of Using Data Replication Function and Snapshot Function Together ...................................................... 14 1.5.1 Backup ............................................................................................................................................................... 14 1.6 Product Configuration ............................................................................................................................................... 15 Chapter 2 Operating Method ........................................................................................................................................... 16 2.1 Data Replication Function ......................................................................................................................................... 16 2.1.1 iSMrc_fsseparate Command .............................................................................................................................. 16 2.1.2 iSMrc_fsreplicate Command ............................................................................................................................. 28 2.2 Snapshot Operations .................................................................................................................................................. 37 2.2.1 iSMsc_fscreate Command ................................................................................................................................. 37 2.2.2 iSMsc_fsdelete Command ................................................................................................................................. 45 Chapter 3 Reference Manual ............................................................................................................................................ 49 3.1 Data Replication Operation ....................................................................................................................................... 49 3.1.1 iSMrc_fsseparate Command .............................................................................................................................. 49 3.1.2 iSMrc_fsreplicate Command ............................................................................................................................. 55 3.2 Snapshot Operation ................................................................................................................................................... 61 3.2.1 iSMsc_fscreate Command ................................................................................................................................. 61 3.2.2 iSMsc_fsdelete Command ................................................................................................................................. 66 Chapter 4 Output Messages .............................................................................................................................................. 70 4.1 Data Replication Operation ....................................................................................................................................... 70 4.1.1 Informational Messages ..................................................................................................................................... 70 4.1.2 Warning Messages ............................................................................................................................................. 72 4.1.3 Error Messages .................................................................................................................................................. 75 4.2 Snapshot Operation ................................................................................................................................................. 101 4.2.1 Informational Messages ................................................................................................................................... 101 4.2.2 Warning Messages ........................................................................................................................................... 104 4.2.3 Error Messages ................................................................................................................................................ 106 Chapter 5 Notes ................................................................................................................................................................ 123 5.1 Data Replication Operations .................................................................................................................................... 123 5.2 Snapshot Operations ................................................................................................................................................ 126 Appendix A Volume Layout and Usability ....................................................................................................................... 129 Appendix B FileSystem Option Operating Procedures ................................................................................................... 133 B.1 When Using Data Replication Functions ................................................................................................................ 133 B.2 When Using Snapshot Functions ............................................................................................................................. 141 Appendix C License ............................................................................................................................................................ 148 C.1 Flex License............................................................................................................................................................. 148 Index ......................................................................................................................................................................... 149 i 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) 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 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 Chapter 1 Product Overview 1.2 Function Overview 1.2.1 Data Replication Function (1) Separation function (File system synchronization + Separation)  In a VxFS (with VxVM)/ext (with LVM) environment, separation can be performed after performing data synchronization through a file system freeze without unmounting the VxFS/ext file system on a disk group or volume group.  In a VxFS (without VxVM)/ext (without LVM) environment, separation can be performed after performing data synchronization through a file system freeze without unmounting the VxFS/ext 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 file system in the ATgroup. (2) Replication function (Disk synchronization)  In a VxFS (with VxVM)/ext (with LVM) environment, this function replicates from the paired MV configuring the disk group to RV.  In a VxFS (without VxVM)/ext (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 Separate VxFS VxVM (File system management) (Disk group (DG) management) Re-replicate DG Disk array FileSystem Option Freeze uses VxVM disk Unfreeze group management functions. Separate OS commands from another server can be used to mount and use RV. RV MV Replicate Disk group FS synchronous disk separation Replication function Figure 1-1 Data Replication Function in VxFS (with VxVM) Environment 2 Chapter 1 Product Overview Linux FileSystem Option ControlCommand Separate VxFS PathManager (File system management) (Redundant path management) Re-replicate Freeze Unfreeze FSCK Mount (*1) For PathManager installed system, operation is executed by PathManager special file. Separate Disk array MV RV FS synchronous disk separation Replicate Replication function Mount option (*1) Figure 1-2 Data Replication Function in VxFS (without VxVM) Environment 3 Chapter 1 Product Overview Linux FileSystem Option Separate VxVM VxFS ControlCommand (Disk group (DG) management) Freeze Re-replicate Atomic Group Unfreeze Separate DG DG MV MV FS synchronous disk separation Replicate function FileSystem Option uses VxVM disk group management functions. DG DG RV RV Replicate Disk array Main site Backup site Figure 1-3 Data Replication Function for Specified ATgroup (DG) Linux FileSystem Option ControlCommand Separate EXT LVM (File system management) (Disk group (VG) management) Re-replicate FileSystem Option Freeze uses LVM disk Unfreeze group management functions. VG Disk array Separate OS commands from another server can be used to mount and use RV. RV MV Replicate Volume group FS synchronous disk separation Replication function Figure1-4 Data Replication Function in ext (with LVM) Environment 4 Chapter 1 Product Overview Linux FileSystem Option ControlCommand Separate EXT PathManager (File system management) (Redundant path management) Re-replicate FSCK Mount (*1) Freeze Unfreeze For PathManager installed system, operation is executed by PathManager special file. Separate Disk array MV RV FS synchronous disk separation Replicate Replication function Mount option (*1) Figure1-5 Data Replication Function in ext (without LVM) Environment Linux FileSystem Option Separate LVM EXT ControlCommand (Disk group (VG) management) Freeze Re-replicate Unfreeze Atomic Group Separate VG VG Replicate function VG VG MV MV FS synchronous disk separation FileSystem Option uses LVM disk group management functions. Replicate Disk array Main site RV RV Backup site Figure 1-6 Data Replication Function for Specified ATgroup (VG) 5 Chapter 1 Product Overview 1.2.2 Snapshot Function (1) Snapshot creation function  In a VxFS (with VxVM)/ext (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 file system on the disk group/volume group.  In a VxFS (without VxVM)/ext (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 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) environment, this function deletes a snapshot of a BV configuring the disk group/volume group.  In a VxFS (without VxVM)/ext (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 file system. If SV and LV are linked without being mounted on the same server as the VxFS/ext file system, it will delete the snapshot after unlinking SV and LV. In other cases, it performs only snapshot deletion. 6 Chapter 1 Product Overview Linux FileSystem Option ControlCommand VxFS VxVM (File system management) (Disk group (DG) management) Create/delete snapshots FileSystem Option Freeze uses VxVM disk Unfreeze group management functions. DG Disk array Create snapshots SV BV Disk group OS commands from another server can be used to mount and use SV. Snapshot function Delete snapshots Figure 1-7 Snapshot Function in VxFS (with VxVM)/ext (with LVM) Environment Linux FileSystem Option ControlCommand Create/delete snapshots VxFS (File system management) Freeze Unfreeze FSCK Mount (*1) Create snapshots Disk array BV PathManager For PathManager installed system, operation is executed by PathManager special file. SV Delete snapshots Snapshot function Mount option (*1) Figure 1-8 Snapshot Function in VxFS (without VxVM) Environment 7 Chapter 1 Product Overview Linux FileSystem Option ControlCommand Create/delete snapshots EXT LVM (File system management) (Disk group (VG) management) FileSystem Option Freeze uses LVM volume Unfreeze group management functions. VG Disk array Create snapshots SV BV Volume group OS commands from another server can be used to mount and use SV. Snapshot function Delete snapshots Figure 1-9 Snapshot Function in ext (with LVM) Environment Linux FileSystem Option ControlCommand Create/delete snapshots EXT (File system management) FSCK Mount (*1) Freeze Unfreeze Create snapshots Disk array BV PathManager For PathManager installed system, operation is executed by PathManager special file. SV Delete snapshots Snapshot function Mount option (*1) Figure 1-10 Snapshot Function in ext (without LVM) Environment 8 Chapter 1 Product Overview 1.3 Example of Using Data Replication Function 1.3.1 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 tape s. 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 Replicate Business volume (MV) Separate Replication volume (RV) Figure 1-11 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. 9 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-12 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. 10 Chapter 1 Product Overview 1.3.2 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-13 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. 11 Chapter 1 Product Overview 1.4 Example of Using Snapshot Function 1.4.1 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) LV Link latest generation Create snapshots Replication volume - 1st generation (latest) (SV1) Replication volume - 2nd generation (SV2) Replication volume - 3rd generation (SV3) Figure 1-14 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. 12 Chapter 1 Product Overview 1.4.2 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 Production task Business volume (BV) Test task LV Replication volume (SV1) Application server 3 Search task LV Create snapshots Replication volume (SV2) Link any generation Replication volume (SV3) Replication volume (SV4) Figure 1-15 Parallel Processing by Search Tasks and Test 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. (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. 13 Chapter 1 Product Overview 1.5 Example of Using Data Replication Function and Snapshot Function Together 1.5.1 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 Replicate Business volume (MV)/(BV) Create snapshots Separate Replication volume (RV) Replication volume - 1st generation (Latest) (SV1) Replication volume - 2nd generation (SV2) Replication volume - 3rd generation (SV3) Figure 1-16 Using Data Replication Function and Snapshot Function Together 14 Chapter 1 Product Overview 1.6 Product Configuration This product provides the following commands.  iSMrc_fsseparate:  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 File system synchronous separation in a disk array 15 Chapter 2 Operating Method Chapter 2 Operating Method 2.1 Data Replication Function 2.1.1 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) environment and by specifying the special file name or the logical disk name of the MV in a VxFS (without VxVM)/ext (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) 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 freeze and disk synchronization. The VxFS file system/ext 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 16 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 17 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 18 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/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 (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 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 19 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. 20 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 21 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 22 Chapter 2 Operating Method (11) When volume group MV/RV are paired one-to-one in ext (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 Separating MV: mv_ld01 RV: rv_ld01 *** Unfreeze Start Unfreezing /mnt1 Unfreezing /mnt2 Unfreezing /mnt3 *** Unfreeze Success *** Separate Success (12) When volume group MV/RV are paired one-to-many in ext (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 23 Chapter 2 Operating Method (13) When time-out occurs while separating in ext (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 24 Chapter 2 Operating Method (14) When MV/RV are paired one-to-one in ext (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) 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 25 Chapter 2 Operating Method (16) When time-out occurs while separating in ext (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) 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 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. 26 Chapter 2 Operating Method (18) When specifying ATgroup in ext (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) environment The execution example below is a case in which ATgroup: atg01 is configured by three MVs. The ext 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 27 Chapter 2 Operating Method 2.1.2 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) environment and by specifying the special file name or the logical disk name of the MV in a VxFS (without VxVM)/ext (without LVM) environment. It can be executed in a VxFS (without VxVM)/ext (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) 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 28 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 29 Chapter 2 Operating Method (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 replicated after specifying one pair of MV and RV in options or one or more pairs of MV and RV in a pair file. The execution examples below are cases in which MV: mv_ld01 (logical disk name) is multiply paired with RVs (rv_ld01 through rv_ld03), of these, rv_ld02 is being replicated. A case of specifying one pair of MV and RV in options and that of specifying a pair of MV and RV in a pair file are shown.  Specifying one pair of MV and RV in options root> /usr/sbin/iSMrc_fsreplicate -m ld -o rvvolume=rv_ld02,rvflg=ld mv_ld01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld02 *** Replicate Success  Specifying a pair file root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/iSMrc_fsreplicate -f pair_file.txt *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld02 *** Replicate Success (6) When time-out occurs while replicating in VxFS (without VxVM) environment If, after executing the iSMrc_fsreplicate command, disk pair replication does not end even on exceeding the synchronization waiting time for one disk (default: 60 seconds), a time-out occurs. This is the same as the case in (3). (7) Unmounting RV from the same server in VxFS (without VxVM)) environment When the iSMrc_fsseparate command is executed with the –o mnt option specified, the file system of the separated RV is mounted on the same server as the MV. If the iSMrc_fsreplicate command is executed in this state, it automatically unmounts the file system of the separation target RV and executes replication. 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. Moreover, it is a case in which the file system of rv_ld01 (logical disk name) in the separate state is mounted on /mnt1_tmp1 of the same server as the MV. Executing the iSMrc_fsreplicate command replicates /mnt1_tmp1 after unmounting it. root> /usr/sbin/iSMrc_fsreplicate -m ld mv_ld01 *** Umount RV Start /mnt1_tmp1 is unmounted *** Umount RV Success *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld01 *** Replicate Success 30 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) is configured by disk group dg01 where VxVM volumes lvol1 and lvol2 exist, which are mounted on /mnt1 and /mnt2, respectively. MV: mv_ld02 (logical disk name) is configured by disk group dg02 where VxVM volumes lvol3 and lvol4 exist, which are mounted on /mnt3 and /mnt4, respectively. root> /usr/sbin/iSMrc_fsreplicate -m atg atg01 *** Replicate Start Info: ATgroup is replicating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 *** Replicate 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_fsreplicate -m atg atg01 *** Replicate Start Info: ATgroup is replicating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 MV: mv_ld03 RV: rv_ld03 *** Replicate Success 31 Chapter 2 Operating Method (10) When time-out occurs while replicating in ATgroup specification After executing the iSMrc_fsreplicate command, if the replication of ATgroup does not end even when the synchronization 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 rpl/exec. Warning: Please check ATgroup state. Error: Replicate state error on ATgroup: atg01. iSMrc_fsreplicate: Replicate Failed If ATgroup replication just takes time, this error is not a problem since ATgroup replication will be completed with the passage of time. To confirm whether or not there is an ATgroup fault, check the replicate 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 synchronization waiting time for ATgroup of five minutes is specified. root> /usr/sbin/iSMrc_fsreplicate -m atg -t 300 atg01 (11) When volume group MV/RV are paired one-to-one in ext (with LVM) environment The execution example below is a case in which LV volumes lvol1 through lvol3 exist on a logical disk of volume group vg01 configured on MV: mv_ld01 (logical disk name). root> /usr/sbin/iSMrc_fsreplicate -m vg vg01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld01 *** Replicate Success 32 Chapter 2 Operating Method (12) When volume group MV/RV are paired one-to-many in ext (with VxVM) environment When the MV configuring the volume group and RV are paired one-to-many, the replication 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 replicated. root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/iSMrc_fsreplicate -m vg -f pair_file.txt vg01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld02 *** Replicate Success (13) When time-out occurs while replicating in ext (with LVM) environment Moreover, after executing the iSMrc_fsreplicate command, if the replication of a disk pair does not end even when the synchronization 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: rpl/exec. Warning: Please check volume pair state. Error: Replicate state error on MV: mv_ld01 RV: rv_ld01 iSMrc_fsreplicate: Replicate Failed If the 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 vg -t 300 vg01 33 Chapter 2 Operating Method (14) When MV/RV are paired one-to-one in ext (without LVM) 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 (15) When MV/RV are paired one-to-many in ext (without LVM) environment When MV and RV are paired one-to-many, they are replicated 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 examples below are cases in which MV: mv_ld01 (logical disk name) is multiply paired with RVs (rv_ld01 through rv_ld03), of these, rv_ld02 is being replicated. 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_fsreplicate -m ld -o rvvolume=rv_ld02,rvflg=ld mv_ld01 *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld02 *** Replicate Success  Specifying a pair file root> more pair_file.txt 0:mv_ld01 0:rv_ld02 root> /usr/sbin/iSMrc_fsreplicate -f pair_file.txt *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld02 *** Replicate Success (16) When time-out occurs while replicating in ext (without LVM) environment Moreover, after executing the iSMrc_fsreplicate command, if the replication of a disk pair does not end even when the synchronization waiting time per disk (default: 60 seconds) is exceeded, a time-out occurs. This is the same as the case in (13). 34 Chapter 2 Operating Method (17) When unmounting RV from same server in ext (without LVM) environment When the iSMrc_fsseparate command is executed with the –o mnt option specified, the file system of the separated RV is mounted on the same server as the MV. If the iSMrc_fsreplicate command is executed in this state, it automatically unmounts the file system of the separation target RV and executes replication. 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. Moreover, it is a case in which the system file of rv_ld01 (logical disk name) in the separate state is mounted on /mnt1_tmp1 of the same server as the MV. Executing the iSMrc_fsreplicate command replicates /mnt1_tmp1 after unmounting it root> /usr/sbin/iSMrc_fsreplicate -m ld mv_ld01 *** Umount RV Start /mnt1_tmp1 is unmounted *** Umount RV Success *** Replicate Start Replicating MV: mv_ld01 RV: rv_ld01 *** Replicate Success (18) When specifying ATgroup in ext (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 vg01 where LVM volumes lvol1 and lvol2 exist, which are mounted on /mnt1 and /mnt2, respectively. MV: mv_ld02 (logical disk name) configures volume group vg02 where LVM volumes lvol3 and lvol4 exist, which are mounted on /mnt3 and /mnt4, respectively. root> /usr/sbin/iSMrc_fsreplicate -m atg atg01 *** Replicate Start Info: ATgroup is replicating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 *** Replicate Success (19) When specifying ATgroup in ext (without LVM) environment The execution example below is a case in which ATgroup: atg01 is configured by three MVs. The ext file systems existing on MV: mv_ld01 through mv_ld03 (logical disk name) are mounted on /mnt1 through /mnt3, respectively. root> /usr/sbin/iSMrc_fsreplicate -m atg atg01 *** Replicate Start Info: ATgroup is replicating. ATgroup: atg01 MV: mv_ld01 RV: rv_ld01 MV: mv_ld02 RV: rv_ld02 MV: mv_ld03 RV: rv_ld03 *** Replicate Success 35 Chapter 2 Operating Method (20) When time-out occurs while replicating in ATgroup specification Moreover, after executing the iSMrc_fsreplicate command, if the replication of ATgroup does not end even when the synchronization 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 rpl/exec. Warning: Please check ATgroup state. Error: Replicate state error on ATgroup: atg01. iSMrc_fsreplicate: Replicate Failed If ATgroup replication just takes time, this error is not a problem since ATgroup replication will be completed with the passage of time. To confirm whether or not there is an ATgroup fault, check the replicate state of the 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 synchronization waiting time for ATgroup of five minutes is specified. root> /usr/sbin/iSMrc_fsreplicate -m atg -t 300 atg01 36 Chapter 2 Operating Method 2.2 Snapshot Operations 2.2.1 iSMsc_fscreate Command The iSMsc_fscreate command creates a snapshot of the BV configuring the disk group/volume group or BV specified by a special file name or the logical disk name. It is executed by specifying a disk group name/volume group name in a VxFS (with VxVM)/ext (with LVM) environment and by specifying a special file name or logical disk name of the BV in a VxFS (without VxVM)/ext (without LVM) environment. Moreover, it can be executed by specifying the PathManager or DM-Multipath special file name in a VxFS (without VxVM)/ext (without LVM) environment in which PathManager or DM-Multipath is installed. The iSMsc_fscreate command performs snapshot creation after performing a VxFS/ext file system freeze and disk synchronization. The VxFS/ext file system is unfrozen after snapshot creation. 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 BV/SV 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 BV: bv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. root> Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: /usr/sbin/iSMsc_fscreate -b dg dg01 Create Snapshot Start. Freeze Start. Freezing /mnt1. Freezing /mnt2. Freezing /mnt3. Freeze Success. Creating Snapshot. BV: bv_ld01 SV: sv_ld01 Unfreeze Start. Unfreezing /mnt1. Unfreezing /mnt2. Unfreezing /mnt3. Unfreeze Success. Create Snapshot Success. 37 Chapter 2 Operating Method (2) When disk group BV/SV are paired one-to-many in VxFS (with VxVM) environment When the BV configuring the disk group and SV are paired one-to-many, snapshot creation is performed after specifying pairs of BV and SV 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 BV: bv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. Moreover, it is a case in which BV: bv_ld01 and SVs (sv_ld01 through sv_ld03) are paired one-to-many and a snapshot is being created in sv_ld02 of them. root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fscreate -b dg -f pair_file.txt dg01 Info: Create Snapshot Start. Info: Freeze Start. Info: Freezing /mnt1. Info: Freezing /mnt2. Info: Freezing /mnt3. Info: Freeze Success. Info: Creating Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Unfreeze Start. Info: Unfreezing /mnt1. Info: Unfreezing /mnt2. Info: Unfreezing /mnt3. Info: Unfreeze Success. Info: Create Snapshot Success. (3) When time-out occurs while creating a snapshot 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. : Info: Unfreeze Start. Error: Failed to ioctl(errno=110). Error: Cannot unfreeze /mnt1. Error: Failed to ioctl(errno=110). Error: Cannot unfreeze /mnt2. Error: Failed to ioctl(errno=110). Error: Cannot unfreeze /mnt3. Warning: Unfreeze Timeout! Error: Unfreeze Failed. Error: Create Snapshot Failed. In such a case, since it is possible that a snapshot was created without completing the synchronization of data that was written to the file system, specify a value greater than 60 in the –t option and execute the iSMsc_fscreate command again. The following is a case in which a maximum waiting time for one disk of five minutes is specified. root> /usr/sbin/iSMsc_fscreate -b dg –t 300 dg01 38 Chapter 2 Operating Method (4) When BV/SV are paired one-to-one in VxFS (without VxVM) environment The execution example below is a case in which BV: bv_ld01 (logical disk name) exists and its file system is mounted on /mnt1. root> Info: Info: Info: Info: Info: Info: Info: Info: Info: (5) /usr/sbin/iSMsc_fscreate -b ld bv_ld01 Create Snapshot Start. Freeze Start. Freezing /mnt1. Freeze Success. Creating Snapshot. BV: bv_ld01 SV: sv_ld01 Unfreeze Start. Unfreezing /mnt1. Unfreeze Success. Create Snapshot Success. When BV/SV are paired one-to-many in VxFS (without VxVM) environment When BV and SV are paired one-to-many, a snapshot is created after specifying one pair of BV and SV in options or specifying one or more pairs of BV and SV in a pair file. The execution examples below are cases in which BV: bv_ld01 (logical disk name) exists and its VxFS file system is mounted on /mnt1. Moreover, they are cases in which SVs from sv_ld01 through sv_ld03 are multiply paired with BV: bv_ld01 and a snapshot is being created in sv_ld02. A case of specifying a pair of BV and SV in options and that of specifying a pair of BV and SV in a pair file are shown.  Specifying one pair of BV and SV in options root> Info: Info: Info: Info: Info: Info: Info: Info: Info:  /usr/sbin/iSMsc_fscreate -b ld -o svvolume=sv_ld02,svflg=ld bv_ld01 Create Snapshot Start. Freeze Start. Freezing /mnt1. Freeze Success. Creating Snapshot. BV: bv_ld01 SV: sv_ld02 Unfreeze Start. Unfreezing /mnt1. Unfreeze Success. Create Snapshot Success. Specifying a pair file root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fscreate -f pair_file.txt Info: Create Snapshot Start. Info: Freeze Start. Info: Freezing /mnt1. Info: Freeze Success. Info: Creating Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Unfreeze Start. Info: Unfreezing /mnt1. Info: Unfreeze Success. Info: Create Snapshot Success. 39 Chapter 2 Operating Method (6) When time-out occurs while creating a snapshot in VxFS (without VxVM) environment When file system synchronization and snapshot creation processing take time and they exceed the file system freeze execution time (default: 60 seconds), a time-out occurs. This is the same as the case in (3). (7) When linking SV and LV and mounting the LV on same server in VxFS (without VxVM) environment To link the LV to the SV where a snapshot was created and mount the LV as another file system after snapshot creation, execute them by specifying the –o mnt option. The execution example below is a case in which BV: bv_ld01 (logical disk name) exists and its file system is mounted on /mnt1. Moreover, it is an example of linking the SV: sv_ld01 (logical disk name) to the LV: lv_ld01 (logical disk name) and mounting the LV on the same server as the BV. root> /usr/sbin/iSMsc_fscreate -b ld -o svvolume=sv_ld01,svflg=ld,mnt bv_ld01 Info: Create Snapshot Start. Info: Freeze Start. Info: Freezing /mnt1. Info: Freeze Success. Info: Creating Snapshot. BV: bv_ld01 SV: sv_ld01 Info: Unfreeze Start. Info: Unfreezing /mnt1. Info: Unfreeze Success. Info: Create Snapshot Success. Info: Mount LV Start. Info: Link Success. LV: lv_ld01 SV: sv_ld01 Info: /dev/sdX is mounted on /mnt1_tmp. Info: Mount LV Success. The mount point name to be mounted at this time is the one obtained by appending _tmp to the mount point name of the file system that is mounted on the BV side. 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 the LV using VxFS mount options, try unmounting and remounting. Moreover, if a mount point to which _tmp 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 _tmp is appended in different file systems. 40 Chapter 2 Operating Method (8) When volume group BV/SV are paired one-to-one in ext (with LVM) environment The execution example below is a case in which LVM volumes lvol1 through lvol3 exist on a logical disk of disk group dg01 configured on BV: bv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. root> Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: Info: (9) /usr/sbin/iSMsc_fscreate -b vg vg01 Create Snapshot Start. Freeze Start. Freezing /mnt1. Freezing /mnt2. Freezing /mnt3. Freeze Success. Creating Snapshot. BV: bv_ld01 SV: sv_ld01 Unfreeze Start. Unfreezing /mnt1. Unfreezing /mnt2. Unfreezing /mnt3. Unfreeze Success. Create Snapshot Success. When volume group BV/SV are paired one-to-many in ext (with LVM) environment When the BV configuring the volume group and SV are paired one-to-many, the snapshot is created after specifying BV and SV 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 BV: bv_ld01 (logical disk name) and are mounted on /mnt1 through /mnt3, respectively. Moreover, the multiple SVs sv_ld01 through sv_ld03 are paired with BV: bv_ld01 and, of these, the snapshot is to be created in sv_ld02. root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fscreate -b dg -f pair_file.txt vg01 Info: Create Snapshot Start. Info: Freeze Start. Info: Freezing /mnt1. Info: Freezing /mnt2. Info: Freezing /mnt3. Info: Freeze Success. Info: Creating Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Unfreeze Start. Info: Unfreezing /mnt1. Info: Unfreezing /mnt2. Info: Unfreezing /mnt3. Info: Unfreeze Success. Info: Create Snapshot Success. 41 Chapter 2 Operating Method (10) When time-out occurs while creating a snapshot in ext (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. : Info: Unfreeze Start. Error: Failed to ioctl(errno=110). Error: Cannot unfreeze /mnt1. Error: Failed to ioctl(errno=110). Error: Cannot unfreeze /mnt2. Error: Failed to ioctl(errno=110). Error: Cannot unfreeze /mnt3. Warning: Unfreeze Timeout! Error: Unfreeze Failed. Error: Create Snapshot Failed. In such a case, since it is possible that a snapshot was created without completing the synchronization of data that was written to the file system, specify a value greater than 60 in the –t option and execute the iSMsc_fscreate command again The following is a case in which a maximum waiting time for one disk of five minutes is specified. root> /usr/sbin/iSMsc_fscreate -b vg –t 300 vg01 (11) When BV/SV are paired one-to-one in ext (without LVM) environment The execution example below is a case in which the BV: bv_ld01 (logical disk name) exists and its system file is mounted on /mnt1. root> Info: Info: Info: Info: Info: Info: Info: Info: Info: /usr/sbin/iSMsc_fscreate -b ld bv_ld01 Create Snapshot Start. Freeze Start. Freezing /mnt1. Freeze Success. Creating Snapshot. BV: bv_ld01 SV: sv_ld01 Unfreeze Start. Unfreezing /mnt1. Unfreeze Success. Create Snapshot Success. 42 Chapter 2 Operating Method (12) When BV/SV are paired one-to-many in ext (without LVM) environment When BV and SV are paired one-to-many, a snapshot is created after specifying one pair of BV and SV in options or specifying one or more pairs of BV and SV in a pair file. The execution example below is a case in which the BV: bv_ld01 (logical disk name) exits and its ext file system is mounted on /mnt1. Moreover, the multiple SVs sv_ld01 through sv_ld03 are paired with BV: bv_ld01 and the snapshot is to be created in sv_ld02. A case of specifying one BV and SV pair in options and that of specifying the BV and SV pair in a pair file are shown.  Specifying one BV and SV pair in options root> Info: Info: Info: Info: Info: Info: Info: Info: Info:  /usr/sbin/iSMsc_fscreate -b ld -o svvolume=sv_ld02,svflg=ld bv_ld01 Create Snapshot Start. Freeze Start. Freezing /mnt1. Freeze Success. Creating Snapshot. BV: bv_ld01 SV: sv_ld02 Unfreeze Start. Unfreezing /mnt1. Unfreeze Success. Create Snapshot Success. Specifying a pair file root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fscreate -f pair_file.txt Info: Create Snapshot Start. Info: Freeze Start. Info: Freezing /mnt1. Info: Freeze Success. Info: Creating Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Unfreeze Start. Info: Unfreezing /mnt1. Info: Unfreeze Success. Info: Create Snapshot Success. (13) When time-out occurs while creating a snapshot in ext (without LVM) environment When file system synchronization and snapshot creation 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 (3). 43 Chapter 2 Operating Method (14) When linking SV and LV and mounting the LV on same server in ext (without LVM) environment To link the LV to the SV where a snapshot was created and mount the LV as another file system, execute specifying the –o mnt option. The execution example below is a case in which the BV: bv_ld01 (logical disk name) exists and its file system is mounted on /mnt1. Moreover, it is an example of linking the SV: sv_ld01 (logical disk name) to the LV: lv_ld01 (logical disk name) and mounting the LV on the same server. root> /usr/sbin/iSMsc_fscreate -b ld -o svvolume=sv_ld01,svflg=ld,mnt bv_ld01 Info: Create Snapshot Start. Info: Freeze Start. Info: Freezing /mnt1. Info: Freeze Success. Info: Creating Snapshot. BV: bv_ld01 SV: sv_ld01 Info: Unfreeze Start. Info: Unfreezing /mnt1. Info: Unfreeze Success. Info: Create Snapshot Success. Info: Mount LV Start. Info: Link Success. LV: lv_ld01 SV: sv_ld01 Info: /dev/sdX is mounted on /mnt1_tmp. Info: Mount LV Success. The mount point name to be mounted at this time is the one obtained by appending _tmp to the mount point name of the file system mounted on the BV side. 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 mount options, try unmounting and remounting. Moreover, if a mount point to which _tmp 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 _tmp is appended in different file systems. 44 Chapter 2 Operating Method 2.2.2 iSMsc_fsdelete Command The iSMsc_fsdelete command deletes a snapshot of BV configuring the disk group/volume group or BV specified by a special file name or the logical disk name. It is executed by specifying a disk group name/volume group name in a VxFS (with VxVM)/ext (with LVM) environment and by specifying a special file name or the logical disk name of a BV in a VxFS (without VxVM)/ext (without LVM) environment. Moreover, it can be executed by specifying the PathManager or DM-Multipath special file name in a VxFS (without VxVM)/ext (without LVM) environment in which PathManager or DM-Multipath is installed. (1) When disk group BV/SV are paired one-to-one in VxFS (with VxVM) environment The execution example below is a case in which disk group dg01 is configured of BV: bv_ld01 (logical disk name) and a snapshot has been created in SV: sv_ld01 (logical disk name). root> Info: Info: Info: (2) /usr/sbin/iSMsc_fsdelete -b dg dg01 Delete Snapshot Start. Deleting Snapshot. BV: bv_ld01 SV: sv_ld01 Delete Snapshot Success. When disk group BV/SV are paired one-to-many in VxFS (with VxVM) environment When the BV configuring the disk group and SV are paired one-to-many, snapshot deletion is performed by specifying the combination of BV and SV in a pair file. The execution example below is a case in which the BV: bv_ld01 (logical disk name) is in disk group dg01, the SVs: sv_ld01 through sv_ld03 are paired with the BV, and the snapshot created in sv_ld02 is being deleted. root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fsdelete -b dg -f pair_file.txt dg01 Info: Delete Snapshot Start. Info: Deleting Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Delete Snapshot Success. (3) When BV/SV are paired one-to-one in VxFS (without VxVM) environment The execution example below is a case in which BV: bv_ld01 (logical disk name) and SV: sv_ld01 (logical disk name) are paired one-to-one and the snapshot on SV: sv_ld01, which is linked to LV: lv_ld01 (logical disk name) and mounted on /mnt1_tmp, is being deleted. root> Info: Info: Info: Info: Info: Info: Info: /usr/sbin/iSMsc_fsdelete -b ld bv_ld01 Umount LV Start. /mnt1_tmp is unmounted. Umount LV Success. Unlink Success. LV: lv_ld01 SV: sv_ld01 Delete Snapshot Start. Deleting Snapshot. BV: bv_ld01 SV: sv_ld01 Delete Snapshot Success. 45 Chapter 2 Operating Method (4) When BV/SV are paired one-to-many in VxFS (without VxVM) environment When BV and SV are paired one-to-many, snapshot deletion is performed by specifying a combination of BV and SV or by specifying one or more combinations of BV and SV in a pair file. The execution examples below are cases in which BV: bv_ld01 (logical disk name) and SVs: sv_ld01 through sv_ld03 (logical disk names) are paired one-to-many and the snapshot on SV: sv_ld02, which is linked to LV: lv_ld01 (logical disk name) and mounted on /mnt1_tmp, is being deleted.  Specifying one pair of BV and SV in options root> /usr/sbin/iSMsc_fsdelete -b ld -o svvolume=sv_ld02,svflg=ld bv_ld01 Info: Umount LV Start. Info: /mnt1_tmp is unmounted. Info: Umount LV Success. Info: Unlink Success. LV: lv_ld01 SV: sv_ld02 Info: Delete Snapshot Start. Info: Deleting Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Delete Snapshot Success.  Specifying a pair file root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fsdelete -f pair_file.txt Info: Umount LV Start. Info: /mnt1_tmp is unmounted. Info: Umount LV Success. Info: Unlink Success. LV: lv_ld01 SV: sv_ld02 Info: Delete Snapshot Start. Info: Deleting Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Delete Snapshot Success. (5) When volume group BV/SV are paired one-to-one in ext (with LVM) environment The execution example below is a case in which volume group vg01 is configured of BV: bv_ld01 (logical disk name) and a snapshot has been created in SV: sv_ld01 (logical disk name). root> Info: Info: Info: /usr/sbin/iSMsc_fsdelete -b vg vg01 Delete Snapshot Start. Deleting Snapshot. BV: bv_ld01 SV: sv_ld01 Delete Snapshot Success. 46 Chapter 2 Operating Method (6) When volume group BV/SV are paired one-to-many in ext (with LVM) environment When the BV configuring the volume group and SV are paired one-to-many, snapshot deletion is performed by specifying the combination of BV and SV in a pair file. The execution example below is a case in which the BV: bv_ld01 (logical disk name) is in volume group vg01, the SVs: sv_ld01 through sv_ld03 are paired with the BV, and the snapshot created in sv_ld02 is being deleted. root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fsdelete -b vg -f pair_file.txt vg01 Info: Delete Snapshot Start. Info: Deleting Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Delete Snapshot Success. (7) When BV/SV are paired one-to-one in ext (without LVM) environment The execution example below is a case in which BV: bv_ld01 (logical disk name) and SV: sv_ld01 (logical disk name) are paired one-to-one and the snapshot on SV: sv_ld01, which is linked to LV: lv_ld01 (logical disk name) and mounted on /mnt1_tmp, is being deleted. root> Info: Info: Info: Info: Info: Info: Info: /usr/sbin/iSMsc_fsdelete -b ld bv_ld01 Umount LV Start. /mnt1_tmp is unmounted. Umount LV Success. Unlink Success. LV: lv_ld01 SV: sv_ld01 Delete Snapshot Start. Deleting Snapshot. BV: bv_ld01 SV: sv_ld01 Delete Snapshot Success. 47 Chapter 2 Operating Method (8) When BV/SV are paired one-to-many in ext (without LVM) environment When BV and SV are paired one-to-many, snapshot deletion is performed by specifying a combination of BV and SV or by specifying one or more combinations of BV and SV in a pair file. The execution examples below are cases in which BV: bv_ld01 (logical disk name) and SVs: sv_ld01 through sv_ld03 (logical disk names) are paired one-to-many and the snapshot on SV: sv_ld02, which is linked to LV: lv_ld01 (logical disk name) and mounted on /mnt1_tmp, is being deleted.  Specifying one BV and SV pair in options root> /usr/sbin/iSMsc_fsdelete -b ld -o svvolume=sv_ld02,svflg=ld bv_ld01 Info: Umount LV Start. Info: /mnt1_tmp is unmounted. Info: Umount LV Success. Info: Unlink Success. LV: lv_ld01 SV: sv_ld02 Info: Delete Snapshot Start. Info: Deleting Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Delete Snapshot Success.  Specifying a pair file root> more pair_file.txt 0:bv_ld01 0:sv_ld02 root> /usr/sbin/iSMsc_fsdelete -f pair_file.txt Info: Umount LV Start. Info: /mnt1_tmp is unmounted. Info: Umount LV Success. Info: Unlink Success. LV: lv_ld01 SV: sv_ld02 Info: Delete Snapshot Start. Info: Deleting Snapshot. BV: bv_ld01 SV: sv_ld02 Info: Delete Snapshot Success. 48 Chapter 3 Reference Manual Chapter 3 Reference Manual The following is the FileSystem Option command reference. 3.1 Data Replication Operation 3.1.1 iSMrc_fsseparate Command [ NAME ] iSMrc_fsseparate - File system synchronous separation in a disk array [ SYNOPSIS ]  VxFS (with VxVM)/ext (with LVM) environment iSMrc_fsseparate -m mv_flg [-f file_name] [-t timeout] [-o [rvacc=rv_access][,rvuse=rv_use][,wait | nowait] [,pairnochk]] dg_name  VxFS (without VxVM)/ext (without LVM) environment iSMrc_fsseparate -m mv_flg [-t timeout] [-o [rvvolume=rv_volume,rvflg=rv_flg] [,rvacc=rv_access][,rvuse=rv_use][,wait | nowait][,mnt]] mv_volume iSMrc_fsseparate -f file_name [-t timeout] [-o [rvacc=rv_access][,rvuse=rv_use][,wait | nowait][,mnt]]  ATgroup specification iSMrc_fsseparate -m mv_flg [-t timeout] [-o [wait | nowait][,arrayname=diskarray]] atgroup_name [ DESCRIPTION ]  VxFS (with VxVM)/ext (with LVM) environment The iSMrc_fsseparate command freezes all mounted VxFS/ext file systems that exist in a VxVM disk group/LVM volume group configured on the MV and separates the MV and RV after performing data synchronization. The VxVM disk group name/LVM volume group name is specified in dg_name. If there is no logical volume on the disk group/volume group or if a file system is not mounted, the command just separates the MV and RV without performing a freeze operation. 49 Chapter 3 Reference Manual  VxFS (without VxVM)/ext (without LVM) environment The iSMrc_fsseparate command freezes all mounted VxFS/ext file systems that exist on the MV and separates the MV and RV after performing data synchronization. If a file system on the MV is not mounted, the command just separates the MV and RV. A special file name or the logical disk name of the MV is specified in mv_volume. In a system in which PathManager or DM-Multipath is installed, MV can be specified by the special file name that is supported by PathManager or DM-Multipath. When a special file name is specified for the MV or RV, it is specified in the format/dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number. To execute the iSMrc_fsseparate command in either a VxFS (with VxVM)/ext (with LVM) environment or a VxFS (without VxVM)/ext (without LVM) environment, the pair state of the MV and RV volumes must be replicate synchrony (rpl/sync) (it can also be in replicate execution (rpl/exec)) or in restore synchrony state (rst/sync). To confirm the pair state, check it using the iSMrc_query command (ReplicationControl command) or iSM client.  ATgroup specification The iSMrc_fsseparate command separates the MVs and RVs in all RDR pairs belonging to ATgroup. If the MV belonging to ATgroup is configured by more than one VxVM disk group/LVM volume group, the separate processing is performed after freezing all mounted VxFS/ext file systems on the disk group and performing the data synchronization. If the MV is not configured by a disk group/volume group, the separate processing is performed after freezing all mounted VxFS/ext file systems on the MV and performing the data synchronization. ATgroup name is specified for atgroup_name. [ OPTIONS ] -m mv_flg Specifies the volume type specified with dg_name, mv_volume, or atgroup_name. One of the following can be specified in mv_flg. (VxFS (with VxVM)) environment) dg Disk group name vg Volume group name (ext (with LVM) environment) sfn Special file name (VxFS (without VxVM)/ext (without LVM) environment) ld Logical disk name (VxFS (without VxVM)/ext (without LVM) environment) atg ATgroup name (ATgroup specification) This argument must be specified together with dg_name, mv_volume or atgroup_name. -f file_name When specifying multiple pairs, a text file in which MV/RV pairs are described 50 Chapter 3 Reference Manual (hereafter denoted “pair file”) is prepared and the pair file name is specified in file_name. Operation instructions are specified in arguments. For details on how to describe file_name, refer to [ PAIR FILE DESCRIPTION METHOD ]. -t timeout Specifies the time-out period (in seconds) to freeze a file system. The default is 60 seconds. The maximum time that can be specified is 86400 seconds (one day). If Unfreeze Timeout is displayed in a warning message during the command execution, a disk may have been separated without completing the synchronization of data written to the file system. After executing the iSMrc_fsreplicate command to replicate the separated disk again, try setting this to a greater value and re-executing the iSMrc_fsseparate command. -o options When –o options are specified simultaneously, they are specified by separating with a comma. Do not put spaces around a comma. rvvolume=rv_volume In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the RV volume. Either a special file name or a logical disk name can be specified in rv_volume. rvflg=rv_flg In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the volume type for what is specified in rv_volume. Either of the following can be specified in rv_flg. sfn Special file name (VxFS (without VxVM)/ext (without LVM) environment) ld Logical disk name (VxFS (without VxVM)/ext (without LVM) environment) This argument must be specified together with rvvolume. rvacc=rv_access Specifies RV access restriction. Either of the following can be specified in rv_access. ro Access to RV is read only. rw Input and output are possible for RV. Omitting this argument makes the operation the same as when rw is specified. rvuse=rv_use Specifies the period in which to make the RV available. Any one of the following can be specified in rv_use. 51 Chapter 3 Reference Manual immediate After executing separation, make the RV available immediately while performing MV/RV difference reflection. complete After executing separation, make the RV available after MV/RV difference reflection is complete. default Follow the setting of environment variable RPL_SEP_RVUSE. Environment variables are explained at the end of [ OPTIONS ]. Omitting the argument makes the operation the same as when default is specified. wait | nowait Specifies whether or not to wait for completion of separation. If wait is specified, it waits for MV/RV difference reflection to complete. It also monitors the processing state at a fixed time interval. The monitoring time interval is five seconds. The monitoring time interval for wait can be changed by the environment variable RPL_WATCHDEV. If nowait is specified, there is no waiting for MV/RV difference reflection to complete. Omitting this argument causes the monitoring time interval of one second. Environment variables are explained at the end of [ OPTIONS ]. arrayname=diskarray When specifying an ATgroup, a disk array name (nickname) to be operated can be specified. pairnochk In a VxFS (with VxVM)/ext (with LVM) environment, pairnochk makes operations on the MV/RV that are described in a pair file proceed even if unpaired disks are included in the disk group/volume group or if not all of the MVs configuring the disk group/volume group are described in the pair file. When this argument is omitted, it results in an error if unpaired disks are included in the disk group/volume group or if not all of the MVs configuring the disk group/volume group are described in the pair file. mnt In a VxFS (without VxVM)/ext (without LVM) environment, mnt option mounts the VxFS/ext file system that is on the RV on the same server as the MV after separation. If the MV is mounted using multiple mount points, the VxFS/ext file system that is on the RV is mounted on only one mount point. The mount point of the VxFS/ext file system that is on the RV is determined by the mount point at which the MV first was mounted. The mount point name is the original mount point name with _tmpN (N: an integer > 1) appended. (Environment Variables) RPL_WATCHDEV Can be used to specify the monitoring time interval when wait is specified. The specification range is 1 to 30 seconds (integer). RPL_SEP_RVUSE Sets the operation if rvuse is omitted or if default is specified in rvuse. 52 Chapter 3 Reference Manual IMMEDIATE : Operation is the same as when immediate is specified in rvuse. COMPLETE : Operation is the same as when complete is specified in rvuse. [ PAIR FILE DESCRIPTION METHOD ]  When MV and RV are paired one-to-many or paired one-to-one, specify the MV/RV pair(s) to be separated by specifying it in a file according to the synopsis below. [ SYNOPSIS ] MV type:MV name RV type:RV name MV type: Specifies the MV type using a numerical value or a character string. 0 or “ld” : Logical disk name 1 or “sfn” : Special file name In MV name, specify a name of the type specified by MV type using up to 24 (1-byte) characters. RV type: Specifies the RV type using a numerical value or a character string. 0 or “ld” : Logical disk name 1 or “sfn” : Special file name In RV name, specify a name of the type specified by RV type using up to 24 (1-byte) characters.  The file name of this file is arbitrary.  Pair settings are described starting in column 1.  A line feed code is a record delimiter.  The maximum number of characters that can be used in descriptions in one record is 1024 (1 -byte) characters.  One pair is described per record.  If MV and RV are paired one-to-one, the description of the RV can be omitted.  If MV and RV are paired one-to-many, the description of the RV cannot be omitted.  An MV and an RV are separated by spaces or tabs.  The character “#” through the end of the record is a comment and will be ignored.  If there are errors in the file syntax, the operation is invalid for all pairs described in the file.  Sample descriptions are shown below. #Type:MV 0:mv_ld1 1:/dev/sdar ld:mv_ld2 sfn:/dev/ddx Type:RV sfn:/dev/sdbr ld:rv_ld1 sfn:/dev/ddy [ NOTES ]  All of the MVs configuring the disk group/volume group must be paired with RV. However, if the pairnochk option is specified, processing is possible even if unpaired disks are included.  The target file system is VxFS/ext and the volume management software is VxVM/LVM. Other file systems and volume management are not supported. 53 Chapter 3 Reference Manual  Mirror disk environments are not supported.  Since parallel execution of commands makes it difficult to investigate the cause when an error occurs, it is not recommended.  When a special file name is specified for MV or RV, it is specified in the format /dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number.  When a logical disk name is specified for MV or RV, the name of a logical disk that was named by the iSM configuration setting function is specified.  Specification of the rvuse option (specification of the available period of RV) is valid only in DynamicDataReplication Ver2 and higher.  Mount processing when the mnt option is specified executes the mount command without options. If you wish to perform a mount command in which options are specified, execute the mount command separately. Moreover, if a mount point to which _tmpN (N: Integer > 1) is already appended is in use, executing this command doubly registers the same mount point. As a result, the originally registered mount point is replaced. Try not to use mount points to which _tmpN (N: Integer > 1) is appended in different file systems.  Disk groups/volume groups on the root disk are not supported. Moreover, commands must not be executed for disk groups/volume groups on the root disk.  Disk operation information at the time of command execution is not logged to syslog.  Operation for the pairs registered in ATgroup cannot be performed. [ RETURN VALUE ] 0: Terminated normally 1: Terminated abnormally for other than incorrect option 2: Terminated abnormally for incorrect option [ REFERENCES ] 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) ControlCommand Command Reference PathManager User’s Manual (Linux) Messages Handbook Manual Guide 54 Chapter 3 Reference Manual 3.1.2 iSMrc_fsreplicate Command [ NAME ] iSMrc_fsreplicate - Replication in a disk array [ SYNOPSIS ]  VxFS (with VxVM)/ext (with LVM) environment iSMrc_fsreplicate -m mv_flg [-f file_name] [-t timeout] [-o [cprange=copy_range][,cpmode=copy_mode] [,rvacc=rv_access][,polling=## | wait | nowait] [,pairnochk]] dg_name  VxFS (without VxVM)/ext (without LVM) environment iSMrc_fsreplicate -m mv_flg [-t timeout] [-o [rvvolume=rv_volume,rvflg=rv_flg] [,cprange=copy_range][,cpmode=copy_mode] [,rvacc=rv_access][,polling=## | wait | nowait]] mv_volume iSMrc_fsreplicate -f file_name [-t timeout] [-o [cprange=copy_range][,cpmode=copy_mode] [,rvacc=rv_access][,polling=## | wait | nowait]]  ATgroup specification iSMrc_fsreplicate -m mv_flg [-t timeout] [-o [atmode=atomic_mode] [,cprange=copy_range][,cpmode=copy_mode] [,polling=## | wait | nowait][,arrayname=diskarray]] atgroup_name [ DESCRIPTION ]  VxFS (with VxVM)/ext (with LVM) environment The iSMrc_fsreplicate command replicates a separated RV on the MV. The name of the VxVM disk group/ext volume group configured by the MV is specified in dg_name.  VxFS (without VxVM)/ext (without LVM) environment The iSMrc_fsreplicate command replicates a separated RV on the MV. A special file name or the logical disk name of the MV is specified in mv_volume. If there is a VxFS/ext file system configured on the RV in the separate state and it is mounted, this command performs replication after unmounting it. When a special file name is specified for MV or RV, it is specified in the format/dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number. 55 Chapter 3 Reference Manual  ATgroup specification The iSMrc_fsreplicate command replicates from MV to RV for all RDR pairs belonging to ATgroup. ATgroup name is specified in atgroup_name. It is recommended that you use the iSMrc_fsreplicate command if execution of the iSMrc_fsseparate command fails and you wish to return to the original state. [ OPTIONS ] -m mv_flg Specifies the volume type for what is specified in dg_name, mv_volume, or atgroup_name. One of the following can be specified in mv_flg. (VxFS (with VxVM) environment) dg Disk group name vg Volume group name (ext (with LVM) environment) sfn Special file name (VxFS (without VxVM)/ext (without LVM) environment) ld Logical disk name (VxFS (without VxVM)/ext (without LVM) environment) atg ATgroup name (ATgroup specification) This argument must be specified together with dg_name, mv_volume, or atgroup_name. -f file_name When specifying multiple pairs, a text file in which MV/RV pairs are described (hereafter denoted “pair file”) is prepared and the pair file name is specified in file_name. Operation instructions are specified in arguments. For details on how to describe file_name, refer to [ PAIR FILE DESCRIPTION METHOD ]. -t timeout For other than ATgroup specification, specifies the maximum completion time per disk for the iSMrc_fsreplicate command. For ATgroup specification, specifies the maximum completion time of ATgroup. The default is 60 seconds. The maximum time that can be specified is 86400 seconds (one day). The iSMrc_fsreplicate command makes processing wait until the pair state of the replicated disk or ATgroup completes synchronization or the time that is set here elapses. If synchronization does not complete within the time set here, it displays an error. If synchronization of a disk pair or ATgroup just takes time, this error is not a problem since disk synchronization will be completed with the passage of time. To confirm the sync state of the disks or ATgroup and whether or not there is a disk fault, check the sync state of the disk pair or 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 the iSMrc_fsreplicate command after 56 Chapter 3 Reference Manual specifying a value greater than 60 in the –t option. -o options When –o options are specified simultaneously, they are specified separated by a comma. Do not put spaces around a comma. rvvolume=rv_volume In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the RV volume. Either a special file name or a logical disk name can be specified in rv_volume. rvflg=rv_flg In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the volume type for what is specified in rv_volume. Either of the following can be specified in rv_flg. sfn Special file name (VxFS (without VxVM)/ext (without LVM) environment) ld Logical disk name (VxFS (without VxVM)/ext (without LVM) environment) This argument must be specified together with rvvolume. cprange=copy_range Specifies the range to be copied from the MV to the RV. Either of the following can be specified in copy_range. diff Replicates only places on the MV that were updated since the separation from the MV to the RV. full Replicates all areas of the MV to the RV. Omitting this argument makes the operation the same as when diff is specified. cpmode=copy_mode Specifies the method of update reflection of updates made from the MV to RV. One of the following can be specified in copy_mode. sync Synchronous copy mode semi Semi synchronous copy mode bg Background copy state Omitting this argument makes the operation the same as when sync is specified. rvacc=rv_access This specifies RV access restriction. Either of the following can be specified in rv_access. ro Access to RV is Read Only. nr Access to RV is not allowed. Omitting this argument makes the operation the same as when nr is specified. 57 Chapter 3 Reference Manual atmode=atomic_mode This specifies atomic break mode for ATgroup. Either of the following can be specified in atomic_mode. stop MV access stop When atomic break activates, ATgroup sync state changes to Rpl/suspend state and each pair becomes abnormal suspend state. In this case, I/O for MV is refused and terminates abnormally. When using RV, it is necessary to perform forced separation on the user side. I/O for MV is enabled by Separate. continue MV access continue When atomic break activates, ATgroup sync state changes to Fault state and each pair is separated automatically and becomes fault separation (Fault) state. In this case, I/O for MV is continued. Moreover, it is not necessary to perform separation on the user side. It is the default when this parameter is omitted. When specifying this parameter, it is not allowed to select the background copy mode in cpmode. polling=## | wait | nowait Specifies whether or not to wait for completion of replication. If polling is specified, a time interval for checking for synchronization completion (## seconds) can be specified. If a value that is greater than the value of the -t option is specified in ##, polling will be set to the same value as the one specified in -t. For example, if -t 120 –o polling=300 is specified, polling=120 will be set. Moreover, when this option is specified, since it is necessary to wait ## seconds if synchronization has not completed, the command may end exceeding the time-out period specified in –t option. If wait is specified, it waits for MV/RV difference reflection to complete. It also monitors the processing state at a fixed time interval. The monitoring time interval is five seconds. The monitoring time interval for wait can be changed by the environment variable (RPL_WATCHDEV). If nowait is specified, there is no waiting for MV/RV difference reflection to complete. Omitting this argument causes the monitoring time interval of one second. Environment variables are explained at the end of [ OPTIONS ]. arrayname=diskarray When specifying ATgroup, disk array name (nickname) to be operated can be specified. 58 Chapter 3 Reference Manual pairnochk In a VxFS (with VxVM)/ext (with LVM) environment, pairnochk makes operations on the MV/RV that are described in a pair file proceed even if unpaired disks are included in the disk group/volume group or if not all of the MVs configuring the disk group/volume group are described in the pair file. When this argument is omitted, there is an error if unpaired disks are included in the disk group/volume group or if not all of the MVs configuring the disk group/volume group are described in the pair file. (Environment Variables) RPL_WATCHDEV Can be used to specify the monitoring time interval when wait is specified. The specification range is 1 to 30 seconds (integer). [ PAIR FILE DESCRIPTION METHOD ]  When MV and RV are paired one-to-many or paired one-to-one, specify the MV/RV pair(s) to be replicated by specifying it in a file according to the synopsis below. [ SYNOPSIS ] MV type:MV name RV type:RV name MV type: Specifies the MV type using a numerical value or a character string. 0 or “ld” : Logical disk name 1 or “sfn” : Special file name In MV name, specify a name of the type specified by MV type using up to 24 (1-byte) characters. RV type: Specifies the RV type using a numerical value or a character string. 0 or “ld” : Logical disk name 1 or “sfn” : Special file name In RV name, specify a name of the type specified by RV type using up to 24 (1-byte) characters.  The file name of this file is arbitrary.  Pair settings are described starting in column 1.  A line feed code is a record delimiter.  The maximum number of characters that can be used in descriptions in one record is 1024 (1 -byte) characters.  One pair is described per record.  If MV and RV are paired one-to-one, the description of the RV can be omitted.  If MV and RV are paired one-to-many, the description of the RV cannot be omitted.  An MV and an RV are separated by spaces or tabs.  The character “#” through the end of the record is a comment and will be ignored.  If there are errors in the file syntax, the operation is invalid for all pairs described in the file.  Sample descriptions are shown below. #Type:MV 0:mv_ld1 1:/dev/sdar ld:mv_ld2 sfn:/dev/ddx Type:RV sfn:/dev/sdbr ld:rv_ld1 sfn:/dev/ddy 59 Chapter 3 Reference Manual [ NOTES ]  All of the MVs configuring the disk group/volume group must be paired with RV. However, if the pairnochk option is specified, processing is possible even if unpaired disks are included.  Mirror disk environments are not supported.  When a special file name is specified for MV or RV, it is specified in the format /dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number.  When a logical disk name is specified for MV or RV, the name of a logical disk that was named by the iSM configuration setting function is specified.  Disk operation information at the time of command execution is not reported to syslog.  Operation for the pairs registered in ATgroup cannot be performed. [ RETURN VALUE ] 0: Terminated normally 1: Terminated abnormally for other than incorrect option 2: Terminated abnormally for incorrect option [ REFERENCES ] 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) ControlCommand Command Reference PathManager User’s Manual (Linux) Messages Handbook Manual Guide 60 Chapter 3 Reference Manual 3.2 Snapshot Operation 3.2.1 iSMsc_fscreate Command [ NAME ] iSMsc_fscreate - File system synchronization and snapshot creation in a disk array [ SYNOPSIS ]  VxFS (with VxVM)/ext (with LVM) environment iSMsc_fscreate iSMsc_fscreate -b bv_flg dg_name -b bv_flg dg_name [-o cyclic] [-t timeout] -f file_name [-t timeout]  VxFS (without VxVM)/ext (without LVM) environment iSMsc_fscreate iSMsc_fscreate -b bv_flg [-t timeout] [-o [svvolume=sv_volume,svflg=sv_flg | cyclic] [,mnt]] bv_volume -f file_name [-t timeout] [-o mnt ] [ DESCRIPTION ]  VxFS (with VxVM)/ext (with LVM) environment The iSMsc_fscreate command freezes all mounted VxFS/ext file systems that exist on a VxVM disk group/LVM volume group configured on a BV and creates a snapshot after performing data synchronization. The VxVM disk group/LVM volume group name is specified in dg_name. If there is no volume on the disk group/volume group or if a file system is not mounted, this command performs only snapshot creation.  VxFS (without VxVM)/ext (without LVM) environment The iSMsc_fscreate command freezes all mounted VxFS/ext file systems that exist on a BV and creates a snapshot after performing data synchronization. If a file system is not mounted on the BV, this command performs only snapshot creation. A special file name or the logical disk name of the BV is specified in bv_volume. When a special file name is specified for the BV, it is specified in the format /dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number. 61 Chapter 3 Reference Manual [ OPTIONS ] -b bv_flg Specifies the volume type for what is specified in dg_name or bv_volume. One of the following can be specified in bv_flg. (VxFS (with VxVM) environment) dg Disk group name vg Volume group name (ext (with LVM) environment) sfn Special file name (VxFS (without VxVM)/ext (without LVM) environment) ld Logical disk name (VxFS (without VxVM)/ext (without LVM) environment) This argument must be specified together with dg_name or bv_volume. -f file_name When specifying multiple pairs, a text file in which BV/SV pairs are described (hereafter denoted “pair file”) is prepared and the pair file name is specified in file_name. Snapshots are created for all pairs specified in the pair file. In a VxFS (with VxVM)/ext (with LVM) environment, the pairing with the SV where a snapshot is to be created must be described for all BVs configuring the disk group/volume group. If the pairing with SV is one-to-one for all BVs configuring the disk group/volume group, this option can be omitted. If multiple pairs are specified and snapshot creation fails for some pairs, the operation is as follows. In a VxFS (with VxVM)/ext (with LVM) environment), it automatically deletes created snapshots and reports errors. In a VxFS (without VxVM)/ext (without LVM) environment, it reports errors without deleting created snapshots. Be particularly careful if you describe a SV by relative generation to execute the iSMsc_fscreate command and then use the same pair file to execute the iSMsc_fsdelete command, since it will designate a different SV. For details on pair files, refer to [ PAIR FILE DESCRIPTION METHOD ]. -t timeout Specifies the time-out period (in seconds) to freeze a VxFS/ext file system. The default is 60 seconds. The maximum time that can be specified is 86400 seconds (one day). If Unfreeze Timeout is displayed in a warning message during the command execution, a snapshot may have been created without completing the synchronization of data written to the VxFS/ext file system. In a VxFS (with VxVM)/ext (with LVM) environment, re-execute the iSMsc_fscreate command after setting this to a greater value. In a VxFS (without VxVM)/ext (without LVM) environment, delete created snapshots as needed, and then re-execute the iSMsc_fscreate command after setting this to a greater value. 62 Chapter 3 Reference Manual -o options When multiple –o options are specified serially, they are specified by separating with a comma. Inserting a space character before or after the comma is not an allowed syntax. svvolume=sv_volume In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the SV volume. Either a logical disk name or a relative generation can be specified in sv_volume. When specifying relative generations, .-1 is specified as the most recent generation and .-n (n=2, 3, …16) for subsequent generations. If BV and SV are paired one-to-one, this and the svflg option can be omitted together. Inserting a space character before or after “=” is not an allowed syntax. svflg=sv_flg In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the SV volume type. Either of the following can be specified in sv_flg. ld Logical disk name relgen Relative generation This argument must be specified together with svvolume. If BV and SV are paired one-to-one, this and the svvolume option can be omitted together. Inserting a space character before or after "=" is not an allowed syntax. cyclic Setting this argument creates a snapshot in an SV where no snapshot is created. If there are multiple SVs having no snapshot, a snapshot is created in the SV with the smallest logical disk number (LDN). If all SVs have a snapshot, a snapshot is created in the SV of the oldest generation (SV of the chronologically oldest generation among the SVs including those of derived generations having a generation number) excluding guarded SVs and SVs of derived generations without generation number. If BV and SV are paired one-to-one, this can be omitted. mnt In a VxFS (without VxVM)/ext (without LVM) environment, after creating a snapshot, it links with LV and the mount operation is done on the same server as BV. If there are multiple LVs that can be linked, it links using the LV with the smallest logical number. The mount point name is the one which _tmp is appended to the BV mount point name. If the BV is mounted using multiple mount points, the VxFS file system that is on the LV-SV is mounted on only one mount point. The mount point of the VxFS/ext file system that is on the LV-SV is determined by the first mount point on which the BV is mounted. 63 Chapter 3 Reference Manual [ PAIR FILE DESCRIPTION METHOD ]  When BV and SV are paired one-to-many or paired one-to-one, specify the BV/SV pair(s) for snapshot creation in a file according to the synopsis below. [ SYNOPSIS ] BV type:BV name SV type:SV name BV type: Specifies the BV type using a numerical value or a character string. 0 or “ld” : Logical disk name 1 or “sfn” : Special file name In BV name, specify a name of the type specified by BV type using up to 24 (1-byte) characters. SV type: Specifies the SV type using a numerical value or a character string. 0 or “ld” : Logical disk name specification 10 or “relgen” : Relative generation specification 11 or “cyclic” : Cyclic use specification In SV name, specify a name of the type specified by SV type using up to 24 (1-byte) characters.  The file name of this file is arbitrary.  Pair settings are described starting in column 1.  A line feed code is a record delimiter.  The maximum number of characters that can be used in descriptions in one record is 1024 (1 -byte) characters.  One pair is described per record.  If BV and SV are paired one-to-one, the description of the SV can be omitted.  If BV and SV are paired one-to-many, the description of the SV cannot be omitted.  A BV and SV are separated by spaces or tabs.  The character “#” through the end of the record is a comment and will be ignored.  If there are errors in the file syntax, the operation is invalid for all pairs described in the file.  Sample descriptions are shown below. #Type:BV 0:bv_ld1 1:/dev/sdar ld:bv_ld2 sfn:/dev/ddx Type:SV relgen:.-1 ld:sv_ld1 cyclic 64 Chapter 3 Reference Manual [ NOTES ]  All of the BVs configuring the disk group/volume group must be paired with SV.  The target file system is VxFS/ext and the volume management software is VxVM/LVM. Other file systems and volume management are not supported.  Mirror disk environments are not supported.  Since parallel execution of commands makes it difficult to investigate the cause when an error occurs, it is not recommended.  When a special file name is specified for the BV, it is specified in the format /dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number.  When a logical disk name is specified for the BV or SV, the name of a logical disk that was named by the iSM configuration setting function is specified.  Mount processing in which the mnt option is specified executes the mount command without options. If you wish to perform a mount in which options are specified, execute the mount command separately. Moreover, if a mount point to which _tmp 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 _tmp is appended in different file systems. If the BV is mounted using multiple mount points, the VxFS file system that is on the LV-SV is mounted on only one mount point. The mount point of the VxFS file system that is on the LV-SV is determined by the first mount point on which the BV is mounted.  When the mnt option is specified, the SV where to create a snapshot must be in one of the following states.   Snapshot active or inactive  Not in restore execution (rst/exec)  Not linked to LV  Not preserved Disk groups/volume groups on the root disk are not supported. Moreover, commands must not be executed for disk groups/volume groups on the root disk.  Disk operation information at the time of command execution is not reported to syslog. [ RETURN VALUE ] 0: Terminated normally 1: Terminated abnormally for other than incorrect option 2: Terminated abnormally for incorrect option [ REFERENCES ] Snapshot User’s Manual (Function Guide) Snapshot User’s Manual (Installation and Operation Guide for Linux) ControlCommand Command Reference PathManager User’s Manual (Linux) Messages Handbook Manual Guide 65 Chapter 3 Reference Manual 3.2.2 iSMsc_fsdelete Command [ NAME ] iSMsc_fsdelete - Snapshot deletion in a disk array [ SYNOPSIS ]  VxFS (with VxVM)/ext (with LVM) environment iSMsc_fsdelete -b bv_flg dg_name [-f file_name]  VxFS (without VxVM)/ext (without LVM) environment iSMsc_fsdelete iSMsc_fsdelete -b bv_flg [-o svvolume=sv_volume,svflg=sv_flg] bv_volume -f file_name [ DESCRIPTION ]  VxFS (with VxVM)/ext (with LVM) environment The iSMsc_fsdelete command deletes snapshots of BV configuring the VxVM disk group/LVM volume group. The VxVM disk group is specified in dg_name.  VxFS (without VxVM)/ext (without LVM) environment The iSMsc_fsdelete command performs snapshot deletion. If the snapshot to be deleted is mounted as a VxFS/ext file system, it deletes the snapshot after unmounting and unlinking the SV and LV. If the SV and LV are linked without being mounted as a VxFS/ext file system, it deletes the snapshot after unlinking the SV and LV. In cases other than these, it performs snapshot deletion only. A special file name or the logical disk name of the BV is specified in bv_volume. When a special file name is specified, it is specified in the format /dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number. [ OPTIONS ] -b bv_flg Specifies the volume type for what is specified in dg_name or bv_volume. One of the following can be specified in bv_flg. (VxFS (with VxVM) environment) dg Disk group name vg Volume group name (ext (with LVM) environment) sfn Special file name (VxFS (without VxVM)/ext (without LVM) environment) ld Logical disk name (VxFS (without VxVM)/ext (without LVM) environment) This argument must be specified together with dg_name or bv_volume. 66 Chapter 3 Reference Manual -f file_name When specifying multiple pairs, a text file in which pairs of BV and SV are described (hereafter denoted “pair file”) is prepared and the pair file name is specified in file_name. Snapshots are deleted for all pairs specified in the pair file. In a VxFS (with VxVM)/ext (with LVM) environment, the pairing with the SV where a snapshot is to be deleted must be described for all BVs configuring the disk group/volume group. If the pairing with SV is one-to-one for all BVs configuring the disk group/volume group, this option can be omitted. Be particularly careful if you describe a SV by relative generation to execute the iSMsc_fscreate command and then use the same pair file to execute the iSMsc_fsdelete command, since it will designate a different SV. For details on the files to be specified, refer to [ PAIR FILE DESCRIPTION METHOD ]. -o options When multiple –o options are specified serially, they are specified by separating with a comma. Inserting a space character before or after the comma is not an allowed syntax. svvolume=sv_volume In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the SV volume. Either a logical disk name or a relative generation can be specified in sv_volume. When specifying relative generations, .-1 is specified as the most recent generation and .-n (n=2, 3, …16) for subsequent generations. If BV and SV are paired one-to-one, this and the svflg option can be omitted together. Inserting a space character before or after “=” is not an allowed syntax. svflg=sv_flg In a VxFS (without VxVM)/ext (without LVM) environment, this specifies the SV volume type. Either of the following can be specified in sv_flg. ld Logical disk name relgen Relative generation This argument must be specified together with svvolume. If BV and SV are paired one-to-one, this and the svvolume option can be omitted together. Inserting a space character before or after “=” is not an allowed syntax. [ PAIR FILE DESCRIPTION METHOD ]  When BV and SV are paired one-to-many or paired one-to-one, specify the BV/SV pair(s) for snapshot deletion in a file according to the synopsis below. [ SYNOPSIS ] BV type:BV name SV type:SV name BV type: Specifies the BV type using a numerical value or a character string. 0 or “ld” : Logical disk name 67 Chapter 3 Reference Manual 1 or “sfn” : Special file name In BV name, specify a name of the type specified by BV type using up to 24 (single byte) characters. SV type: Specifies the SV type using a numerical value or a character string. 0 or “ld” : Logical disk name specification 10 or “relgen” : Relative generation specification In SV name, specify a name of the type specified by SV type using up to 24 (single byte) characters.  The file name of this file is arbitrary.  Pair settings are described starting in column 1.  A line feed code is a record delimiter.  The maximum number of characters that can be used in descriptions in one record is 1024 (1-byte) characters.  One pair is described per record.  If BV and SV are paired one-to-one, the description of SV can be omitted.  If BV and SV are paired one-to-many, the description of SV cannot be omitted.  A BV and SV are separated by spaces or tabs.  The character “#” through the end of the record is a comment and will be ignored.  If there are errors in the file syntax, the operation is invalid for all pairs described in the file.  Sample descriptions are shown below. #Type:BV 0:bv_ld1 1:/dev/sdab ld:bv_ld2 sfn:/dev/sdda Type:SV relgen:.-1 ld:sv_ld1 relgen:.-2 [ NOTES ]  All of the BVs configuring the disk group/volume group must be paired with SV.  Mirror disk environments are not supported.  When a special file name is specified for BV, it is specified in the format dev/dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number.  When a logical disk name is specified for BV or SV, the name of a logical disk that was named by the iSM configuration setting function is specified.   The SV where to delete a snapshot must be in one of the following states.  Snapshot active  Not in restore execution (rst/exec)  Not linked to LV (If using snapshot on different server than BV)  Not preserved Disk operation information at the time of command execution is not reported to syslog. 68 Chapter 3 Reference Manual [ RETURN VALUE ] 0: Terminated normally 1: Terminated abnormally for other than incorrect option 2: Terminated abnormally for incorrect option [ REFERENCES ] Snapshot User’s Manual (Function Guide) Snapshot User’s Manual (Installation and Operation Guide for Linux) ControlCommand Command Reference PathManager User’s Manual (Linux) Messages Handbook Manual Guide 69 Chapter 4 Output Messages Chapter 4 Output Messages 4.1 Data Replication Operation This section explains the messages that are output when using data replication operation commands (iSMrc_fsseparate, iSMrc_fsreplicate). Informational messages are displayed in standard output and warnings and error messages in standard error output. When parameters are entered in brackets as in or , it means that parameter values that are not fixed are displayed. (The brackets “< >” are not actually output.) For details on parameter values, refer to the [Explanation] field. 4.1.1 Informational Messages All lvols are not mounted Explanation: There is no volume to mount or freeze. Only separation is executed. Freezing Explanation: A VxFS/ext file system is being frozen. aaa...a: Mount point name No volume to be frozen. Explanation: There is no volume to freeze. Only separation is executed. Replicating MV: Explanation: A pair is being replicated. aaa...a: Logical disk name of MV bbb...b: Logical disk name of RV Separating MV: Explanation: RV: RV: A pair is being separated. aaa...a: Logical disk name of MV bbb...b: Logical disk name of RV 70 Chapter 4 Output Messages Unfreezing Explanation: A VxFS/ext file system is being unfrozen. aaa...a: Mount point name [Added for V4.1] Info: ATgroup is replicating. ATgroup: MV: RV: : : : : Explanation: An ATgroup is being replicated. Logical disk names of all MVs and RVs in the ATgroup are displayed. aaa...a: ATgroup name bbb...b: Logical disk name of MV ccc...c: Logical disk name of RV Info: ATgroup is separating. ATgroup: MV: RV: : : : : Explanation: An ATgroup is being separated. Logical disk names of all MVs and RVs in the ATgroup are displayed. aaa...a: ATgroup name bbb...b: Logical disk name of MV ccc...c: Logical disk name of RV 71 Chapter 4 Output Messages 4.1.2 Warning Messages Warning: fsck failed on . Explanation: Execution of fsck failed. aaa...a: Measures: Special file name Refer to the /tmp/.hafss.log file and check for the cause of the error. Also check whether other error messages are displayed in standard output or there are other causes such as I/O error in syslog. Warning: Cannot mount . Explanation: Mount processing failed. aaa...a: Measures: Special file name of RV Refer to the previous error message and check whether the mount point exists and the directory state is correct. Also check whether or not there are other causes of the error such as in /tmp/.hafss.log file and I/O error in syslog. After eliminating the cause of mount failure, re-mount by manually executing the fsck/mount command for the RV. Warning: Sync Timeout! Warning: The pair is still in synchronizing state: . Warning: Please check volume pair state. Explanation: A time-out occurred in a separation or replication execution request. aaa...a: Measures: State  sep/exec: Separate execution  rpl/exec: Replicate execution Use the iSMrc_query command or iSM client to check the pair state of the MV and RV. Sometimes the differential quantity of volume of the MV and RV is great and synchronization completion in separation or replication takes time. In this case, if it is confirmed that synchronization ends on its own, there is no problem and separation or replication will be executed. Warning: Cannot get pair information of some disks of the DG Explanation: There are unpaired volumes in the disk group. Measures: Check pair states and the pair file and re-execute the command. If the result of checking is that there is no problem, ignore this message. 72 Chapter 4 Output Messages Warning: Number of MVs listed in the file is different from the DG Explanation: Some of the MVs configuring the disk group are not specified in the pair file. Measures: Check the pair file and re-execute the command. If the result of checking is that there is no error, ignore this message. Warning: Warning: Warning: Warning: Unfreeze Timeout! Separate is not correctly done. You must merge again and please retry to separate setting larger value of timeout. Explanation: Separation ended but a time-out was detected in the file system unfreeze processing. Separation may have been done without file system synchronization being performed. Measures: Execute the iSMrc_fsreplicate command to re-execute synchronization processing of the separated disk. Afterwards, set a greater time-out value and re-execute the iSMrc_fsseparate command. [Added for V4.1] Warning: Sync Timeout! Warning: The ATgroup is still in synchronizing state: . Warning: Please check ATgroup state. Error: state error on ATgroup: . Explanation: A time-out occurred in a request for execution of separation or replication of an ATgroup. aaa...a: ATgroup state  ATgroup sep/exec: The ATgroup is in the state of separate execution. Separation has been started for all pairs in the ATgroup, and the pair state is separate (sep/exec) or separate (separated).  ATgroup rpl/exec: ATgroup sync state. Replication has been started for all pairs in the ATgroup, and the pair state is replicate (rpl/exec) or replicate (rpl/sync). bbb...b: ccc...c: Measures: Operation of the ATgroup  Separate  Replicate ATgroup name Check the ATgroup state using the iSMrc_query command or the iSM client. The difference may be great, which may cause synchronous completion of separation or replication to take time. In this case, confirm that synchronization is completed. That means that separation or replication has been executed. 73 Chapter 4 Output Messages [Added for V7.2.001] Warning: ext and vxfs are using at the same time! Explanation: The ext and VxFS file systems cannot be used at the same time. Measures: Handle it by checking the file system type. [Added for V7.2.001] Warning: Cannot get pair information of some disks of the volume group. Explanation: There are unpaired volumes in the volume group. Measures: Check pair states and the pair file and re-execute the command. If the result of checking is that there is no problem, ignore this message. 74 Chapter 4 Output Messages 4.1.3 Error Messages /usr/sbin/iSMrc_query command error (retcode = ) Explanation: An error occurred in the iSMrc_query command. aaa...a: Measures: Return code Check the /tmp/.hafss.log file and eliminate the cause of the error. [Revised for V7.2] Can not mount RV under VxVM environment or LVM environment Explanation: A mount specification cannot be specified together with a disk group name/volume group name. Measures: Specify the correct options and re-execute the command. Error: command timeout. Explanation: A time-out occurred in system command execution. aaa...a: Measures: Command name  /sbin/fsck  /bin/mount  /bin/rpm  /bin/umount  /usr/sbin/vxdisk  /usr/sbin/vxprint Check the operating environment of the system command and eliminate the cause of the error. Error: command error(retcode = ) Explanation: A command error occurred. aaa...a: bbb...b: Measures: Command name  /sbin/fsck  /bin/mount  /bin/umount  /usr/sbin/vxdisk  /usr/sbin/vxprint Return code Check the return code and /tmp/.hafss.log file and eliminate the cause of the error. 75 Chapter 4 Output Messages Cannot allocate memory for putenv (). Explanation: There is insufficient memory. Measures: End unnecessary processes in the system and re-execute the command. Error: Cannot get pair information of MV: . Explanation: Obtaining pair information failed. aaa...a: Measures: Logical disk name or special file name of MV Handle it by referring to the previously displayed error. Error: Cannot open : Explanation: Measures: Opening of a file system in freeze or unfreeze processing failed. aaa...a: Mount point name bbb...b: Error message Check the error message and eliminate the cause of the fault. Error: Cannot read from the file. Explanation: Reading of the pair file failed. Measures: Handle it by checking pair file access rights and other messages. Error: Failed to get the device information of DiskGroup: from the output of command /usr/sbin/vxdisk. Error: Please check the status of DiskGroup: . Explanation: Obtaining disk group device information failed. aaa...a: Measures: Disk group name Check the state of the disk group. Error: Failed to open file: . Explanation: Opening of the pair file failed. aaa...a: Measures: File name Handle it by checking pair file access rights and other messages. [Added for V7.2.001] Error: Failed to ioctl(errno= ). Error: Cannot freeze . Explanation: Measures: An error occurred in VxFS/ext file system freeze processing. aaa...a: Error message bbb...b: Mount point Refer to the error message and eliminate the cause of the error. 76 Chapter 4 Output Messages [Added for V7.2.001] Error: Failed to ioctl(errno= ). Error: Cannot unfreeze . Explanation: Measures: An error occurred in VxFS/ext file system unfreeze processing. aaa...a: Error message bbb...b: Mount point Refer to the error message and eliminate the cause of the error. Error: is failed (retcode = ) Explanation: An error occurred in a data replication function. aaa...a: bbb...b: Measures: Function name  iSMrc_query  iSMrc_replicate  iSMrc_separate  iSMrc_lsdev  iSMrc_lsdev_seek  iSMrc_fsexec_atgsense  iSMrc_queryEx Error code (Return code) Check the error code (explained in Table 4-1 “Error Codes Returned by Data Replication Function”) and eliminate the cause of the error. Table 4-1 Error Codes Returned by Data Replication Function Value Explanation 1 An error occurred on issuance of a SCSI command. 2 An invalid value was specified in a parameter. 3 Semi synchronous copy mode was specified for DynamicDataReplication. 4 An error occurred in the interface with the system. 5 Obtaining disk group volume information failed. 6 The number of MV and RV pairs is inconsistent. 7 An error occurred in SCSI open processing. 8 An error occurred in SCSI close processing. 9 A specified volume does not exist in the volume list. 10 The type of a specified volume is not supported. 11 MV and RV are not paired. 12 The RV was omitted when multiple RVs exist for the MV. 13 DynamicDataReplication is not supported. 14 RemoteDataReplication is not supported. 15 There is no DynamicDataReplication license. Or, the license does not meet the requirements (capacity, version, etc.). 16 There is no RemoteDataReplication license. Or, the license does not meet the requirements (capacity, version, etc.). 17 DynamicDataReplication and RemoteDataReplication are not supported. 77 Chapter 4 Output Messages Value Explanation 18 There is no DynamicDataReplication or RemoteDataReplication license. 19 Obtaining disk group volume information failed. 20 Obtaining ATgroup information failed. For details, refer to the return value (for expansion). 21 The format of the volume list is invalid. 22 Opening of the volume list failed. 23 Obtaining an exclusive lock on a resource using a lock control file failed. The target resource is exclusively locked. 24 Releasing an exclusive lock on a resource using a lock control file failed. 25 This volume cannot be used for data replication. 27 The MV or RV is linked. 28 DynamicSnapVolume is not supported. 29 There is no DynamicSnapVolume license. Or, the license does not meet the requirements (capacity, version, etc.). 30 A volume that is registered in an ATgroup cannot be specified. For details, refer to the return value (for expansion). 31 The ATgroup is in a state in which the requested operation is impossible. For details, refer to the return value (for expansion). 32 The ATgroup or some pairs already are in the requested state. For details, refer to the return value (for expansion). 33 The specified pair has not been replicated. 34 The specified pair has not been separated. 35 The ATgroup cannot accept a request due to Atomic Break activity. 36 ATgroup creation or deletion failed. For details, refer to the return value (for expansion). 37 Pair registration or deregistration in an ATgroup failed. For details, refer to the return value (for expansion). 38 RemoteDataReplication/DisasterRecovery is not supported. 39 There is no RemoteDataReplication/DisasterRecovery license. 42 A volume is mounted. 46 The license required for the command execution does not exist. 48 The volume list is locked (creating or updating). 49 The volume list has been updated. Or a volume list does not exist. 50 Besides specified pairs, there are pairs in the Restore state or Separate state. 51 An upper pair in which the MV of the specified pair is the RV is not in the Separate state. 52 A lower pair in which the RV of the specified pair is the MV is not in the Separate state. 53 The data replication function of the disk array is in the freeze state. 54 The specified pair is in the Suspend state. 55 The specified pair is replicate synchronous. 56 The specified pair is in the Restore state. 57 The specified pair is in the Separate state. 58 The specified pair is in a background copy state. 59 The specified pair is not in the sync state (Replicate state or Restore state). 60 The specified pair or volume is not in a state to accept requests. 61 Memory reservation failed. 62 A snapshot operation is being executed for the specified volume. 63 The specified pair is in a foreground copy state. 78 Chapter 4 Output Messages Value Explanation 64 ReplicationControl is not installed. 65 Replication or restoration cannot be executed simultaneously for the same specified volume. 66 Reading of the signature failed. 67 Writing of the signature failed. 70 Reading from a disk failed. 71 Writing to a disk failed. 73 Restore (protect) function is not supported by the disk array. 74 Separate (immediate) function is not supported by the disk array. 75 The specified pair already is in the Replicate state. 76 The specified pair already is in the Restore state. 77 The specified pair already is in the Separate state. 78 The specified pair is not in the Restore state. 79 Forced Separate cannot be executed for the RV of the specified pair. 82 An abnormality was detected in the RDR link path. 83 The specified disk array has not been frozen. 84 The specified pair or disk array is not under iSM (replication management) management. 85 iSM (replication management) monitoring is stopped for the specified pair or disk array. 86 iSM (replication management) cannot be used because there is no DynamicDataReplication/RemoteDataReplication license. 87 Because there are two or more logical disk names as specified, operations by iSM (replication management) are impossible. 88 Because the specified disk array name was not found, operations by iSM are impossible. 89 Because operating conditions for pair setting are not satisfied, pair setting by iSM (replication management) is impossible. 90 The operation target has a locked logical disk. 91 The operation target has a protected logical disk. 92 RV cannot be set to RW enabled in a state other than separated (separated). 93 An abnormality occurred in iSM (replication management). 94 Obtaining a SCSI address failed. 95 Operation is impossible because the specified pair is separating. 96 An abnormality was detected in a message from iSM (replication management). 97 Because the specified logical disk was not found, operations by iSM (replication management) are impossible. 98 Opening the target-control volume list failed. 99 Closing the target-control volume list failed. 100 A needed function to the disk array is not supported by the disk array. 101 A needed function cannot be used because iSM (replication management) is an old version. 102 A needed function to the iSM (replication management) is not supported. 120 Access to the specified volume is not permitted. 129 A request cannot be accepted because the specified pair is in the snapshot restore fault state. 254 An abnormality was detected during processing. 79 Chapter 4 Output Messages Error: Line is too long. Explanation: The number of bytes is too long for a line in a pair file. aaa...a: Measures: Line number Specify it using no more than 1024 bytes per line. Error: Line : failed to get pair information of MV: . Explanation: Measures: Obtaining information for a pair described in the pair file failed. aaa...a: Line number bbb...b: Logical volume name or special file name of MV Check line of the pair file and eliminate the cause of the error. Error: Line : MV has RVs, RV name must be specified. Explanation: The RV was omitted in a pair file description. Since the MV is paired with multiple RVs, the RV cannot be omitted. Measures: aaa...a: Line number bbb...b: Logical volume name or special file name of MV ccc...c: Number of RVs that are paired with the MV Add a description of the RV to the pair file and re-execute the command. Error: Line : RV name is incorrect. Explanation: Measures: The specification of an RV described in the pair file is incorrect. aaa...a: Line number bbb...b: Logical disk name or special file name of RV Revise the RV specification in the pair file and re-execute the command. Error: Line : This pair is already specified in the file. Explanation: The same pair is specified in the pair file multiple times. aaa...a: Measures: Line number Delete duplicate pair descriptions from the pair file and re-execute the command. Error: Line : unknown format. Explanation: There is an error in a pair file description. aaa...a: Measures: Line number Correctly describe the pair file and re-execute the command. 80 Chapter 4 Output Messages Error: Line : volume name is too long. Explanation: A volume name that is described in the pair file is too long. aaa...a: Measures: Line number Correctly describe the volume name in the pair file and re-execute the command. Error: MV: cannot be recognized by OS. Explanation: The MV is not recognized by the operating system. aaa...a: Measures: Logical volume name of MV Re-execute the command in a state in which the MV is recognized by the operating system and ReplicationControl. Error: MV has RVs, RV name must be specified. Explanation: The RV was omitted. Since the MV is paired with multiple RVs, the RV cannot be omitted. Measures: aaa...a: Logical volume name or special file name of MV bbb...b: Number of RVs paired with the MV Correctly specify the RV and re-execute. Error: MV: has more than one RV. Explanation: The MV is paired with multiple RVs. aaa...a: Measures: Logical volume name or special file name of MV Check the previously displayed message and eliminate the cause of the error. Error: : specified has been mounted. SFN: Explanation: MNTPT: The MV or RV specified by the special file name has been mounted by another special file name. Measures: aa: MV or RV bbb...b: Special file name of specified MV or RV ccc...c: Special file name on which MV or RV has been mounted ddd...d: Mount point name Specify the MV or RV by logical volume name. Alternatively, specify the special file on which it has been mounted and re-execute the command. Error: No valid pair in the DG. Explanation: There are no paired disks in the disk group. Measures: Check the state of disks in the disk group. 81 Chapter 4 Output Messages Error: Number of MVs listed in the file is incorrect. Explanation: The number of MVs described in the pair file is not correct. All of the MVs included in the disk group/volume group must be specified. Measures: Revise the description of the pair file and re-execute the command. Error: One or more MVs listed in the file do not belong to the DG: . Explanation: One or more MVs described in the pair file do not configure the disk group. aaa...a: Measures: Disk group name Revise the description of the pair file and re-execute the command. Error: Pair state error on MV: RV: Explanation: Measures: The pair state is not available for replication or separation. aaa...a: Logical disk name or special file name of MV bbb...b: Logical disk name or special file name of RV Check the previously displayed message and eliminate the cause of the error. Error: Replicate state error on MV: RV: Explanation: Measures: This is a disk pair state check error in the iSMrc_fsreplicate command. aaa...a: Logical disk name or special file name of MV bbb...b: Logical disk name or special file name of RV Check the previously displayed message and eliminate the cause of the error. Also check the disk pair state using iSM client or the iSMrc_query command. Error: RV name is incorrect. Explanation: The specified RV is incorrect. aaa...a: Measures: Logical disk name or special file name of RV Correctly specify the RV and re-execute the command. Error: Separate state error on MV: RV: Explanation: Measures: This is a disk pair state check error in the iSMrc_fsseparate command. aaa...a: Logical disk name or special file name of MV bbb...b: Logical disk name or special file name of RV Check the previously displayed message and eliminate the cause of the error. Also check the disk pair state using iSM client or the iSMrc_query command. 82 Chapter 4 Output Messages Error: The duplicate mount point is found. FSNAME1: FSNAME2: MNTPT: Explanation: Processing is impossible because another file system has been mounted using the same name as the mount point on which the target file system of an operation is being mounted. aaa...a: Special file name or VxVM/LVM volume name of operation target bbb...b: Special file name or VxVM/LVM volume name of file system whose mount point is duplicated by ccc...c: Measures: Duplicated mount point Re-execute the command after unmounting the duplicate mount point. Error: The last line of the file does not terminate with CR. Explanation: There is no line feed code in the last line of the pair file. Measures: Add a line feed code and re-execute the command. Error: Too many file systems mounted. Explanation: File systems that need unmount or freeze processing exceed the limit. Measures: If specified in a pair file, split the pair file and re-execute. If a disk group/volume group is specified, replication cannot be executed. Execute unmount processing manually. Error: Too many mount points in the system (/proc/mounts is truncated). Explanation: The file systems that are mounted in the system exceed the limit. Whether the limit is exceeded can be confirmed from the contents of the /proc/mounts file. If “# truncated” is stored at the end of the /proc/mounts file, the limit has been exceeded. Measures: Upon checking the system mount status, manually execute unmount processing. Error: Volume is in separate state ! Explanation: The specified volume has already been separated. Measures: Check the disk pair state using the iSMrc_query command or iSM client and execute the iSMrc_fsseparate command in a state in which replication has completed. Error: Volume is incorrect state ! Explanation: During the command execution, the disk pair activity state became a state in which separation/replication is not possible. Measures: Check the disk pair state using the iSMrc_query command or iSM client. 83 Chapter 4 Output Messages Error: Volume is not foreground or background copy state ! Explanation: The copy control state of the disk to be separated by iSMrc_fsseparate is not foreground copy state or background copy state. Measures: Execute the iSMrc_fsseparate command in a foreground copy state or background copy state. Error: Volume is not separated ! Explanation: The activity state of the disk to be replicated is not Separate state. Measures: Execute the iSMrc_fsreplicate command after making it replicate synchronous. Error: Volume is not sync state ! Explanation: The activity state of the pair to be separated or replicated is not a state in which the specified command can be executed. Measures: Check the activity state of the pair and re-execute the command after making it a state in which the command can be executed. Error: Volume is replicate syncing state now ! Explanation: The disk to be replicated is undergoing replicate synchronous execution. Measures: Try executing the command after confirming a sync state of the disk using iSM client or the like. Error: VxVM mirroring is found on DiskGroup: . Explanation: The specified disk group has a VxVM mirroring. aaa...a: Measures: Disk group name Operation is not possible for the disk group that is mirrored. Failed to mount RV Explanation: Mounting of the RV failed. Measures: Check the previously displayed message and eliminate the cause of the error. Freeze Failed Explanation: File system freeze processing failed. Measures: Check the previously displayed message and eliminate the cause of the error. 84 Chapter 4 Output Messages [Added for V7.2.001] Error: FS type of is not support. Explanation: The volume file system type is not supported. aaa...a: Measures: File system type to be used Operation is not possible for a file system other than VxFS or ext. Specify a valid file system type and re-execute the command. Invalid DiskGroup name: Explanation: The disk group name is invalid. aaa...a: Measures: Disk group name Specify a valid disk group name and re-execute the command. Invalid timeout value: Explanation: The time-out value specified in the –t option is invalid. aaa...a: Measures: Time-out value Specify a valid time-out value and re-execute the command. Invalid value of environment variable RPL_WATCHDEV: Explanation: The value specified in the environment variable RPL_WATCHDEV is invalid. aaa...a: Measures: Value of environment variable RPL_WATCHDEV Correctly set the environment variable RPL_WATCHDEV and re-execute the command. -m option is incorrect ( is installed). Explanation: If “VxVM” is displayed, it is an environment in which VxVM is installed and only dg can be specified in the -m option. If “SPS” is displayed, it is an environment in which PathManager is installed and dg cannot be specified in the -m option. aaaa: Measures: VxVM or SPS If “VxVM” is displayed, re-execute the command using the command interface of a VxFS (with VxVM) environment. If “SPS” is displayed, re-execute the command using the command interface of a VxFS (without VxVM) environment. Neither target nor file is specified Explanation: Neither a volume specification nor a file specification has been specified. Measures: Correctly specify the options and re-execute the command. 85 Chapter 4 Output Messages No pair found in file: . Explanation: Pairs of MV and RV are not described in the pair file. aaa...a: Measures: Pair file name Describe correct specifications in the pair file and re-execute the command. Replicate Failed Explanation: The replication operation failed. Measures: Check the previously displayed message and eliminate the cause of the error. RV can't be specified when -m option is dg Explanation: When the disk group is specified, RV cannot be described. Measures: Correctly specify the options and re-execute the command. Separate Failed Explanation: The separation operation failed. Measures: Check the previously displayed message and eliminate the cause of the error. umount command error Explanation: File system unmount processing failed. Measures: Check the previously displayed message and eliminate the cause of the error. umount is failed on Explanation: File system unmount processing failed. aaa...a: Measures: Mount point name Check the previously displayed message and eliminate the cause of the error. Unfreeze Failed Explanation: VxFS/ext file system unfreeze processing failed. Measures: Check the previously displayed message and eliminate the cause of the error. Error: Unrecognized option: -. Explanation: An invalid option was specified. a: Measures: First byte of specified option Correctly specify the option and re-execute the command. 86 Chapter 4 Output Messages Value: is invalid for option: Explanation: Measures: A value specified in an option is invalid. aaa...a: Option name bbb...b: Option value Correctly specify the option and re-execute the command. VxVM is not installed, DiskGroup is not supported Explanation: A disk group cannot be specified in an environment in which VxVM is not installed. Measures: Correctly specify the options and re-execute the command. [Added for V4.1] Error: /usr/sbin/vxdisk list failed(retcode=). Explanation: A command error occurred. aaa...a: Measures: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. Error: cannot be specified when ATgroup is specified. Explanation: The specified option is incorrect for specifying an ATgroup. aaa...a: Measures: Option  pairnochk  rvvolume  rvflg  rvacc  rvuse  mnt  file Specify the option correctly and re-execute the command. Error: failed(retcode=). Explanation: An error occurred in a function of the data replication function. aaa...a: bbb...b: Measures: Function name  iSMrc_atgsense  iSMrc_atgreplicate  iSMrc_atgseparate Error code (Return code) Check the error code (explained in Table 4-1 “Error Codes Returned by Data Replication Function”) and eliminate the cause of the error. 87 Chapter 4 Output Messages Error: failed(retcode=, subcode=). Explanation: An error occurred in a function of the data replication function. aaa...a: Measures: Function name  iSMrc_atgsense  iSMrc_atgreplicate  iSMrc_atgseparate  iSMrc_lsdev_seek bbb...b: Error code (Return code) ccc...c: Return value (for expansion) Check the error code (explained in Table 4-1 “Error Codes Returned by Data Replication Function”) and the return value (for expansion) (explained in Table 4-2 “Value Returned by Data Replication Function (for Expansion)”) and eliminate the cause of the error. Table 4-2 Value Returned by Data Replication Function (for Expansion) Value (hexadecimal) Explanation 0xffffffff Terminated abnormally. 0x00000020 This request cannot be operated from the concentrator side. 0x00000030 This request cannot be operated from the distributor side. 0x00000101 The specified ATgroup name already exists. 0x00000201 A pair is already registered with the specified ATgroup. 0x00000301 The specified pair is not a pair with RDR configuration. 0x00000302 The MV of the specified pair has multiple RVs with RDR configuration. 0x00000303 The MV of the specified pair has already been registered with another ATgroup. 0x00000401 The specified pair has not been registered with the specified ATgroup. 0x00000501 The setting value of the specified atomic-break mode or copy mode has already been set in the ATgroup. 0x00001000 No pair has been registered with the specified ATgroup. 0x00001010 An error was detected in the link path state of the specified ATgroup. 0x00001020 An unknown state was detected in the consistency or sync state of the specified ATgroup. 0x00001030 The maximum number of concentrators that can be executed at the same time in semi synchronous copy mode (order guarantee) has been exceeded on the target unit. 0x00001210 The specified ATgroup is now separated (Separated). 0x00001220 The specified ATgroup is now in the state of separate start (Sep/start). 0x00001230 The specified ATgroup is now in the state of separate execution (Sep/exec). 0x00001240 The specified ATgroup is now in the state of fault recovering (Fault/recovering). 0x00001200 The specified ATgroup is now in the state of fault separation (Fault). 0x00001280 There are pairs in different separate states (separated, fault, and cancel) in the specified ATgroup. 0x00001120 The specified ATgroup is now in the state of replicate start (Rpl/start). 0x00001130 The specified ATgroup is now in the state of replicate execution (Rpl/exec). 0x00001110 The specified ATgroup is now in the state of replicate synchronous (Rpl/sync). 0x00001100 The specified ATgroup is now in the state of replicate suspend (Rpl/suspend). 88 Chapter 4 Output Messages Value (hexadecimal) Explanation 0x00001180 There are pairs in different replicate states (rpl/exec and rpl/sync) in the specified ATgroup. 0x00001330 The specified ATgroup is now in the state of restore execution (Rst/exec). 0x00001300 The specified ATgroup is now in the state of restore suspend (Rst/suspend). 0x00001380 There are pairs in different restore states (rst/exec and rst/sync) in the specified ATgroup. Error: is invalid for option: . Explanation: Measures: The option value is incorrect. aaa...a: Option value bbb...b: Option name Correctly specify the option and re-execute the command. Error: All paths of the device: in the disk group: do not exist in volume list. Explanation: Measures: The VxVM state is incorrect. aaa...a: Device to be displayed in the vxdisk list bbb...b: Disk group name Check the state of the VxVM. If necessary, restart the VxVM. Error: ATgroup: cannot be operated for path state: . Explanation: Measures: An error in the ATgroup link path was detected. aaa...a: ATgroup name bbb...b: State  link path/invalid: The value of the link path state is invalid.  link path/frozen: A frozen link path exists.  link path/fault: No normal link path exists. Check the link path state of the ATgroup and eliminate the cause of the error. Error: ATgroup: cannot be operated for sync state: . Explanation: An incorrect ATgroup state was detected. aaa...a: ATgroup name bbb...b: State  ATgroup sep/fault: There are pairs in the separate (separated) state, separate (fault) state, and separate (cancel) state.  ATgroup sep/start: The separate command or forced separate command was executed on some of the pairs, and there are pairs in the separate state and replicate state.  ATgroup sep/exec: 89 Chapter 4 Output Messages All pairs in the ATgroup are in the separate state including the separate (exec) state.  ATgroup separated: All pairs are in the separate (separated) state.  ATgroup rpl/start: Synchronization was started or resumed only on some of the pairs, and there are pairs in the separate state and replicate state.  ATgroup rpl/exec: The ATgroup has one or more pairs in the replicate (exec) state and the remaining pairs are in the replicate synchronous (sync) state.  ATgroup rpl/suspend: One or more pairs are in the abnormal suspend (replicate) state.  ATgroup rpl/sync: All pairs are replicate synchronous (sync) state.  ATgroup rst/exec: One or more pairs are in the restore (exec) state.  ATgroup rst/suspend: One or more pairs are in the abnormal suspend (restore) state.  ATgroup invalid: No pairs (volumes) are registered with the ATgroup. Measures: Check the state of the ATgroup and eliminate the cause of the error. Error: ATgroup: cannot be operated in sync state: for invalid : . Explanation: The ATgroup cannot be operated in the specified mode. aaa...a: ATgroup name bbb...b: ATgroup state  ATgroup rpl/suspend: At least one pair is in the abnormal suspend (replicate) state.  ATgroup rpl/start: The separate command or forced separate command was executed on some of the pairs, and there are pairs in the separate state and replicate state. ccc...c: ddd...d: Measures: Mode  atmode: Atomic-break mode  cpmode: Copy mode Specified mode  stop: MV access stop  continue: MV access continue  sync: Synchronous copy mode  semi: Semi synchronous copy mode (order guarantee)  bg: Background copy mode (asynchronous) Correctly specify the option and re-execute the command. 90 Chapter 4 Output Messages Error: ATgroup name: is too long. Explanation: The specified ATgroup name is too long. aaa...a: Measures: ATgroup name Correctly specify the ATgroup name and re-execute the command. Error: DiskArray name: is too long. Explanation: The specified disk array name is too long. aaa...a: Measures: Disk array name Correctly specify the disk array name and re-execute the command. Error: Failed to wait state for sync state: . Explanation: The pair state of the disk did not enter a synchronous state during command execution. aaa...a: bbb...b: Measures: Sync state  separated: Separate synchronous  rpl/sync: Replicate synchronous Pair state  rpl/preparing: Replicate preparation  rpl/exec: Replicate execution  rpl/sync: Replicate synchronous  sep/preparing: Separate preparation  separated: Separate synchronous  sep/exec: Separate execution  sep/cancel: Separated (forced separation)  sep/fault: Separated (fault separation)  rst/preparing: Restore preparation  rst/sync: Restore sync state  rst/exec: Restore execution Check the pair state of the disk using the iSMrc_query command or the iSM client. Error: Failed to wait state for sync state: . Explanation: The state of the ATgroup did not enter a synchronous state during command execution. aaa...a: bbb...b: Sync state  ATgroup separated: All pairs are separated.  ATgroup rpl/sync: All pairs are replicate synchronous (sync) state. ATgroup state  ATgroup sep/fault: There are pairs in the separate (separated) state, separate (fault) state, and separate (cancel) state.  ATgroup sep/start: The separate command or forced separate command was executed on some 91 Chapter 4 Output Messages of the pairs, and there are pairs in the separate state and replicate state.  ATgroup sep/exec: All pairs in the ATgroup are in a separate state including the separate (exec) state.  ATgroup separated:  ATgroup rpl/start: All pairs are separated. Synchronization was started or resumed only on some of the pairs, and there are pairs in the separate state and replicate state.  ATgroup rpl/exec: The ATgroup has one or more pairs in the replicate (exec) state and the remaining pairs are in the replicate synchronous (sync) state.  ATgroup rpl/suspend: At least one pair is in the abnormal suspend (replicate) state.  ATgroup rpl/sync: All pairs are in the replicate (sync) state.  ATgroup rst/exec: At least one pair is in the restore (exec) state.  ATgroup rst/suspend: At least one pair is in the abnormal suspend (restore) state.  ATgroup invalid: No pair (volume) is registered with the ATgroup. Measures: Check the state of the ATgroup using the iSMrc_query command or the iSM client. Error: Insufficient option. Explanation: Neither the -m option nor -f option is specified. Measures: Correctly specify the option and re-execute the command. Error: Invalid ATgroup name: . Explanation: The specified ATgroup does not exist. aaa...a: Measures: ATgroup name Correctly specify the ATgroup name and re-execute the command. Error: LDNAME: is mounted abnormally. FSNAME1: FSNAME2: Explanation: Measures: The logical disk (volume) to be operated is mounted under multiple special file names. aaa...a: Logical disk name bbb...b: Mounted special file name ccc...c: Mounted special file name Mount the logical disk under a single special file name and re-execute the command. 92 Chapter 4 Output Messages Error: Line : Cannot get pair information of MV: . Explanation: Measures: Acquisition of pair information failed. aaa...a: Line number bbb...b: Logical disk name or special file name of the MV Refer to the message displayed immediately before this error and eliminate the cause of the error. Error: Line : Disk listed in the file does not belong to DG: . Explanation: Measures: The specified MV in the pair file is not a disk configuring the disk group. aaa...a: Line number bbb...b: Logical volume name or special file name of the MV. ccc...c: Disk group name Correct the data of the pair file and re-execute the command. Error: Line : MV: cannot be recognized by OS. Explanation: Measures: The MV is not recognized by the OS. aaa...a: Line number bbb...b: Logical volume name of the MV. Make the MV recognized by the OS and ReplicationControl, and re-execute the command. Error: Line : SPS DEVICE: cannot be specified when disk group is specified. Explanation: Measures: A PathManager device cannot be specified when a disk group name is specified. aaa...a: Line number bbb...b: PathManager device name Correctly specify the option and re-execute the command. [Revised for V7.2.001] Error: mv_volume, dg_name, vg_name or atgroup_name must be specified. Explanation: mv_volume, dg_name, vg_name or atgroup_name is not specified. Measures: Correctly specify the parameter and re-execute the command. Error: mvflg(ld or sfn) cannot be specified along with file. Explanation: The -m option cannot be specified when a pair file is specified. Measures: Correctly specify the option and re-execute the command. 93 Chapter 4 Output Messages Error: No MV in the ATgroup: . Explanation: The specified ATgroup does not have any registered logical disk (volume). aaa...a: Measures: ATgroup name Register a logical disk (volume) with the ATgroup, specify the ATgroup, and re-execute the command. Error: Option requires an argument. Explanation: The option is specified incorrectly. aaa...a: Measures: Option name Correctly specify the option and re-execute the command. Error: Pair cannot be operated for copy control state: . MV: RV: Explanation: The copy control state of the pair is not ready for replication or separation. aaa...a: Pair state  cpmode/normal suspend: Suspended (copy suspended) state  cpmode/abnormal suspend: Suspended (copy fault) state  cpmode/frozen: The data replication function of the disk array is freezing. Measures: bbb...b: Logical disk name of the MV ccc...c: Logical disk name of the RV Refer to the message displayed immediately before this error and eliminate the cause of the error. Check the disk pair state using the iSM client or the iSMrc_query command. Make the copy control state ready for execution, and re-execute the command. [Revised for V7.2.001] Error: pairnochk must be specified along with disk group or volume group. Explanation: The pairnochk option must be specified together with a disk group or a volume group. Measures: Correctly specify the option re-execute the command. 94 Chapter 4 Output Messages Error: Pair state error. State: MV: RV: Explanation: Measures: A pair state error was detected. aaa...a: Logical disk name or special file name of the MV bbb...b: Logical disk name or special file name of the RV ccc...c: Pair state  rpl/preparing: Replicate preparation  rpl/exec: Replicate execution  rpl/sync: Replicate synchronous  sep/preparing: Separate preparation  separated: Separate synchronous  sep/exec: Separate execution  sep/cancel: Separated (forced separation)  sep/fault: Separated (fault separation)  rst/preparing: Restore preparation  rst/sync: Restore sync state  rst/exec: Restore execution Refer to the message displayed immediately before this error and eliminate the cause of the error. Check the disk pair state using the iSM client or the iSMrc_query command. Make the state ready for execution, and re-execute the command. Error: polling cannot be specified along with nowait. Explanation: The polling option cannot be specified when the nowait option is specified. Measures: Correctly specify the option and re-execute the command. Error: polling cannot be specified along with wait. Explanation: The polling option cannot be specified when the wait option is specified. Measures: Correctly specify the option and re-execute the command. Error: rvflg must be specified along with rvvolume. Explanation: The rvflg option must be specified together with the rvvolume option. Measures: Correctly specify the options and re-execute the command. Error: rvvolume cannot be specified along with file. Explanation: The rvvolume option cannot be specified when the -f option is specified. Measures: Correctly specify the option and re-execute the command. 95 Chapter 4 Output Messages Error: Some MVs in the ATgroup cannot be recognized by OS. ATgroup: MV: : : Explanation: Measures: The logical disk (volume) registered with the ATgroup is not recognized by the OS. aaa...a: ATgroup name bbb...b: Logical disk name of the MV Make the MV recognized by the OS and ReplicationControl, and re-execute the command. Error: Some disks in the disk group do not belong to ATgroup: . disk group: DEVICE: (ATgroup) DEVICE: : : Explanation: Some logical disks (volumes) registered with the disk group are not registered with the ATgroup. Measures: aaa...a: ATgroup name bbb...b: Disk group name ccc...c: Logical disk name of the MV, when the MV belongs to the disk group. ddd...d: Logical disk name of the MV, when the MV does not belong to the disk group. Register all logical disks (volumes) registered with the disk group with the ATgroup. Error: SPS DEVICE: cannot be specified when disk group is specified. Explanation: A PathManager device cannot be specified when a disk group name is specified. aaa...a: Measures: PathManager device name Correctly specify the option and re-execute the command. Error: The state error is found in the disk group which belongs to ATgroup: . disk group: DEVICE: (ATgroup) DEVICE: : : Explanation: Measures: The device information in the disk group cannot be obtained. aaa...a: ATgroup name bbb...b: Disk group name ccc...c: Logical disk name of the MV, when the MV belongs to the disk group. - When the device information cannot be obtained. : Delete the device of which information cannot be obtained from the disk group and re-execute the command. 96 Chapter 4 Output Messages Error: umount command error(retcode=) Explanation: File system unmount processing failed. aaa...a: Measures: Return code Refer to the message displayed immediately before this error and eliminate the cause of the error. [Added for V4.2.002] Error: Specified MV: is belong to disk group: . Explanation: Measures: If the specified MV belongs to a disk group, processing cannot be executed for the MV. aa: MV bbb…b: Disk group name Check the relation between the specified MV and the disk group. Error: VxVM is not available, DiskGroup is not supported. Explanation: A disk group cannot be specified in an environment in which VxVM cannot be used. Measures: Check whether or not VxVM can be used in the environment. [Added for V7.2.001] RV can't be specified when –m option is vg Explanation: When the volume group is specified, RV cannot be described. Measures: Correctly specify the options and re-execute the command. [Added for V7.2.001] Error: /opt/iSMfso/bin/vgdisplay -c failed(retcode=). Explanation: A command error occurred. aaa...a: Measures: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. [Added for V7.2.001] Error: Invalid volume group name: Explanation: The volume group name is invalid. aaa...a: Measures: Volume group name Specify a valid disk group name and re-execute the command. 97 Chapter 4 Output Messages [Added for V7.2.001] Error: Failed to get the information of device: in the volume group: . Explanation: Measures: Obtaining volume group device information failed. aaa...a: Special file name bbb...b: Volume group name Check the previously displayed message and eliminate the cause of the error. [Added for V7.2.001] Error: /opt/iSMfso/bin/vgdisplay failed, cannot get information of the volume group: (retcode= ). Explanation: Measures: Obtaining volume group device information failed. aaa...a: Volume group name bbb...b: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. [Added for V7.2.001] Error: Specified MV: is belong to volume group: . Explanation: Measures: If the specified MV belongs to a volume group, processing cannot be executed for the MV. aa: MV bbb...b: Volume group name Check the relation between the specified MV and the volume group. [Added for V7.2.001] Error: Some disks in the volume group do not belong to ATgroup: . volume group: DEVICE: (ATgroup) DEVICE: : : Explanation: Some logical disks (volumes) registered with the volume group are not registered with the ATgroup. Measures: aaa...a: AT group name bbb...b: Volume group name ccc...c: Logical disk name of the MV, when the MV belongs to the volume group. ddd...d: Logical disk name of the MV, when the MV does not belong to the volume group. Register all logical disks (volumes) registered with the volume group with the ATgroup. 98 Chapter 4 Output Messages [Added for V7.2.001] Error: No valid pair in the volume group. Explanation: There are no paired disks in the volume group. Measures: Check the state of disks in the volume group. [Added for V7.2.001] Error: All paths of the device: in the volume group: do not exist in volume list. Explanation: Measures: The LVM state is incorrect. aaa...a: Device to be displayed on vgdisplay bbb...b: Volume group name Check the state of the LVM. [Added for V7.2.001] Error: Line : Disk listed in the file does not belong to volume group: . Explanation: Measures: The specified MV in the pair file is not a disk configuring the volume group. aaa...a: Number of lines bbb...b: Logical volume name or special file name of MV ccc...c: Volume group name Correct the data of the pair file and re-execute the command. [Added for V7.2.001] Error: Line : SPS DEVICE: cannot be specified when volume group is specified. Explanation: Measures: A PathManager device cannot be specified when a volume group name is specified. aaa...a: Number of lines bbb...b: PathManager device name Correctly specify the option and re-execute the command. [Added for V7.2.001] Error: SPS DEVICE: cannot be specified when volume group is specified. Explanation: A PathManager device cannot be specified when a volume group name is specified. aaa...a: Measures: PathManager device name Correctly specify the option and re-execute the command. 99 Chapter 4 Output Messages [Added for V9.1.001] Error: Line : DM-Multipath DEVICE: cannot be specified when volume group is specified. Explanation: Measures: A DM-Multipath device cannot be specified when a volume group name is specified. aaa...a: Number of lines bbb...b: DM-Multipath device name Correctly specify the option and re-execute the command. [Added for V9.1.001] Error: DM-Multipath DEVICE: cannot be specified when volume group is specified. Explanation: A DM-Multipath device cannot be specified when a volume group name is specified. aaa...a: Measures: DM-Multipath device name Correctly specify the option and re-execute the command. 100 Chapter 4 Output Messages 4.2 Snapshot Operation This section explains the messages that are output when using snapshot functions (iSMsc_fscreate, iSMsc_fsdelete). Informational messages are displayed in standard output, and warnings and error messages in standard error output. When parameters are entered using brackets as in or , it means that parameter values that are not fixed are displayed. (The brackets “< >” are not actually output.) For details on parameter values, refer to the [Explanation] field. 4.2.1 Informational Messages Info: is mounted on . Explanation: Mounting is done. aaa...a: Special file name bbb...b: Mount point name Info: is unmounted. Explanation: Unmounting is done. aaa...a: Special file name Info: All lvols are not mounted. Explanation: There is no volume to unmount or freeze. Only snapshot creation is performed. Info: Create Snapshot Start. Explanation: Snapshot creation has started. Info: Create Snapshot Success. Explanation: Snapshot creation succeeded. Info: Creating Snapshot. BV: Explanation: SV: Snapshot creation is being performed. aaa...a: Logical disk name of BV bbb...b: Logical disk name of SV 101 Chapter 4 Output Messages Info: Delete Snapshot Start. Explanation: Snapshot deletion has started. Info: Delete Snapshot Success. Explanation: Snapshot deletion succeeded. Info: Deleting Snapshot. BV: Explanation: SV: Snapshot deletion is being performed. aaa...a: Logical disk name of BV bbb...b: Logical disk name of SV Info: Freeze Start. Explanation: Freeze processing of the VxFS/ext file system has started. Info: Freeze Success. Explanation: Freeze processing of the VxFS/ext file system succeeded. Info: Freezing . Explanation: The VxFS/ext file system is being frozen. aaa...a: Mount point name Info: Link Success. LV: Explanation: SV: Link processing succeeded. aaa...a: Logical disk name of LV bbb...b: Logical disk name of SV Info: Mount LV Start. Explanation: Mount processing of the LV has started. Info: Mount LV Success. Explanation: Mount processing of the LV succeeded. Info: No disk in DiskGroup, Snapshot cannot be created. Explanation: A snapshot cannot be created because the BV is not included in the volumes configuring the disk group. 102 Chapter 4 Output Messages Info: No disk in DiskGroup, Snapshot cannot be deleted Explanation: A snapshot cannot be deleted because the BV is not included in the volumes configuring the disk group. Info: No volume to be frozen. Explanation: There is no volume to be frozen. Only snapshot creation is executed. Info: Umount LV Start. Explanation: Unmount processing of the LV has started. Info: Umount LV Success. Explanation: Unmount processing of the LV succeeded. Info: Unfreeze Start. Explanation: Unfreeze processing of the VxFS/ext file system has started. Info: Unfreeze Success. Explanation: Unfreeze processing of the VxFS/ext file system succeeded. Info: Unfreezing . Explanation: The VxFS/ext file system is being unfrozen. aaa...a: Mount point name Info: Unlink Success. LV: Explanation: SV: Unlink processing succeeded. aaa...a: Logical disk name of LV bbb...b: Logical disk name of SV 103 Chapter 4 Output Messages 4.2.2 Warning Messages Warning: All LVs which can be linked with SV: have been linked or cannot be recognized by OS. Explanation: All of the LVs that can be linked to the SV have been linked or cannot be recognized by the operating system. aaa...a: Measures: Logical disk name of SV If there are unneeded LVs among the linked LVs, unlink them. If all are needed, allocate a new LV and re-execute the command. Warning: LV: linked with SV: cannot be recognized by OS. Explanation: Measures: The snapshot cannot be deleted because the LV cannot be recognized by the operating system. aaa...a: Logical disk name of LV bbb...b: Logical disk name of SV Re-execute the command after unlinking on the server that is using the snapshot. Warning: No LVs which can be linked with SV: exist. Explanation: There is no LV that can be linked. aaa...a: Measures: Logical disk name of SV Re-execute the command after allocating a linkable LV. Warning: Snapshot cannot be deleted. BV: Explanation: Measures: SV: The snapshot cannot be deleted. aaa...a: Logical disk name of BV bbb...b: Logical disk name of SV Check the previously displayed message and eliminate the cause of the error. Warning: Unfreeze Timeout! Explanation: Snapshot creation ended but a time-out was detected in unfreeze processing of the file system. A snapshot may have been created without performing file system synchronization. Measures: Set a greater time-out value and re-execute the iSMsc_fscreate command. [Added for V7.2.001] Warning: ext and vxfs are using at the same time! Explanation: The ext and VxFS file systems cannot be used at the same time. Measures: Handle it by checking the file system type. 104 Chapter 4 Output Messages [Added for V7.2.001] Warning: Cannot get pair information of some disks of the volume group. Explanation: There are unpaired volumes in the volume group. Measures: Check the pair state and the pair file, and then re-execute the command. Ignore this message if there is no problem. [Added for V7.2.001] Warning: Number of BVs listed in the file is different from the volume group. Explanation: The number of BVs described in the pair file is different from that in the volume group. Measures: Revise the pair file description and re-execute the command. 105 Chapter 4 Output Messages 4.2.3 Error Messages Error: command timeout. Explanation: A time-out occurred in system command execution. aaa...a: Measures: Command name  sbin/fsck  bin/mount  bin/rpm  bin/umount  usr/sbin/vxdisk  usr/sbin/vxprint Check the operating environment of the system command and eliminate the cause of the error. Error: failed on (retcode = ) . Explanation: A command error occurred. aaa...a: Measures: Command name  sbin/fsck  bin/mount  bin/umount bbb...b: Special file name of LV ccc...c: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. Error: failed, cannot get information of (retcode = ). Explanation: A command error occurred. aaa...a: Measures: Command name  usr/sbin/vxdisk  /usr/sbin/vxprint bbb...b: Disk group name ccc...c: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. Error: has been specified. Explanation: The same option has been specified multiple times. aaa...a: Measures: Option name Correctly specify the option and re-execute the command. 106 Chapter 4 Output Messages Error: is invalid for option: . Explanation: Measures: The value of an option is invalid. aaa...a: Value of option bbb...b: Option name Correctly specify the option and re-execute the command. Error: -b option is incorrect ( is installed). Explanation: If “VxVM” is displayed, it is an environment in which VxVM is installed and only dg can be specified in the -m option. If “SPS” is displayed, it is an environment in which PathManager is installed and dg cannot be specified in the -m option. aaaa: Measures: VxVM or SPS If “VxVM” is displayed, re-execute the command using the command interface of a VxFS (with VxVM) environment. If “SPS” is displayed, re-execute the command using the command interface of a VxFS (without VxVM) environment. Error: BV: cannot be recognized by OS. Explanation: The BV is not being recognized by the operating system. aaa...a: Measures: Logical volume name of BV Re-execute the command in a state in which the BV is recognized by the operating system and SnapControl. Error: BV: has SVs, SV name must be specified. Explanation: Measures: Because the BV is paired with multiple SVs, the SV cannot be omitted. aaa...a: Logical volume name or special file name of BV bbb...b: Number of SVs that are paired with BV Correctly specify the SV and re-execute the command. Error: BV: is restoring, cannot Snapshot. Explanation: Measures: Because the BV is restoring, a snapshot cannot be created or deleted. aaa...a: Logical disk name of BV bbb...b: create or delete Re-execute the command after restoring ends. 107 Chapter 4 Output Messages Error: BV: is specified more than one time in the file. Explanation: The same BV is specified multiple times in the pair file. aaa...a: Measures: Logical disk name of BV Correctly specify the pair file and re-execute the command. Error: BV: listed in the file does not belong to DG: . Explanation: Measures: The specified BV in the pair file is not a disk configuring the disk group. aaa...a: Logical disk name or special file name of BV bbb...b: Disk group name Correctly specify the pair file and re-execute the command. Error: BV: specified has been mounted. SFN: Explanation: Measures: MNTPT: A BV specified by the special file name has been mounted by another special file name. aaa...a: Special file name of specified BV bbb...b: Name of special file by which BV has been mounted ccc...c: Mount point name Specify the BV by logical volume name. Alternatively, specify the special file by which it was mounted and re-execute the command. Error: bvflg (ld or sfn) cannot be specified along with file. Explanation: A pair file cannot be specified simultaneously with the -b option. Measures: Correctly specify the options and re-execute the command. Error: bvvolume or dgname must be specified. Explanation: bv_volume or dg_name has not been specified. Measures: Correctly specify the parameters and re-execute the command. Error: Cannot freeze . Explanation: Freeze processing failed. aaa...a: Measures: Mount point name Check the previously displayed message and eliminate the cause of the error. Error: Cannot get pair information of BV: . Explanation: Obtaining BV pair information failed. aaa...a: Measures: Logical disk name or special file name of BV Handle it by referring to previously displayed error. 108 Chapter 4 Output Messages Error: Cannot mount . Explanation: Mount processing failed. aaa...a: Measures: Special file name of LV Refer to the previous error message and check whether the mount point exists and whether the directory state is correct. After eliminating the cause of mount failure, re-mount by manually executing the fsck/mount command for the LV. Error: Cannot read from the file: (errno=) . Explanation: Measures: Reading of the pair file failed. aaa...a: File name bbb...b: Error number (The value defined in the Linux system is directly output.) Check the error number for the Linux system and eliminate the cause of the fault. Error: Cannot unfreeze . Explanation: Unfreeze processing failed. aaa...a: Measures: Mount point name Check the previously displayed message and eliminate the cause of the error. Error: Create Snapshot Failed. Explanation: Snapshot creation failed. Measures: Check the previously displayed message and eliminate the cause of the error. Error: cyclic cannot be specified along with file. Explanation: A pair file cannot be specified simultaneously with the cyclic option. Measures: Correctly specify the options and re-execute the command. Error: Delete Snapshot Failed. Explanation: Snapshot deletion failed. Measures: Check the previously displayed message and eliminate the cause of the error. 109 Chapter 4 Output Messages Error: Failed to (errno=) . Explanation: An error occurred in a system function. aaa...a: bbb...b: Measures: System function name  access  chdir  calloc  execv  fdopen  fork  ioctl  malloc  mkdir  pipe  putenv  realloc  strdup  wait Error number (The value defined in the Linux system is directly output.) Check the error number for the Linux system and eliminate the cause of the fault. Error: Failed to get device from DiskGroup: . Explanation: Obtaining disk group device information failed. aaa...a: Measures: Disk group name From vxdisk command output results, check whether or not there is a volume in the disk group and eliminate the cause of failure. Error: Failed to get the information of device: in DiskGroup: . Explanation: Measures: Obtaining disk group device information failed. aaa...a: Special file name bbb...b: Disk group name Check the previously displayed message and eliminate the cause of the error. Error: Failed to open file: (errno=) . Explanation: Measures: The opening of a file failed. aaa...a: File name bbb...b: Error number (The value defined in the Linux system is directly output.) Check the error number for the Linux system and eliminate the cause of the fault. 110 Chapter 4 Output Messages Error: Freeze Failed. Explanation: Freeze processing of a file system failed. Measures: Check the previously displayed message and eliminate the cause of the error. Error: FS type of is not VxFS. Explanation: The file system of a volume is not a VxFS file system. aaa...a: Measures: Special file name of BV Operation is not possible for file systems other than VxFS. Error: Insufficient option. Explanation: Neither the -b option nor the -f option has been specified. Measures: Correctly specify the options and re-execute the command. Error: Invalid dg_name: Explanation: The disk group name is invalid. aaa...a: Measures: Disk group name Specify a valid disk group name and re-execute the command. Error: Invalid timeout value: . Explanation: The time-out value specified in the -t option is invalid. aaa...a: Measures: Time-out value Specify a valid time-out value and re-execute the command. Error: failed (retcode = ). Explanation: An error occurred in a snapshot function. aaa...a: bbb...b: Measures: Function name  iSMsc_create  iSMsc_delete  iSMsc_get_linkvolcnt  iSMsc_link  iSMsc_linkinfo  iSMsc_query  iSMsc_unlink  iSMrc_lsdev Error code (Return code) Check the error code (explained in Table 4-3 Error Codes Returned by Snapshot Function) and eliminate the cause of the error. 111 Chapter 4 Output Messages Table 4-3 Error Codes Returned by Snapshot Function Value Explanation 1 An error occurred on issuance of a SCSI command. 2 An invalid value was specified in a parameter. 4 An error occurred in the interface with the system. 5 Acquisition of volume information of the disk group failed. 6 The number of BV and SV pairs is inconsistent. 7 An error occurred in SCSI open processing. 8 An error occurred in SCSI close processing. 9 A specified volume does not exist in the volume list. 10 The OS type of a specified volume is not supported. 11 The specified SV has not been set as a generation of the BV. 12 The SV was omitted when multiple SVs exist for the BV. 19 Acquisition of volume information of the disk group failed. 21 The format of the volume list is incorrect. 22 Opening the volume list failed. 42 The volume is mounted. 48 The volume list is locked (create/update). 49 The volume list is updated. Or the volume list does not exist. 53 The disk array snapshot function is not in the freeze state. 61 Memory reservation failed. 64 SnapControl has not been installed. 80 SCSI I/O failed, and the I/O path has been switched (warning). 81 The specified number of volumes does not match the number of volumes belonging to the volume group or disk group. 201 A volume that is not a BV was specified. 202 A volume that is not a SV was specified. 203 A volume that is not a LV was specified. 204 A volume that is not a SV nor a BV was specified. 205 The specified link permission volume does not exist. 207 The specified volume is not a volume targeted for link operation (not an LV or link permission volume). 209 There is no DynamicSnapVolume license. 212 A request cannot be accepted due to not being in an active or inactive state. (Target pair) 213 A request cannot be accepted due to not being in an active state. (Target pair) 214 A request cannot be accepted due to restore execution (rst/exec). (Other pairs) 215 A request cannot be accepted because deleting is being executed. (Other pairs) 216 Link setting is not possible because capacities disagree. 217 Link setting is not possible because OS types disagree. 218 A request cannot be accepted due to link setting. 219 A request cannot be accepted because a link is not set. 220 A request cannot be accepted because the SV is protected. 223 DynamicSnapVolume is not supported. 224 The specified access control is incorrect. 112 Chapter 4 Output Messages Value Explanation 225 A request cannot be accepted due to link setting. 226 A request cannot be accepted because a replication operation is being executed. 229 A request cannot be accepted because the base-volume which is restoring is in the restore fault state. 230 A request cannot be accepted because the snapshot reserve area is invalid. 253 Only the RemoteDataReplication license is Ver2. Error: Line is too long. Explanation: The number of bytes is too long for a line in a pair file. aaa...a: Measures: Line number Specify it using no more than 1024 bytes per line. Error: Line : BV: has SVs, SV name must be specified. Explanation: The SV was omitted in a pair file description. Since the BV is paired with multiple SVs, the SV cannot be omitted. Measures: aaa...a: Line number bbb...b: Logical volume name or special file name of BV ccc...c: Number of SVs that are paired with the BV Add a description of the SV to the pair file and re-execute the command. Error: Line : cyclic cannot be specified. Explanation: cyclic cannot be specified in the pair file when executing iSMsc_fsdelete. aaa...a: Measures: Line number Correctly describe the pair file and re-execute the command. Error: Line : SV name is incorrect. Explanation: Measures: The specification of a SV described in the pair file is incorrect. aaa...a: Line number bbb...b: Logical disk name or generation name of SV Revise the specification of the SV in the pair file and re-execute the command. Error: Line : unknown format. Explanation: There is an error in a pair file description. aaa...a: Measures: Line number Correctly describe the pair file and re-execute the command. 113 Chapter 4 Output Messages Error: Line : volume name is too long. Explanation: A volume name described in the pair file is too long. aaa...a: Measures: Line number Correctly describe the volume name in the pair file and re-execute the command. Error: Link Failed. LV: Explanation: Measures: SV: Link processing failed. aaa...a: Logical disk name of LV bbb...b: Logical disk name of SV Check the previously displayed message and eliminate the cause of the error. Error: mnt cannot be specified when -b option is dg. Explanation: A mount specification cannot be specified together with a disk group name. Measures: Specify correct options and re-execute the command. Error: Mount LV Failed. Explanation: The mount processing of a LV failed. Measures: Check the previously displayed message and eliminate the cause of the error. Error: Neither target nor file is specified. Explanation: Neither the -b option nor the -f option has been specified. Measures: Correctly specify the options and re-execute the command. Error: No pair found in file: . Explanation: Pairs of BV and SV are not described in the pair file. aaa...a: Measures: Pair file name Describe a correct specification in the pair file and re-execute the command. Error: No SVs available for creating Snapshot. BV: Explanation: There is no SV that can be used to create a snapshot. aaa...a: Measures: Logical disk name of BV If there is a preserved SV, cancel the preserved state or add a generation. Error: Number of BVs listed in the file is incorrect. Explanation: The number of BVs in the pair file is incorrect. All of the BVs that are included in the disk group must be specified. Measures: Revise the pair file description and re-execute the command. 114 Chapter 4 Output Messages Error: Option requires an argument. Explanation: The specification of an option is incorrect. aaa...a: Measures: Option name Correctly specify the option and re-execute the command. Error: Pair state error. BV: Explanation: Measures: SV: State: A pair state error was detected. aaa...a: Logical disk name of BV bbb...b: Logical disk name of SV ccc...c: Pair state  SV linked: The SV is linked  SV protected: The SV is preserved  snap/active: Snapshot active  snap/inactive: Snapshot inactive  rst/exec: Restore execution  snap/deleting: Snapshot deleting  rst/preparing: Restore preparation  snap/preparing: Snapshot preparation  snap/prepare-fault: A fault occurred in SV preparation. Check whether the state of the pair is one of these states and eliminate the cause of the error. Error: SV name is incorrect. Explanation: The specification of a SV is incorrect. aaa...a: Measures: Logical disk name or generation name of SV Correctly specify the SV and re-execute the command. Error: svflg must be specified along with svvolume. Explanation: The svflg option must be specified together with the svvolume option. Measures: Correctly specify the options and re-execute the command. Error: svvolume cannot be specified along with cyclic. Explanation: The svvolume option cannot be specified together with the cyclic option. Measures: Correctly specify the options and re-execute the command. Error: svvolume cannot be specified along with file. Explanation: The svvolume option cannot be specified together with the -f option. Measures: Correctly specify the options and re-execute the command. 115 Chapter 4 Output Messages Error: svvolume cannot be specified when -b option is dg. Explanation: The svvolume option cannot be specified when a disk group is specified. Measures: Correctly specify the options and re-execute the command. Error: The duplicate mount point is found. FSNAME1: FSNAME2: MNTPT: Explanation: Processing is not possible because another file system has been mounted using the same name as the mount point at which the target file system of an operation is being mounted. aaa...a: Special file name or VxVM/LVM volume name of operation target bbb...b: Special file name or VxVM/LVM volume name of file system whose mount point is duplicated by ccc...c: Measures: Duplicated mount point Re-execute the command after unmounting the duplicate mount point. Error: The last line of the file does not terminate with LF. Explanation: There is no line feed code in the last line of the file specified in the -f option. Measures: Add a line feed code and re-execute the command. Error: The oldest generation: of BV: has been linked. Explanation: Measures: The SV of the oldest generation has been linked. aaa...a: Logical disk name of SV bbb...b: Logical disk name of BV Re-execute the command after unlinking. Error: Too many file systems mounted. Explanation: File systems that need unmount or freeze processing exceed the limit. Measures: If specified in a pair file, split the pair file and re-execute the command. If a disk group/volume group is specified, a snapshot cannot be created. Execute unmount processing manually. Error: Too many mount points in the system (/proc/mounts is truncated) . Explanation: The file systems that are mounted in the system exceed the limit. Whether the limit is exceeded can be confirmed from the contents of the /proc/mounts file. If “# truncated” exists at the end of the /proc/mounts file, the limit has been exceeded. Measures: Upon checking the system mount status, manually execute unmount processing. 116 Chapter 4 Output Messages Error: Umount LV Failed. Explanation: Unmounting of the LV failed. Measures: Check the previously displayed message and eliminate the cause of the error. Error: Unexpected parameter: . Explanation: An invalid parameter was specified in the command line. aaa...a: Measures: Invalid parameter Correctly specify the parameters and re-execute the command. Error: Unfreeze Failed. Explanation: Unfreeze processing failed. Measures: Check the previously displayed message and eliminate the cause of the error. Error: Unlink Failed. LV: Explanation: Measures: SV: Unlink processing of the LV failed. aaa...a: Logical disk name of LV bbb...b: Logical disk name of SV Check the previously displayed message and eliminate the cause of the error. Error: Unrecognized option: -. Explanation: An invalid option was specified. a: Measures: First byte of specified option Correctly specify the option and re-execute the command. Error: VxVM is not installed, DiskGroup is not supported. Explanation: A disk group cannot be specified in an environment in which VxVM is not installed. Measures: Correctly specify the options and re-execute the command. Error: VxVM mirroring is found on DiskGroup: . Explanation: The specified disk group has a VxVM mirroring. aaa...a: Measures: Disk group name Operation is not possible for the disk group that is mirrored. 117 Chapter 4 Output Messages [Added for V4.1] Error: All paths of the device: in the disk group: do not exist in volume list. Explanation: Measures: The VxVM state is incorrect. aaa...a: Device to be displayed in the vxdisk list bbb...b: Disk group name Check the state of the VxVM. If necessary restart the VxVM. Error: LDNAME: is mounted abnormally. FSNAME1: FSNAME2: . Explanation: Measures: The volume to be operated is mounted under multiple special file names. aaa...a: Logical disk name bbb...b: Mounted special file name ccc...c: Mounted special file name Mount the volume under a single special file name and re-execute the command. Error: Line : SPS DEVICE: cannot be specified when disk group is specified. Explanation: Measures: A PathManager device cannot be specified when a disk group is specified. aaa...a: Line number bbb...b: PathManager device name Correctly specify the option and re-execute the command. Error: SPS DEVICE: cannot be specified when disk group is specified. Explanation: A PathManager device cannot be specified when a disk group name is specified. aaa...a: Measures: PathManager device name Correctly specify the option and re-execute the command. [Added for V4.2.002] Error: Specified BV: is belong to disk group: . Explanation: Measures: If the specified BV belongs to a disk group, processing cannot be executed for the BV. aa: BV bbb…b: Disk group name Check the relation between the specified BV and the disk group. Error: VxVM is not available, DiskGroup is not supported. Explanation: A disk group cannot be specified in an environment in which VxVM cannot be used. Measures: Check whether or not VxVM can be used in the environment. 118 Chapter 4 Output Messages [Added for V7.2.001] Error: Failed to ioctl(errno= ). Error: Cannot freeze Explanation: Measures: An error occurred in VxFS/ext file system freeze processing. aaa...a: Error message bbb...b: Mount point Refer to the error message and eliminate the cause of the error. [Added for V7.2.001] Error: Failed to ioctl(errno= ). Error: Cannot unfreeze . Explanation: Measures: An error occurred in VxFS/ext file system unfreeze processing. aaa...a: Error message bbb...b: Mount point Refer to the error message and eliminate the cause of the error. [Added for V7.2.001] Error: svvolume cannot be specified when volume group is specified. Explanation: The svvolume option cannot be specified when a volume group is specified. Measures: Correctly specify the options and re-execute the command. [Added for V7.2.001] Error: Line : SPS DEVICE: cannot be specified when volume group is specified. Explanation: Measures: A PathManager device cannot be specified when a volume group name is specified. aaa...a: Number of lines bbb...b: PathManager device name Correctly specify the option and re-execute the command. [Added for V7.2.001] Error: SPS DEVICE: cannot be specified when volume group is specified. Explanation: A PathManager device cannot be specified when a volume group name is specified. aaa...a: Measures: PathManager device name Correctly specify the option and re-execute the command. [Added for V7.2.001] Error: mnt cannot be specified when volume group is specified. Explanation: The mnt option cannot be specified when a volume group is specified. Measures: Correctly specify the options and re-execute the command. 119 Chapter 4 Output Messages [Added for V7.2.001] Error: Failed to get the information of device: in the volume group: . Explanation: Measures: Obtaining volume group device information failed. aaa...a: Special file name bbb...b: Volume group name Check the previously displayed message and eliminate the cause of the error. [Added for V7.2.001] Error: /opt/iSMfso/bin/vgdisplay failed, cannot get information of the volume group: (retcode= )． Explanation: Measures: Obtaining volume group device information failed. aaa...a: Volume group name bbb...b: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. [Added for V7.2.001] Error: Cannot get information of the volume group: . Explanation: Obtaining volume group device information failed. aaa...a: Measures: Volume group name Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. [Added for V7.2.001] Error: Specified BV: is belong to volume group: . Explanation: Measures: If the specified BV belongs to a volume group, processing cannot be executed for the BV. aa: BV bbb…b: Disk group name Check the relation between the specified BV and the volume group. [Added for V7.2.001] Error: No valid pair in the volume group. Explanation: There are no paired disks in the volume group. Measures: Check the state of disks in the volume group. [Added for V7.2.001] Error: Invalid volume group name: Explanation: The volume group name is invalid. aaa...a: Measures: Volume group name Specify a valid disk group name and re-execute the command. 120 Chapter 4 Output Messages [Added for V7.2.001] Error: FS type of is not support. Explanation: The volume file system type is not supported. aaa…a: Measures: File system type to be used Operation is not possible for a file system other than VxFS or ext. Specify a valid file system type and re-execute the command. [Added for V7.2.001] Error: mv_volume, dg_name, vg_name or atgroup_name must be specified. Explanation: mv_volume, dg_name, vg_name or atgroup_name is not specified. Measures: Correctly specify the parameter and re-execute the command. [Added for V7.2.001] Error: /opt/iSMfso/bin/vgdisplay -c failed(retcode=). Explanation: A command error occurred. aaa...a: Measures: Return code Check the return code and the /tmp/.hafss.log file and eliminate the cause of the error. [Added for V7.2.001] Error: Too many file systems mounted. Explanation: File systems that need unmount or freeze processing exceed the limit. Measures: If specified in a pair file, split the pair file and re-execute. If a disk group/volume group is specified, snapshot cannot be executed. Execute unmount processing manually. [Added for V7.2.001] Error: All paths of the device: in the volume group: do not exist in volume list. Explanation: Measures: The LVM state is incorrect. aaa...a: Device to be displayed on vgdisplay bbb...b: Volume group name Check the state of the LVM. 121 Chapter 4 Output Messages [Added for V7.2.001] Error: Line : Disk listed in the file does not belong to volume group: . Explanation: Measures: The specified MV in the pair file is not a disk configuring the volume group. aaa...a: Number of lines bbb...b: Logical volume name or special file name of MV ccc...c: Volume group name Correct the data of the pair file and re-execute the command. [Added for V7.2.001] Error: No valid pair in volume group. Explanation: There are no paired disks in the volume group. Measures: Check the state of disks in the volume group. [Added for V9.1.001] Error: Line : DM-Multipath DEVICE: cannot be specified when volume group is specified. Explanation: Measures: A DM-Multipath device cannot be specified when a volume group name is specified. aaa...a: Number of lines bbb...b: DM-Multipath device name Correctly specify the option and re-execute the command. [Added for V9.1.001] Error: DM-Multipath DEVICE: cannot be specified when volume group is specified. Explanation: A DM-Multipath device cannot be specified when a volume group name is specified. aaa...a: Measures: DM-Multipath device name Correctly specify the option and re-execute the command. 122 Chapter 5 Notes Chapter 5 Notes This chapter explains matters that should be heeded when performing operations in which FileSystem Option is used. 5.1 (1) Data Replication Operations To use the iSMrc_fsseparate and iSMrc_fsreplicate commands for disk arrays, the following products are all required.  Storage Manager  ControlCommand  DynamicDataReplication or RemoteDataReplication Note that the following products are also required separately when using the disaster recovery-capable function.  (2) RemoteDataReplication/DisasterRecovery (RemoteDataReplication indispensable) All of the MV and RV configuring the disk group must be paired in advance. However, if the pairnochk option is specified, processing is possible even if unpaired disks are included. (3) FileSystem Option functions cannot be used when VxVM and PathManager or DM-Multipath are used simultaneously. (4) The file system that is supported is VxFS/ext and logical volumes are VxVM/LVM. Moreover, the following versions are required. File systems and logical volumes other than these are not supported.  VERITAS Storage Foundation for Linux V2.2 or later (VxFS, VxVM)  Red Hat Enterprise Linux 5.6 or later (ext3, LVM)  Red Hat Enterprise Linux 6.0 or later (ext3,ext4, LVM) (5) Mirror disk environments are not supported. (6) Command execution requires a user ID that has super user (root) authority. (7) Since parallel execution of commands makes it difficult to investigate the cause when an error occurs, it is not recommended. (8) When a special file name is specified for MV or RV, it is specified in the format /dev/sdX , /dev/ddX , or /dev/mapper/mpathX (where X is a lowercase letter), omitting the partition number. (9) When a logical disk name is specified for MV or RV, the name of a logical disk that was named by the iSM configuration setting function is specified. Specification of the rvuse option (specification of the available period for RV) is effective only in DynamicDataReplication Ver2 or higher. (10) Mount processing when the mnt option is specified executes the mount command without options. If you wish to perform a mount in which options are specified, execute the mount command separately. Moreover, if a mount point to which _tmp 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 _tmp is appended in different file systems. If the MV is mounted using multiple mount points, the VxFS/ext file system that is on the RV is mounted on only one mount point. The mount point of the VxFS/ext file system on the RV is determined by the mount 123 Chapter 5 Notes point that first mounted the MV (11) Disk groups on the root disk are not supported. Moreover, commands must not be executed for disk groups on the root disk. (12) Disk operation information (such as separation and replication) at the time when each FileSystem Option command is executed is not reported to syslog. (13) A maximum of 240 MV file systems can be handled by FileSystem Option. This is also the maximum number of files that can be frozen simultaneously. (14) Pay attention to the following when using data replication operations and snapshot operations together. When a BV (MV) is being restored from a SV, replication operations are not performed. Table 5-1 Data Replication Operations and Snapshot States Snapshot states Replication control Snapshot Active Inactive Deleting rst/exec iSMrc_fsreplicate (Replicate)    - iSMrc_fsseparate (Separate)    : Executable -: Unexecutable : Impossible situation (15) For disks (MV, RV) for which FC is multiplexed, when making data replication operation requests, the following precautions are necessary.  If only one special file is mounted in a VxFS (without VxVM)/ext (without LVM) environment, specify a disk by the logical disk name or by the mounted special file name.  If multiple file systems are mounted due to multiple special files in a VxFS (without VxVM)/ext (without LVM) environment, FileSystem Option cannot be used.  In a VxFS (with VxVM) environment, specify a disk by logical disk name or by a special file name displayed by the vxdisk -g list command. (16) If the string “# truncated” exists at the end of the /proc/mounts file, the file systems that are mounted in the system exceed the limit. In this case, FileSystem Option cannot get mount information and cannot operate. Unmount unnecessary mount points. (17) Data replication operation of FileSystem Option is based on commands to perform data replication directly from the application server. Therefore, it cannot be used for the following operations. For the following operations, refer to the “Data Replication User's Manual (Function Guide)”.  Operation linked with iSM  Remote operation (18) To restart the server connecting to the RV, you must separate the pair in advance to cancel Not Ready state of the RV. If the server is restarted with the RV in Not Ready state, it is necessary to make OS recognize operation for recognition is required because the OS cannot recognize the RV partition information. For details, refer to the “Data Replication User's Manual (Installation and Operation Guide for Linux)”. 124 Chapter 5 Notes (19) If an access is made to a volume in Not Ready state or Read Only state, such as an access-restricted RV, a message indicating an SCSI error (refer to the below) may be recorded in syslog. If you execute a command, such as fsck, that tries to access all volumes in a server, a message similar to the example below may be recorded for every volume in the server in Not Ready state. Dec 10 14:48:14 sv001 kernel: SCSI error : <4 0 1 1> return code = 0x8000002 Dec 10 14:48:14 sv001 kernel: Info fld=0x0, Current sde: sense key Data Protect Dec 10 14:48:14 sv001 kernel: ASC=f4 ASCQ= a Dec 10 14:48:14 sv001 kernel: end_request: I/O error, dev sde, sector 0 In an environment that has PathManager installed, if such a message is recorded, the PathManager path to the volume may be broken, preventing the volume from being accessed. Separate the pair or change the RV access restriction to make the volume read/write-enabled, and then recover the broken path using the recoverpath command of PathManager. If the path to a volume a volume in Read Only state is broken, recovery is automatically performed by path monitoring of PathManager after a fixed time period (monitoring interval). For details on PathManager, refer to the “PathManager User’s Manual (Linux)”. In an environment that does not have PathManager installed, there is no operational problem even if a message similar to the above example is recorded. (20) Pairs registered with an ATgroup cannot be manipulated. (21) For Red Hat Enterprise Linux 5.6 or later, if the iSMrc_fsseparate command, which is running on the ext file system, is forcibly stopped, the volume might be in the freeze state and inaccessible. In such a case, the freeze state can be released by executing the command below: /usr/sbin/iSMfsfreeze -u mountpoint * For moutpoint, specify the mountpoint of the volume that cannot be accessed because it is in the freeze state. iSMfsfreeze returns the following: 0: The volume is successfully unfreezed. 22: Since the volume has already been unfreezed, it is necessary to unfreeze it again. (22) When using the DM-Multipath, the environment where MV and RV exit in the same server is not supported. 125 Chapter 5 Notes 5.2 (1) Snapshot Operations To use the iSMsc_fscreate and iSMsc_fsdelete commands for disk arrays, the following products are all required.  Storage Manager  ControlCommand  DynamicSnapVolume (2) All of the BV configuring the disk group must be paired with SV in advance. (3) FileSystem Option functions cannot be used when VxVM and PathManager or DM-Multipath are used simultaneously. (4) The file system that is supported is VxFS/ext and logical volumes are VxVM/LVM. Moreover, the following versions are required. File systems and logical volumes other than these are not supported.  VERITAS Storage Foundation for Linux V2.2 or later (VxFS, VxVM)  Red Hat Enterprise Linux 5.6 or later (ext3, LVM)  Red Hat Enterprise Linux 6.0 or later (ext3,ext4, LVM) (5) Mirror disk environments are not supported. (6) Command execution requires a user ID that has super user (root) authority. (7) Since parallel execution of commands makes it difficult to investigate the cause when an error occurs, it is not recommended. (8) When a special file name is specified for BV, it is specified in the format /dev/sdX, /dev/ddX or /dev/mapper/mpathX (where X is a lowercase letter ), omitting the partition number. (9) When a logical disk name is specified for BV or SV, the name of a logical disk that was named by the iSM configuration setting function is specified. (10) Mount processing when the mnt option is specified executes the mount command without options. If you wish to perform a mount in which options are specified, execute the mount command separately. Moreover, if a mount point to which _tmp 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 _tmp is appended in different file systems. If the BV is mounted using multiple mount points, the VxFS/ext file system that is on the LV-SV is mounted on only one mount point. The mount point of the VxFS/ext file system that is on the LV-SV is determined by the first mount point on which the BV is mounted. (11) Disk groups on the root disk are not supported. Moreover, commands must not be executed for disk groups on the root disk. (12) Disk operation information at the time when each FileSystem Option command is executed is not reported to syslog. (13) A maximum of 240 BV file systems can be handled by FileSystem Option. This is also the maximum number of files that can be frozen simultaneously. (14) Pay attention to the following when using data replication operations and snapshot operations together. When a MV (BV) is being restored from a RV, snapshot creation is not performed. 126 Chapter 5 Notes Table 5-2 Snapshot Operations and Data Replication States 1 (MV Snapshot Creation) Data replication states Snapshot operations Replicate Separate Restore rpl/exec rpl/sync sep/exec separated rst/exec rst/sync iSMsc_fscreate (Snapshot creation)     - - iSMsc_fsdelete (Snapshot deletion)       : Executable -: Unexecutable Table 5-3 Snapshot Operations and Data Replication States 2 (RV Snapshot Creation) Data replication states Snapshot operations Replicate Separate Restore Active Sync Active Complete Active Sync iSMsc_fscreate (Snapshot creation) - - -  - - iSMsc_fsdelete (Snapshot deletion)       : Executable -: Unexecutable (15) The following precautions are necessary when making snapshot operation requests for disks (BV) for which FC is multiplexed.  If only one special file is mounted in a VxFS (without VxVM)/ext (without LVM) environment, specify a disk by the logical disk name or by the mounted special file name.  If multiple file systems are mounted due to multiple special files in a VxFS (without VxVM)/ext (without LVM) environment, FileSystem Option cannot be used.  In a VxFS (with VxVM) environment, specify a disk by the logical disk name or by the special file name displayed by the vxdisk -g list command. (16) If the string “# truncated” exists at the end of the /proc/mounts file, the file systems that are mounted in the system exceed the limit. In this case, FileSystem Option cannot get mount information and cannot operate. Unmount unnecessary mount points. (17) Snapshot operation of FileSystem Option is based on commands to perform snapshot operation directly from the application server. Therefore it cannot be used for the following operations. For the following operations, refer to the “Snapshot User’s Manual (Function Guide)”.  Operation linked with iSM  Remote operation (18) To restart the server connecting to the LV, you must link the LV with the SV in advance to cancel the Not Ready state of the LV. If the server is restarted with the LV in Not Ready state, operation for recognition is required because the OS cannot recognize the LV partition information. For details, refer to the “Snapshot User's Manual (Installation and Operation Guide for Linux)”. 127 Chapter 5 Notes (19) If an access is made to a volume in Not Ready state or Read Only state, such as an unlinked or access-restricted LV, a message indicating an SCSI error (refer to the below) may be recorded in syslog. If you execute a command, such as fsck, that tries to access all volumes in a server, a message similar to the example below may be recorded for every volume in the server in Not Ready state. Dec 10 14:48:14 sv001 kernel: SCSI error : <4 0 1 1> return code = 0x8000002 Dec 10 14:48:14 sv001 kernel: Info fld=0x0, Current sde: sense key Data Protect Dec 10 14:48:14 sv001 kernel: ASC=f4 ASCQ= a Dec 10 14:48:14 sv001 kernel: end_request: I/O error, dev sde, sector 0 In an environment that has PathManager installed, if such a message is recorded, the PathManager path to the volume may be broken, preventing the volume from being accessed. Link the LV in the Read/Write mode to make the volume read/write-enabled, and then recover the broken path using the recoverpath command of PathManager. If the path to a volume a volume in Read Only state is broken, recovery is automatically performed by path monitoring of PathManager after a fixed time period (monitoring interval). For details on PathManager, refer to the “PathManager User’s Manual (Linux)”. In an environment that does not have PathManager installed, there is no operational problem even if a message similar to the above example is recorded. (20) For Red Hat Enterprise Linux 5.6 or later, if the iSMsc_fscreate command, which is running on the ext file system, is forcibly stopped, the volume might be in the freeze state and inaccessible. In such a case, the freeze state can be released by executing the command below: /usr/sbin/iSMfsfreeze -u mountpoint * For moutpoint, specify the mountpoint of the volume that cannot be accessed because it is in the freeze state. iSMfsfreeze returns the following: 0: The volume is successfully unfreezed. 22: Since the volume has already been unfreezed, it is necessary to unfreeze it again. (21) When using the DM-Multipath, the environment where MV and RV exist in the same server is not supported. 128 Appendix A Volume Layout and Usability Appendix A Volume Layout and Usability Volume layout and usability when using FileSystem Option are described using replication functions in examples. They are the same when using snapshot functions (read MV as BV and RV as SV). [Volume layout and usability] No 1 Volume Layout Concatenation (1) When volumes do not span multiple disks (When volumes and disks are one-to-one) (2) When there are multiple volumes on one disk (When volumes and disks are n-to-one) (*Usability: : Usable, -: Unusable) Sample Configuration Usability   DG : dg01 MV0 vol01 RV0 RV0 MV1 vol02 RV1 RV1 MV2 vol03 RV2 RV2  DG : dg01 vol01 RV0 RV0 vol02 RV1 RV1 MV0 MV1 vol03 MV2 (3) When a volume spans multiple disks (When multiple volumes do not coexist on one disk) vol04  DG : dg01 MV0 vol01 MV2 vol02 RV2 RV2 MV0 vol01 RV0 RV0  DG : dg01 RV1 RV1 MV1 vol02 MV2 129 RV0 RV0 RV1 RV1 MV1 (4) When volumes span multiple disks (When multiple volumes coexist on one disk) RV2 RV2 RV2 RV2 Appendix A Volume Layout and Usability No 2 Volume Layout Usability  3 Sample Configuration Striping DG : dg01 MV0 vol01 RV0 RV0 MV1 vol02 RV1 RV1 MV2 vol03 RV2 RV2 MV0 vol01 RV0 RV0 MV1 vol02 RV1 RV1 MV2 vol03 RV2 RV2 RAID-5 - DG : dg01 *Management data may lose its integrity on the RV side. 4 Mirroring - DG : dg01 Mirroring RV0MV3’ MV0 vol01 RV0 RV0 RV1MV4 MV1 vol02 RV1 RV1 RV2MV5 MV2 vol03 RV2 RV2 *Management data may lose its integrity on the RV side. 5 Mirroring plus striping - 6 Mixture of VxFS file systems and RAW (or file systems other than VxFS) - *Management data may lose its integrity on the RV side. DG : dg01 MV0 vol01 MV1 vol02 MV2 vol03 RV0 RV1 RV2 Mixture of RAW and file systems other than VxFS etc. *Management data may lose its integrity on the RV side. 130 Appendix A Volume Layout and Usability [Volume layout and usability] (*Usability: : Usable, -: Unusable) No 7 Volume Layout Usability Sample Configuration Concatenation  (1) When volumes do not span multiple disks (When volumes and disks are one-to-one) (2) When there are multiple volumes on one disk (When volumes and disks are n-to-one) VG: vg01 MV1 vol01 MV2 vol02 MV3 vol03  VG: vg01 vol02 MV3 vol03 vol04 RV3 RV0 RV1 RV2  VG: vg01 MV1 vol01 MV2 (4) When volumes span multiple disks (When multiple volumes coexist on one disk) RV2 vol01 MV1 MV2 (3) When a volume spans multiple disks (When multiple volumes do not coexist on one disk) RV1 RV0 RV1 MV3 vol02 RV2 MV1 vol01 RV0  VG: vg01 MV2 RV1 vol02 MV3 8 RV2 Striping  VG: vg01 131 MV1 vol01 MV2 vol02 MV3 vol03 RV0 RV1 RV2 Appendix A Volume Layout and Usability No 9 Volume Layout Usability Sample Configuration RAID-5 VG: vg01 vol01 MV1 RV0 RV1 RV1 MV2 vol02 RV2 MV3 vol03 RV3 RV2 *Management data may lose its integrity on the RV side. 10 Mirroring - VG: vg01 Mirroring RV0 MV4 MV1 vol01 RV0 RV1 MV5 MV2 vol02 RV1 RV2 MV6 MV3 vol03 RV2 *Management data may lose its integrity on the RV side. 11 Mirroring plus striping - 12 Mixture of ext file systems and RAW (or file systems other than ext) *Management data may lose its integrity on the RV side. VG: vg01 MV1 vol01 MV2 vol02 MV3 vol03 RV0 RV1 RV2 Mixture of RAW and file systems other than VxFS etc. *Management data may lose its integrity on the RV side. のファイルシステムなどの混在 132 Appendix B FileSystem Option Operating Procedures Appendix B FileSystem Option Operating Procedures The basic operating procedures when FileSystem Option is used are shown in an example. When actually designing operating procedures, you must design them to suit the requirements of each system. B.1 When Using Data Replication Functions (1.1) Initial settings (when using VxVM in VxFS) It is assumed that logical disks used on the MV side are recognized on the application server. Set the following initial configuration. [Initial configuration] MV0 _____ vol01 MV1 _____ vol02 MV2 _____ vol03 (1) Set pairs (Management server) Perform pair setting from iSM (Replication screen). Pair MV1, MV2, and MV3 with RV1, RV2, and RV3, respectively. (2) Create pair file (Application server) Create the pair file to use in data replication operations. (Sample setting: pair_file) 0:MV1 0:RV1 0:MV2 0:RV2 0:MV3 0:RV3 (3) Create volume list (Application server) Create the volume list. iSMvollist -r (4) Create disk group and volumes (Application server) Create a disk group (Disk group name: dg01) and volumes (volume names: vol01, vol02, vol03). vxdg init dg01 MV1=sdX vxdg -g dg01 adddisk MV2=sdX vxdg -g dg01 adddisk MV3=sdX vxassist -g dg01 make vol01 2g MV1 vxassist -g dg01 make vol02 2g MV2 vxassist -g dg01 make vol03 2g MV3 133 Appendix B FileSystem Option Operating Procedures (5) Create file systems (Application server) Create VxFS file systems. mkfs -t vxfs /dev/vx/rdsk/dg01/vol01 mkfs -t vxfs /dev/vx/rdsk/dg01/vol02 mkfs -t vxfs /dev/vx/rdsk/dg01/vol03 (6) Mount file systems (Application server) Mount the VxFS file systems. mount -t vxfs /dev/vx/dsk/dg01/vol01 /MV_fs01 mount -t vxfs /dev/vx/dsk/dg01/vol02 /MV_fs02 mount -t vxfs /dev/vx/dsk/dg01/vol03 /MV_fs03 (1.2) Backup procedure (when using VxVM in VxFS) An example of a procedure that backs up volumes vol01, vol02, and vol03 of the disk group (dg01) that is configured on MV1, MV2, and MV3 to RV is described. (1) Unmount (Backup server) If operating using RV, unmount the logical volumes that are being used as file systems. umount /RV_fs01 umount /RV_fs02 umount /RV_fs03 (2) Deport disk group (Backup server) Deport the disk group from the backup server. vxdg deport dg01 Set the disk of the RV to offline using the following command. When managing multiple generations on the same backup server (handling multiple RV s for one MV), set all the disks to offline. vxdisk offline sdX (3) Execute replication (Application server) Execute replication for the disk group (dg01). iSMrc_fsreplicate -m dg -f pair_file dg01 *If replication does not end within 60 seconds, add the -t option and specify a greater time-out period. (4) Execute separation (Application server) Execute separation for the disk group (dg01). iSMrc_fsseparate -m dg -f pair_file dg01 *If separation does not end within 60 seconds, add the -t option and specify a greater time-out period. 134 Appendix B FileSystem Option Operating Procedures (5) Import disk group (Backup server) Set RVs to import to the backup server to online using the following command. vxdisk online sdX Perform disk group importing and activation. vxdctl enable vxdg -C import dg01 vxvol -g dg01 startall (6) Execute fsck (Backup server) Perform file system consistency check and repair. fsck -t vxfs /dev/vx/dsk/dg01/vol01 fsck -t vxfs /dev/vx/dsk/dg01/vol02 fsck -t vxfs /dev/vx/dsk/dg01/vol03 (7) Mount logical volumes (Backup server) Mount VxFS file systems belonging to the disk group. mount -t vxfs /dev/vx/dsk/dg01/vol01 /RV_fs01 mount -t vxfs /dev/vx/dsk/dg01/vol02 /RV_fs02 mount -t vxfs /dev/vx/dsk/dg01/vol03 /RV_fs03 (1.3) RV separation from backup server (when using VxVM in VxFS) (1) Unmount logical volumes (Backup server) umount /RV_fs01 umount /RV_fs02 umount /RV_fs03 (2) Deport disk group (Backup server) vxdg deport dg01 vxdisk offline sdX (1.4) Expansion during operation (1) (when using VxVM in VxFS) The following procedure expands a volume when MV and RV are separated and there are unused areas in the disk group, an example of which is shown below. [Initial configuration] [Expanded configuration] MV0 MV0 vol01 MV1 MV2 vol01 MV1 vol02 MV2 135 vol02 (Expanded) Appendix B FileSystem Option Operating Procedures (1) Expand volume Configure the volume that exists in MV3 (vol02) on MV3 and MV2 and expand the volume size from 2 GB to 5 GB. vxassist -g dg01 growto vol02 5g MV3 MV2 *If there is striping, specify it in parameters of the vxassist command. (2) Expand VxFS file system (VxFS) Expand it by setting the block size to 5 GB. Make /MV_fs02 the mount point of vol2. /usr/lib/fs/vxfs/fsadm -b 10485760 /MV_fs02 (1.5) Expansion during operation (2) (when using VxVM in VxFS) The following procedure expands a volume by adding a new disk to the disk group when MV and RV are separated, an example of which is shown below. [Initial configuration] [Expanded configuration] MV0 vol01 MV0 MV2 vol02 vol01 (Expanded) MV1 MV2 vol02 (1) Set pairs (Management server) Perform pair setting from iSM (Replication screen). Pair the added MV and RV (make them MV2 and RV2, respectively). (2) Create pair file (Application server) Create the pair file to use in data replication operations. (Sample setting: pair_file) [Initial configuration]  [Expanded configuration] 0:MV1 0:RV1 0:MV1 0:RV1 0:MV3 0:RV3 0:MV2 0:RV2 0:MV3 0:RV3 (3) Update volume list (Application server) Update the volume list. iSMvollist -r (4) Add disk to disk group (Application server) vxdg -g dg01 adddisk MV2=sdX 136 Appendix B FileSystem Option Operating Procedures (5) Expand volume (Application server) Configure the volume that is in MV1 (vol01) on MV1 and MV2 and expand the volume size from 2 GB to 5 GB. vxassist -g dg01 growto vol01 5g MV1 MV2 *If there is striping, specify it in parameters of the vxassist command. Expand it by specifying the block size to 5 GB. Make /MV_fs01 the mount point of vol1. /usr/lib/fs/vxfs/fsadm -b 10485760 /MV_fs01 (2.1) Initial settings (when using LVM in ext) It is assumed that logical disks used on the MV side are recognized on the application server. Set the following initial configuration. [VG initial configuration] MV1:(/dev/sdX) vol01 MV2:(/dev/sdX) vol01 MV3:(/dev/sdX) vol01 [Volume configuration information for data replication] MV1:/dev/sdX RV1:/dev/sdY MV2:/dev/sdX RV2:/dev/sdY MV3:/dev/sdX RV3:/dev/sdY (1) Set pairs (Management server) Perform pair setting from iSM (Replication screen). Pair MV1, MV2, and MV3 with RV1, RV2, and RV3, respectively. (2) Create pair file (Application server) Create the pair file to use in data replication operations. (Sample setting: pair_file) 0:MV1 0:RV1 0:MV2 0:RV2 0:MV3 0:RV3 (3) Create volume list (Application server) Create the volume list with the iSMvollist command. iSMvollist –r 137 Appendix B FileSystem Option Operating Procedures (4) Create physical volume (Application server) Create the LVM physical volume that uses the volume group. pvcreate /dev/sdX pvcreate /dev/sdX pvcreate /dev/sdX (5) Create volume group and volumes (Application server) Create a volume group (Volume group name: vgmv) and logical volumes (logical volume names: vol01, vol02, vol03). vgcreate /dev/vgmv /dev/sdX /dev/sdX /dev/sdX lvcreate -L 1000 -n vol01 /dev/vgmv lvcreate -L 1000 -n vol02 /dev/vgmv lvcreate -L 1000 -n vol03 /dev/vgmv (6) Create file systems (Application server) Create ext file system. mkfs -t ext3 /dev/vgmv/vol01 mkfs -t ext3 /dev/vgmv/vol02 mkfs -t ext3 /dev/vgmv/vol03 (7) Mount file systems (Application server) Mount the ext file systems. mount -t ext3 /dev/vgmv/vol01 /MV_fs01 mount -t ext3 /dev/vgmv/vol02 /MV_fs02 mount -t ext3 /dev/vgmv/vol03 /MV_fs03 (2.2) Backup procedure (when using LVM in ext) An example of a procedure that backs up logical volumes vol01, vol02, and vol03 of the volume group (vgmv) that is configured on MV1, MV2, and MV3 to RV is described. (1) Unmount (Backup server) If operating using RV, unmount the logical volumes that are being used as file systems. umount /RV_fs01 umount /RV_fs02 umount /RV_fs03 (2) Deactivate the RV and delete volume group information (Backup server) Deactivate and delete the LVM volume group to which the RV belongs from the backup server. vgchange -a n /dev/vgmv vgexport /dev/vgmv 138 Appendix B FileSystem Option Operating Procedures (3) Execute replication (Application server) Execute replication for the volume group (vgmv). iSMrc_fsreplicate -m vg -f pair_file vgmv *If replication does not end within 60 seconds, add the -t option and specify a greater time-out period. (4) Execute separation (Application server) Execute separation for the volume group (vgmv). iSMrc_fsseparate -m vg -f pair_file vgmv *If separation does not end within 60 seconds, add the -t option and specify a greater time-out period. (5) Export MV volume group information (Application server) Export the MV volume group (vgmv) into the map file vgmv.map. umount /MV_fs01 umount /MV_fs02 umount /MV_fs03 vgchange -a n /dev/vgmv (6) Activate volume group (Backup server) Import and activate the volume group. vgchange -a y /dev/vgmv (7) Execute fsck (Backup server) Perform file system consistency check and repair. fsck -t ext3 -y /dev/vgmv/vol01 fsck -t ext3 -y /dev/vgmv/vol02 fsck -t ext3 -y /dev/vgmv/vol03 (8) Mount logical volumes (Backup server) Mount VxFS file systems belonging to the volume group. mount -t ext3 /dev/vgmv/vol01 /RV_fs01 mount -t ext3 /dev/vgmv/vol02 /RV_fs02 mount -t ext3 /dev/vgmv/vol03 /RV_fs03 (2.3) RV separation from backup server (when using LVM in ext) (1) Unmount logical volumes (Backup server) umount /RV_fs01 umount /RV_fs02 umount /RV_fs03 139 Appendix B FileSystem Option Operating Procedures (2) Deactivate the RV and delete volume group information (Backup server) vgchange -a n /dev/vgmv vgexport /dev/vgmv (3) Cautions  FileSystem Option secures file system static points. Static points of business applications must be secured in operation.  RV must be paired with all of the MVs configuring the disk group or volume group.  RV must also be paired with MV added to a disk group or volume group.  When the disk configuration is new or changed, be sure to re-create the application server volume list (iSMvollist -r).  When the disk configuration is new or changed, the pair file used for MV/RV separation or replication (pair_file) must also be created or updated.  Creation or update of the volume list on the backup server is not necessary unless data replication operations will be performed on the backup server.  The following procedure is necessary in the case of one generation (one RV for one MV) and when managing multiple generations (handling multiple RVs for one MV) on the same backup server. (1) Set offline for STATUS of all the RV disks from right after deporting until right before importing. vxdisk offline sdX (Updates to STATUS: offline) vxdisk list (Confirms STATUS: offline) (2) Set online for STATUS of RV disks when importing to a backup server. RV disks not to be imported must be offline. vxdisk online sdX (Updates to STATUS: online) vxdisk list (Confirms STATUS: online/offline) * Care is needed since performing an operation such as importing after mistakenly setting STATUS to online/offline could make VxVM unable to recognize the RV disks.  Addition of a disk to a disk group or volume group must not be performed during backup.  Separation or replication must not be performed during VxVM disk or subdisk movement. Data could lose its integrity.  Besides FileSystem Option commands, ControlCommand, VxVM, VxFS, and OS commands are used in this operating procedure. For details on commands outside FileSystem Option, refer to the respective manuals. 140 Appendix B FileSystem Option Operating Procedures B.2 When Using Snapshot Functions (1.1) Initial settings (when using VxVM in VxFS) It is assumed that logical disks used as BV are recognized by the operating system on the application server. Set the following initial configuration. [Initial configuration] BV0 _____ vol01 BV1 _____ vol02 BV2 _____ vol03 (1) Create BV generation and link-volume (Application server) Perform BV generation and link-volume creation from iSM (Configuration Setting screen). Make the BV1, BV2, and BV3 generations SV1, SV2, and SV3, respectively. Make the BV1, BV2, and BV3 link-volumes LV1, LV2, and LV3, respectively. (2) Create pair file (Application server) Create the pair file to use in snapshot operations. (Sample setting: pair_file) 0:BV1 0:SV1 0:BV2 0:SV2 0:BV3 0:SV3 (3) Create volume list (Application server) Create the volume list. iSMvollist -r (4) Create disk group and volumes (Application server) Create a disk group (disk group name: dg01) and volumes (volume names: vol01, vol02, vol03). vxdg init dg01 BV1=sdX vxdg -g dg01 adddisk BV2=sdX vxdg -g dg01 adddisk BV3=sdX vxassist -g dg01 make vol01 2g BV1 vxassist -g dg01 make vol02 2g BV2 vxassist -g dg01 make vol03 2g BV3 141 Appendix B FileSystem Option Operating Procedures (5) Create file systems (Application server) Create VxFS file systems. mkfs -t vxfs /dev/vx/rdsk/dg01/vol01 mkfs -t vxfs /dev/vx/rdsk/dg01/vol02 mkfs -t vxfs /dev/vx/rdsk/dg01/vol03 (6) Mount file systems (Application server) Mount the VxFS file systems. mount -t vxfs /dev/vx/dsk/dg01/vol01 /BV_fs01 mount -t vxfs /dev/vx/dsk/dg01/vol02 /BV_fs02 mount -t vxfs /dev/vx/dsk/dg01/vol03 /BV_fs03 (1.2) Snapshot creation and operation (when using VxVM in VxFS) An example of a procedure that uses snapshot functions to back up volumes vol01, vol02, and vol03 of the disk group (dg01) that is configured on BV1, BV2, and BV3 is described. (1) Unmount LV (SV) (Backup server) If snapshots are being used, unmount logical volumes that are being used as file systems. umount /SV_fs01 umount /SV_fs02 umount /SV_fs03 (2) Deport disk group (Backup server) If snapshots are being used, deport the disk group. vxdg deport dg01 vxdisk offline sdX (3) Unlink LV and SV (Backup server) If snapshots are being used, unlink LV and SV. iSMsc_unlink -lv LV1 -lvflg ld iSMsc_unlink -lv LV2 -lvflg ld iSMsc_unlink -lv LV3 -lvflg ld (4) Create snapshot (Application server) Create a snapshot of the disk group (dg01) in a state in which a business application static point has been secured. iSMsc_fscreate -b dg -f pair_file dg01 142 Appendix B FileSystem Option Operating Procedures (5) Link LV and SV (Application server) Link SV and LV in order to access the snapshot. iSMsc_link -lv LV1 -lvflg ld -sv SV1 -svflg ld iSMsc_link -lv LV2 -lvflg ld -sv SV2 -svflg ld iSMsc_link -lv LV3 -lvflg ld -sv SV3 -svflg ld (6) Import disk group (Application server) Set online for LV (SV) to be imported to a backup server by the following command. vxdisk online sdX Perform disk group importing and activation. vxdctl enable vxdg -C import dg01 vxvol -g dg01 startall (7) Execute fsck (Backup server) Perform file system consistency check and repair. fsck -t vxfs /dev/vx/dsk/dg01/vol01 fsck -t vxfs /dev/vx/dsk/dg01/vol02 fsck -t vxfs /dev/vx/dsk/dg01/vol03 (8) Mount logical volumes (Backup server) Mount VxFS file systems belonging to the disk group. mount -t vxfs /dev/vx/dsk/dg01/vol01 /SV_fs01 mount -t vxfs /dev/vx/dsk/dg01/vol02 /SV_fs02 mount -t vxfs /dev/vx/dsk/dg01/vol03 /SV_fs03 (1.3) Snapshot deletion (when using VxVM in VxFS) An example of a procedure to delete snapshots that have become unnecessary is described. (1) Unmount logical volumes (Backup server) umount /SV_fs01 umount /SV_fs02 umount /SV_fs03 (2) Deport disk group (Backup server) vxdg deport dg01 vxdisk offline sdX 143 Appendix B FileSystem Option Operating Procedures (3) Unlink LV and SV (Backup server) iSMsc_unlink -lv LV1 -lvflg ld iSMsc_unlink -lv LV2 -lvflg ld iSMsc_unlink -lv LV3 -lvflg ld (4) Delete snapshot (Application server) Delete the snapshot of the disk group (dg01). iSMsc_fsdelete -b dg -f pair_file dg01 (2.1) Initial settings (when using LVM in ext) It is assumed that logical disks used as BV are recognized by the operating system on the application server. Set the following initial configuration. [VG initial configuration] BV1(dev/sdX) --- vol01 BV2(dev/sdX) --- vol02 BV3(dev/sdX) --- vol03 [Volume configuration information for snapshot] BV1:/dev/sdX --- SV1 --- LV1:/dev/sdY BV2:/dev/sdX --- SV2 --- LV2:/dev/sdY BV3:/dev/sdX --- SV3 --- LV3:/dev/sdY (1) Create BV generation and link-volume (Application server) Perform BV generation and link-volume creation from iSM (Configuration Setting screen). Make the BV1, BV2, and BV3 generations SV1, SV2, and SV3, respectively. Make the BV1, BV2, and BV3 link-volumes LV1, LV2, and LV3, respectively. (2) Create pair file (Application server) Create the pair file to use in snapshot operations. (Sample setting: pair_file) 0:BV1 0:SV1 0:BV2 0:SV2 0:BV3 0:SV3 (3) Create volume list (Application server) Create the volume list with the iSMvollist command. iSMvollist –r 144 Appendix B FileSystem Option Operating Procedures (4) Create physical volume (Application server) Create the LVM physical volume that uses the volume group. pvcreate /dev/sdX pvcreate /dev/sdX pvcreate /dev/sdX (5) Create volume group and volumes (Application server) Create a volume group (Volume group name: vgbv) and volumes (volume names: vol01, vol02, vol03). vgcreate /dev/vgbv /dev/sdX /dev/sdX /dev/sdX lvcreate -L 1000 -n vol01 /dev/vgbv lvcreate -L 1000 -n vol02 /dev/vgbv lvcreate -L 1000 -n vol03 /dev/vgbv (6) Create file systems (Application server) Create VxFS file system. mkfs -t ext3 /dev/vgbv/vol01 mkfs -t ext3 /dev/vgbv/vol02 mkfs -t ext3 /dev/vgbv/vol03 (7) Mount file systems (Application server) Mount the VxFS file systems. mount -t ext3 /dev/vgbv/vol01 /BV_fs01 mount -t ext3 /dev/vgbv/vol02 /BV_fs02 mount -t ext3 /dev/vgbv/vol03 /BV_fs03 (2.2) Snapshot creation and operation (when using LVM in ext) An example of a procedure that backs up volumes vol01, vol02, and vol03 of the volume group (vgbv) that is configured on BV1, BV2, and BV3 using the snapshot function is described. (1) Unmount LV (SV) (Backup server) If using snapshot, unmount the logical volumes that are being used as file systems. umount /SV_fs01 umount /SV_fs02 umount /SV_fs03 145 Appendix B FileSystem Option Operating Procedures (2) Deactivate the LV and delete volume group information (Backup server) Deactivate and delete the LVM volume group to which the LV belongs from the backup server. vgchange -a n /dev/vgbv vgexport /dev/vgbv (3) Unlink LV and SV (Backup server) If using snapshot, unlink LV and SV. iSMsc_unlink -lv LV1 -lvflg ld iSMsc_unlink -lv LV2 -lvflg ld iSMsc_unlink -lv LV3 -lvflg ld (4) Create snapshot (Application server) Create a snapshot of the volume group (vgbv) in a state in which a business application static point has been secured. iSMsc_fscreate -b vg -f pair_file vgbv (5) Link LV and SV (Backup server) Link SV and LV in order to access the snapshot. iSMsc_link -lv LV0 -lvflg ld -sv SV0 -svflg ld iSMsc_link -lv LV1 -lvflg ld -sv SV1 -svflg ld iSMsc_link -lv LV2 -lvflg ld -sv SV2 -svflg ld (6) Export BV volume group information (Application server) Export the BV volume group (vgbv) into the map file vgbv.map. vgchange -a n /dev/vgbv (7) Execute fsck (Backup server) Perform file system consistency check and repair. fsck -t ext3 -y /dev/vgbv/vol01 fsck -t ext3 -y /dev/vgbv/vol02 fsck -t ext3 -y /dev/vgbv/vol03 (8) Mount logical volumes (Backup server) Mount VxFS file systems belonging to the volume group. mount -t ext3 /dev/vgbv/vol01 /SV_fs01 mount -t ext3 /dev/vgbv/vol02 /SV_fs02 mount -t ext3 /dev/vgbv/vol03 /SV_fs03 146 Appendix B FileSystem Option Operating Procedures (2.3) Snapshot deletion (when using LVM in ext) An example of a procedure to delete snapshots that have become unnecessary is described. (1) Unmount logical volumes (Backup server) umount /SV_fs01 umount /SV_fs02 umount /SV_fs03 (2) Deactivate the LV and delete volume group information (Backup server) vgchange -a n /dev/vgbv vgexport /dev/vgbv (3) Unlink LV and SV (Backup server) iSMsc_unlink -lv LV0 -lvflg ld iSMsc_unlink -lv LV1 -lvflg ld iSMsc_unlink -lv LV2 -lvflg ld (4) Delete snapshot (Application server) Delete the snapshot of the volume group (vgb1). iSMsc_fsdelete -f pair_file vgbv (3) Cautions  FileSystem Option secures file system static points. Static points of business applications must be secured in operation.  Generations (SVs) and link-volumes must be created for all BVs configuring the disk group/volume group.  When the disk configuration is newly created or changed, be sure to re-create the application server volume list (iSMvollist -r).  When the disk configuration is newly created or changed, the pair file (pair_file) must also be created or updated.  The following procedure is necessary when using LV (SV) on a backup server. (1) Set offline for STATUS of all the LV (SV) disks from right after deporting until right before importing. vxdisk offline sdX (Updates to STATUS: offline) vxdisk list (Confirms STATUS: offline) (2) Set online for STATUS of LV (SV) disks when importing to a backup server. LV (SV) disks not to be imported must be offline. vxdisk online sdX (Updates to STATUS: online) vxdisk list (Confirms STATUS: online/offline)  Addition of a disk to a disk group/volume group must not be performed during backup.  Besides FileSystem Option commands, ControlCommand, VxVM, VxFS, and OS commands are used in this operating procedure. For details on commands outside FileSystem Option, refer to the respective manuals. 147 Appendix C License Appendix C License C.1 Flex License The flex manual is placed under the same licensing conditions as the rest of flex: Copyright c 2001, 2002, 2003, 2004, 2005, 2006, 2007 The Flex Project. Copyright c 1990, 1997 The Regents of the University of California. All rights reserved. This code is derived from software contributed to Berkeley by Vern Paxson. The United States Government has rights in this work pursuant to contract no. DE-AC03-76SF00098 between the United States Department of Energy and the University of California. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 148 Index iSMsc_fscreate command reference ............................. 61 iSMsc_fsdelete command .......................................45, 66 A L ATgroup ................................. 1, 2, 21, 27, 31, 35, 49, 55 Atomic Group ................................................................. 1 LVM ................................................................................ 1 B P backup ............................................................. 1, 9, 12, 14 backup to magnetic tapes ................................................ 9 pair file description method ..... 51, 53, 56, 59, 62, 64, 67 D R data replication function ................................................. 2 data replication operation ........................................... 123 disk backup ................................................................... 10 replication function ......................................................... 2 return code ..................................................................... 88 S E secondary use in search tasks and test tasks ...........11, 13 separation function .......................................................... 2 snapshot creation function .............................................. 6 snapshot deletion function .............................................. 6 snapshot function ............................................................ 6 snapshot operation ....................................................... 126 error codes returned by data replication function ... 77, 88 error codes returned by snapshot function.................. 112 ext .................................................................................... 1 I V iSMrc_fsreplicate command ......................................... 28 iSMrc_fsreplicate command reference ......................... 55 iSMrc_fsseparate command .................................... 16, 49 iSMsc_fscreate command ............................................. 37 VxFS ................................................................................ 1 VxVM .............................................................................. 1 149