NEC Storage Manager Data Replication User’s Manual (Installation and Operation Guide for Windows) IS016-5E
© NEC Corporation 2001-2004 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 describes how to use the data replication function provided by NEC Storage DynamicDataReplication Ver2, NEC Storage RemoteDataReplication Ver2, and NEC Storage ReplicationControl. The data replication function consists of the replication volume creation function provided in a disk array subsystem and software to manage and operate it. It utilizes replication volume to make business operation more effective.
Description Corresponding Manual Messages Handbook NEC Storage Manager Messages Handbook (IS010) Data Replication User’s Manual (Function Guide) NEC Storage Manager Data Replication User’s Manual (Function Guide) (IS015) Data Replication Command Reference NEC Storage Manager Data Replication Command Reference (IS021) PerformanceMonitor User’s Manual NEC Storage PerformanceMonitor User’s Manual (IS025) 6.
Contents Chapter 1 Installation Procedure.......................................................................................................................................1 1.1 Installation Procedure..................................................................................................................................................1 1.2 System Configuration........................................................................................................................................
This page is intentionally left blank.
Chapter 1 Installation Procedure Chapter 1 Installation Procedure This chapter describes the system installation procedures showing an example of a tape backup system that uses the 2000 series disk array subsystem. 11..11 IIn nssttaallllaattiio on nP Prro occeed du urree Installation works are outlined below. For details of the procedures, refer to the associated sections. 1. Determining the system configuration y Select necessary hardware configuration. y Select necessary software configuration. 1.2.
Chapter 1 Installation Procedure 11..22 S Syysstteem mC Co on nffiig gu urraattiio on n 11..22..11 H Haarrddw waarree C Coonnffiigguurraattiioonn Select hardware components according to the business conditions, requirements, disk capacity, and so forth. Figure 1-1 shows an example of hardware configuration. Management Server LAN LAN Specific for Interconnection Business Server (Operated primarily) Switch Figure 1-1 Backup Server Dir No.1 Port No.1 Switch Dir No.0 Port No.0 Dir No.1 Port No.
Chapter 1 Installation Procedure 11..22..22 S Sooffttw waarree C Coonnffiigguurraattiioonn Select software to be used according to the hardware components, operating conditions, etc. Figure 1-2 shows a software configuration example. Storage Manager LAN Business Server (Operated primarily) Business Server (Standby) ReplicationControl PathManager Backup Server LTO Switch Dir No.1 Port No.1 Switch Dir No.1 Port No.0 Dir No.0 Port No.0 ReplicationControl PathManager Dir No.0 Port No.
Chapter 1 Installation Procedure 11..33 S So offttw waarree IIn nssttaallllaattiio on n 11..33..11 R Reepplliiccaattiioonn M Maannaaggeem meenntt (1) Operating Environment Replication Management (Server) The replication management function is included in the iSM server. For the operating environment, refer to the “User’s Manual” or “User’s Manual (UNIX)” in accordance with your OS. Replication Management (GUI) The replication management is an expanded function of the iSM client.
Chapter 1 Installation Procedure Replication Management (GUI) Uninstallation Refer to the “User’s Manual” or “User’s Manual (UNIX)” in accordance with your OS to uninstall the Replication Management (GUI). (4) Software Update iSM Server Update To update the iSM server, uninstall the existing software, and then install the new software. Replication Management (GUI) Update To update the iSM client, uninstall the existing software, and then install the new software. 11..33..
Chapter 1 Installation Procedure (2) ReplicationControl Software Installation To install ReplicationControl, follow the procedure below. (1) Log on as the Administrator. (2) Set the ReplicationControl installation media on CD-ROM drive and execute the following install program in the CD-ROM drive: \iSMRC\SETUP.EXE (3) Follow the directions of the installer.
Chapter 1 Installation Procedure (4) Select the deletion of the following software component by using [Add/Remove Programs] ([Add or Remove Programs] for Windows Server 2003) in [Control Panel] to start uninstallation: • (5) ReplicationControl Follow the directions of the uninstaller.
Chapter 1 Installation Procedure ReplicationControl outputs the operation trace (trace log) in the folder iSMrpl\etc\trace under the folder where ReplicationControl has been installed (\Program Files\NEC\iSMrpl\etc\trace\ by default) to deal with faults if occur. In operation trace files, messages output to the standard output, standard error output, event log, and command trace and the detailed internal information are recorded. These files are used as important data for analyzing a fault if occurs.
Chapter 1 Installation Procedure 11..44 D Diisskk A Arrrraayy C Co on nffiig gu urraattiio on n For the disk array to be connected, determine the configuration for using the data replication. 11..44..11 LLooggiiccaall D Diisskk ((LLD D)) S Seelleeccttiioonn According to the disk capacity necessary for business or operation conditions, determine the logical disk (LD) and hot spare configurations.
Chapter 1 Installation Procedure Figure 1-4 shows an example of setting five pairs and one IV on the backup server as a control volume. A control volume is used when a server issues control I/O to the relevant disk array. For details of a control volume, refer to 1.5 “Control Volume Setting”, 3.9 “Control Volume”, and the “Data Replication User’s Manual (Function Guide)”.
Chapter 1 Installation Procedure 11..44..22 S Seettttiinnggss ooff D Diisskk A Arrrraayy N Naam mee,, LLooggiiccaall D Diisskk N Naam mee,, aanndd P Poorrtt N Naam mee You can assign identification names to hardware components managed by the iSM.
Chapter 1 Installation Procedure Table 1-3 gives an example of setting logical disk names and OS types for an LD configuration example when a control volume is used (Figure 1-4). Table 1-3 Example of Setting Logical Disk Names and OS Types (When a Control Volume Is Used) LD No.
Chapter 1 Installation Procedure 11..44..33 A Acccceessss C Coonnttrrooll S Seettttiinngg Normally, in a system without clusters, one volume cannot be connected to more than one server to prevent data inconsistency due to file update from servers. To prevent erroneous updates to this volume or erroneous changes to disk configuration on the business servers, the RV must be separated using Access Control, etc. from the business server that uses the MV.
Chapter 1 Installation Procedure Table 1-5 Access Control Setting Example Director No. Port No. 00 00 01 00 00 01 01 01 Access Control settings Server connected LD00 to LD04 Business server LD05 to LD09 Backup server Table 1-6 gives an Access Control setting example for an LD configuration example when a control volume is used (Figure 1-4). Table 1-6 Access Control Setting Example (When a Control Volume is Used) Director No. Port No.
Chapter 1 Installation Procedure 11..44..55 P Paaiirr C Coonnffiigguurraattiioonn S Seettttiinngg In the basic pair configuration, one RV is connected to one MV. For certain operation conditions, more than one RV may be connected, but select the basic or parallel configuration for backup operations. The MV and RV to be paired must have the same LD capacity and OS type.
Chapter 1 Installation Procedure • An RV of a maximum of four volumes can be set for one PV. For DynamicDataReplication, an RV of a maximum of three volumes can be set at a time, however. • An RV can be allocated to a maximum of two disk arrays for one PV. • The DynamicDataReplication can be set in only one layer in the disk array. • You cannot set dRV directly for dRV. • Volumes with different volume capacities cannot be set as a pair. • Unless the OS type is the same, the pair setting cannot be executed.
Chapter 1 Installation Procedure 11..55 C Co on nttrro oll V Vo ollu um mee S Seettttiin ng g A control volume is used when a server issues control I/O to the relevant disk array. Select one of the logical disks connected to each server for each disk array as the volume for issuing I/O to that disk array and register the volume in the Volume List.
Chapter 1 Installation Procedure Then, select [Define Control Volume] in [Operation] in the Volume List Display screen to open the Define Control Volume screen. Figure 1-9 Define Control Volume Screen “Selected Volume List” Lists already registered control volumes. “Candidate Volume List” Lists candidate logical disks that can be registered as a control volume. 11..55..
Chapter 1 Installation Procedure (1) Select a logical disk you want to use as a control volume from “Candidate Volume List”. (2) Click the [Add] button. (3) The selected logical disk is registered in “Selected Volume List”. Figure 1-10 Registering a Control Volume 11..55..33 S Saavviinngg R Reeggiisstteerreedd D Daattaa Click the [OK] button on the Define Control Volume screen. A confirmation message appears asking if you want to save definition information.
Chapter 1 Installation Procedure Figure 1-12 The definition of control volume: Termination Message Screen Clicking the [OK] button closes the Define Control Volume screen and displays the Volume List Display screen again. Clicking the [Cancel] button in the Define Control Volume screen displays a confirmation message asking if you want to cancel the definition.
Chapter 1 Installation Procedure 11..66 V Vo ollu um mee L Liisstt C Crreeaattiio on n Creation of Volume List is required before using replication operation command. A Volume List is created by the iSMvollist command with an argument -cr. Execute iSMvollist command by a user that belongs to Administrators group. When you have already performed [Create/Update Volume List] using the Volume List Display function (screen operation) according to the instructions described in 1.
Chapter 1 Installation Procedure 11..77 P Prreep paarriin ng gV Vo ollu um mee When using a volume for the first time for replication operation or changing the MV partition size, execute the steps given below for the target volume. In data replication operation using ReplicationControl Ver3.
Chapter 1 Installation Procedure Step 3. Checking RV volume In Windows 2000, using [Disk Management] (Windows), check that the disk to be used as RV is in an unassigned area. If signature is not found, execute “Signature Disk” here. If RV has partitions, delete them and place the area in unassigned state. On Windows Server 2003, use [Disk Management] (Windows) to create partitions on the disk to be used as the RV in advance so that the disk has the same partition configuration as the MV.
Chapter 1 Installation Procedure Step 7. Setting pair Use the Replication Management (GUI) for setting a pair. executed by using the iSMrc_pair command. In addition, the pair setting can also be By checking the vollist_data.txt that stores the Volume List information created in step 4 and the volume displayed by the Replication Management, determine the target disk for replication and set a pair. For pair setting, note the following: • The MV and RV disk capacities must be the same.
Chapter 1 Installation Procedure Flush Normal End 2001/02/21 11:08:14 disk10 dev001 WN \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ G: Step 10. Unmounting MV Before separating MV/RV, you must create a complete static point of the MV data. The purpose of this is to write out all data that is not reflected, including the file system control data and the metadata to disk and to keep the MV and RV data consistency by restricting accesses to the logical volume.
Chapter 1 Installation Procedure Separating… Separate Normal End 2001/02/21 11:08:21 MV:10 dev001 WN \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ G: RV:- dev002 WN Note that, if the RV access restriction has been set to Read Only (ro) when executing Separate, attempting a write operation to that drive with the volume mounted causes a write error. In such a case, change the RV access restriction to Read/Write (rw) from the Replication Management (GUI). Step 12.
Chapter 1 Installation Procedure Upon successful creation of Volume List, the following message appears: iSMvollist: Info: iSM11701: Volume list is created successfully. Output the Volume List data into the vollist_data.txt. iSMvollist -a > vollist_data.txt * If a logical disk name has been changed using the iSM, the Volume List must be updated.
Chapter 1 Installation Procedure 11..88 P Prreep paarraattiio on n ffo orr O Op peerraattiio on n To operate the system in the Replicate state, take the following steps and re-synchronize (Replicate). The following procedures are not required when the systems are operated separately. Step 1. Executing RV file system flush Flush RV file system and write the unwritten data in file system buffer onto disk. iSMrc_flush –drv H: Then, the following message appears and the data is flushed.
Chapter 1 Installation Procedure iSMrc_umount: Info: iSM13221: Resetting drive letter (H:) (\\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\) has succeeded. Umount Normal End 2001/02/21 11:21:14 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: Step 3. Executing Replicate Execute Replicate and re-synchronize (Replicate).
Chapter 2 Operation and Maintenance Chapter 2 Operation and Maintenance This chapter describes an example of operation using the Data Replication function, the operation procedure for replication, and the trouble-shooting for faults that may occur during operations. 22..11 O Op peerraattiio on nss 22..11..11 E Exxaam mppllee ooff B Baacckkuupp O Oppeerraattiioonn This section describes an example of backup operation by using the Data Replication function.
Chapter 2 Operation and Maintenance Work flow of the backup example Step 1. Step 4. Executing Replicate Step 5. Terminating applications Step 6. Flushing MV file system Step 7. Unmounting MV Step 8. Executing Separate Step 9. Mounting MV Terminating applications Step 2. Flushing RV file system Step 3. Unmounting RV Step 10. Restarting applications Step 11. Mounting RV Step 12. Restarting applications Step 13.
Chapter 2 Operation and Maintenance (2) Operation procedure Step 1. Terminating applications (backup server) To maintain data consistency, terminate or halt applications and specified services that are accessing the volume concerned. If shared folders are used on the volume concerned, cancel sharing temporarily. If application or service has not been halted or terminated, or accesses to shared folder exist, unmounting in step 3 fails.
Chapter 2 Operation and Maintenance Then, the following message appears and RV is unmounted. Umount Start 2001/02/21 12:27:02 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: iSMrc_umount: Info: iSM13221: Resetting drive letter (H:) (\\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\) has succeeded. Umount Normal End 2001/02/21 12:27:02 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: Step 4.
Chapter 2 Operation and Maintenance Step 5. Terminating applications (business server) To maintain data consistency, terminate or halt applications and specified services that are accessing the target volume. If a shared folder is used on the target volume, cancel the sharing temporarily. If applications and services have not been halted or terminated, or a shared folder is accessed, the unmounting operation in step 7 will fail.
Chapter 2 Operation and Maintenance Step 7. Unmounting MV (business server) You must create a perfect static point of MV data. This is for writing the metadata of the file system completely to the disk. This is also for suppressing I/O to the logical volume to keep data consistency of MV and RV. To keep data consistency of MV and RV, unmount MV after stopping operation, and cancel association between the volume and file system.
Chapter 2 Operation and Maintenance Then, the following message is displayed and MV is separated. Separate Start 2001/02/21 12:23:16 MV:10 dev001 WN \\?\Volume{ce49f299-614e-11d5-b1df-009027520bce}\ G: RV:- dev002 WN Separating.....
Chapter 2 Operation and Maintenance Step 10. Restarting applications (business server) Restart the applications closed in Step 5. If services were halted in step 5, restart the services by the following procedures. If services were not halted in step 5, executing of the following is not required. (Example) Starting service NET START (service name) To start the service “ESMCommonService”, specify as shown below.
Chapter 2 Operation and Maintenance Step 12. Restarting applications (backup server) Start the applications and services terminated in step 1. For the procedures to start services and share the folder, refer to step 10. Step 13. Executing backup (backup server) Use backup software to back up the data copied to RV to the tape. 22..11..22 E Exxaam mppllee ooff R Reessttoorriinngg M Maasstteerr V Voolluum mee D Daattaa This section describes procedures of restoring master volume (MV) data.
Chapter 2 Operation and Maintenance (2) Data restoration with use of replication function The following describes the procedures of completely restoring data using backup tape, upon failure of data file. The procedures assume that MV data file has physical or logical failure, and the tape contains backup data previously retrieved.
Chapter 2 Operation and Maintenance Work flow for an example of the master volume data recovery Step 1. Terminating applications Step 2. Repairing MV Step 4. Flushing MV file system Step 5. Unmounting MV Step 9. Step 3. Executing Restore from tape Step 6. Halting service Step 7. Flushing RV file system Step 8. Unmounting RV Executing Restore Step 10. Mounting MV Step 11. Restarting applications Step 12. Waiting for Separated state Step 13.
Chapter 2 Operation and Maintenance Step 1. Terminating applications (business server) Terminate or halt applications and specified services that are accessing the volume where a fault has occurred. If a shared folder is used on the target volume, cancel the sharing temporarily.
Chapter 2 Operation and Maintenance Step 3. Executing Restore from tape (backup server) Restore data from the tape to RV, using backup software. Backup Software such as ARCserve, BackUp Exec, NetBackup, etc. Tape RV Figure 2-5 Step 4. Restoring Backup Data to RV Flushing MV file system (business server) Flush the MV file system and discard data in the file system buffer. iSMrc_flush -drv D: Then, the following message appears and flushing is executed.
Chapter 2 Operation and Maintenance D: If normal unmounting fails, execute unmounting again by specifying the -force option. iSMrc_umount -drv D: -force Step 6. Halting service (backup server) Terminate or halt applications and services that may prevent RV from being unmounted. If applications and services have not been halted or terminated, the unmounting operation in step 8 will fail.
Chapter 2 Operation and Maintenance # Type:MV Type:RV ld:dev001 ld:dev002 When Restore with RV protection specified is executed, Separate is automatically executed after Restore has been completed. iSMrc_restore -file disks.txt -mode protect Execute Restoration. MV RV Figure 2-6 Step 10. Executing Restoration Mounting MV (business server) Use MV again on applications. Mount MV to associate it with a file system.
Chapter 2 Operation and Maintenance If sharing of the folder was cancelled in step 1, specify the sharing again. If sharing was not cancelled in step 1, it is not necessary to execute the following. (Example) Sharing of shared folder NET SHARE share_name=drive_letter: path To enable the sharing of the folder mv_folder1, specify as shown below. NET SHARE mv_folder1=G:\mv_folder1 Step 12.
Chapter 2 Operation and Maintenance Use RV again as a backup volume. Step 14. Restarting service (backup server) Resume the applications and services that have been terminated in step 6. If the services have been halted in step 6, restart the services by the following procedure. services were not halted in step 6, it is not necessary to execute the following. (Example) Restarting service NET START (service name) To restart the service “ESMCommonService”, specify as shown below.
Chapter 2 Operation and Maintenance 22..11..33 E Exxaam mppllee ooff U Ussiinngg R Reepplliiccaattiioonn V Voolluum meess This section describes how to build the environment same as that used for actual operations, using a replication volume. Figure 2-8 shows the replication volume structure. Backup Server Business Server Disk Copy MV RV Master Volume Replication Volume Use replication volume.
Chapter 2 Operation and Maintenance By using the Separate function which enables the use of RV also in the middle of separation while reflecting the difference of MV and RV, it is not necessary to wait for the copy operation to finish, thereby reducing the time duration when the master operations are halted. Also, it is possible to refer to the replication volume for the latest data, thereby reducing the time duration when the server-side operations are halted.
Chapter 2 Operation and Maintenance Step 10. Restarting applications Step 11. Mounting RV Step 12. Restarting applications The following describes the procedure for executing replication control for the RV that is can be used as a file system through the prepared volumes: Step 1. Terminating applications (backup server) To maintain data consistency, terminate or halt applications and specified services that area accessing the volume concerned.
Chapter 2 Operation and Maintenance When executing unmounting, all application software, that may access the drive, must be terminated in advance. Refer to descriptions about unmounting Chapter 3 “Notes” also.
Chapter 2 Operation and Maintenance Step 5. Terminating applications (business server) To maintain data consistency, terminate or halt applications that are accessing the volume concerned. If application has not been terminated, unmounting in step 7 fails. If shared folders are used on the volume concerned, cancel sharing temporarily. (Example) Stopping service NET STOP (service name) To stop the service “ESMCommonService”, specify as shown below.
Chapter 2 Operation and Maintenance In addition, although separating is allowed without unmounting in this step, unmounting upon replication and restoration is mandatory. iSMrc_umount -drv G: Then, the following message is displayed and MV is unmounted. Umount Start 2001/02/21 12:23:15 disk10 dev001 WN \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ G: Umount Normal End 2001/02/21 12:23:15 disk10 dev001 WN \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ G: Step 8.
Chapter 2 Operation and Maintenance Step 9. Mounting MV (business server) To associate MV and the file system, mount MV. iSMrc_mount -drv G: Then, the following message is displayed. Mount Start MV is mounted and can be used as a file system. 2001/02/21 12:23:17 disk10 dev001 WN \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ G: Mount Normal End 2001/02/21 12:23:17 disk10 dev001 WN \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ G: Step 10.
Chapter 2 Operation and Maintenance Mount Start 2001/02/21 12:26:14 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: iSMrc_mount: Info: iSM13220: Setting drive letter (H:) (\\?\Volume{37d84cca-2507- 11d5-a0f7-00004c714491}\) has succeeded. Mount Normal End 2001/02/21 12:26:14 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: Use RV again for backup on applications. Step 12.
Chapter 2 Operation and Maintenance 22..11..44 R Reessttaarrttiinngg B Buussiinneessss//B Baacckkuupp S Seerrvveerr This section describes procedures for restarting a server that uses the data replication function. The following describes the procedures for restarting backup server. Step 2. Step 9. Step 1. Shutting down server Step 3. Restarting server Step 4. Scanning disks Step 5. Executing CHKDSK Step 6. Terminating applications Step 7.
Chapter 2 Operation and Maintenance Step 1. Shutting down server (backup server) Shut down a server that is connected with RV. Step 2. Executing Separate (business server) Execute Separate on RV that is not separated and connected with the backup server. If the RV is separated already, separation is not required. This example uses the replication file for the execution according to the following settings.
Chapter 2 Operation and Maintenance Step 5. Executing CHKDSK (backup server) In step 2, separation was executed without specifying a static point. Execute CHKDSK /F to remove inconsistency in file system. CHKDSK H: /F Step 6. Terminating applications (backup server) To maintain data consistency, terminate or halt applications and specified services. (Example) Terminating service NET STOP (service name) To stop the service “ESMCommonService”, specify as shown below. NET STOP ESMCommonService Step 7.
Chapter 2 Operation and Maintenance Then, the following message appears and RV is unmounted. Umount Start 2001/02/21 11:21:14 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: iSMrc_umount: Info: iSM13221: Resetting drive letter (H:) (\\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\) has succeeded. Umount Normal End 2001/02/21 11:21:14 disk11 dev002 WN \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ H: Step 9.
Chapter 2 Operation and Maintenance 22..22 M Meeaassu urreess ffo orr E Errrro orrss 22..22..11 E Errrroorr TTyyppeess Data replication errors can be categorized as follows: (1) HW fault unique to replication (2) iSM Server or client fault (3) ReplicationControl abnormal end (4) Down of server machine connected to RV (5) Invalid product 22..22..
Chapter 2 Operation and Maintenance Figure 2-9 An Example of the Copy Fault Occurrence Screen Operations after recovering from a copy fault For information on operation to recover the state of the pair where the copy fault occurred to the normal state after removing the cause of the copy fault, refer to 3.3.20 “Display Copy Fault List” in the “Data Replication User’s Manual (Function Guide)”.
Chapter 2 Operation and Maintenance Figure 2-10 An Example of the Link Failure Occurrence Screen Operations after recovering from a link fault After you remove the cause of the link fault, check that the state of the path is normal in this screen. If a copy fault occurs due to this fault, refer to 3.3.20 “Display Copy Fault List” in the “Data Replication User’s Manual (Function Guide)” to recover from the failure. 22..22..
Chapter 2 Operation and Maintenance 22..22..44 A Abbnnoorrm maall E Enndd ooff R ReepplliiccaattiioonnC Coonnttrrooll ReplicationControl outputs error contents to the standard output, standard error output, event log, command trace, or operation trace when an error has occurred. The standard output, standard error output, event log, or command trace records the messages described in the “Messages Handbook”. Take necessary actions depending on the message.
Chapter 2 Operation and Maintenance - When iSMrc_umount command terminates abnormally on business server Step 1. Terminate application (backup server) Halt applications and services with programs running on server, that are referring to a volume concerned. Step 2. After verifying halt of applications and services, execute iSMrc_umount again. Executing CHKDSK (backup server) Execute the CHKDSK to maintain a static point of the file system.
Chapter 2 Operation and Maintenance iSM13224: MV is restored. Volume Name: mount point volume name Mount Point: drive letter or NTFS folder path name Step 2. Re-setting the drive letter and remounting MV into the NTFS folder Start [Disk Management]. According to the collected MV volume information (drive letter and mount point volume name), operate the volume with [Change Drive Letter and Path] to set the drive letter and mount the MV with the NTFS folder path name specified.
Chapter 2 Operation and Maintenance Access to “H:” Figure 2-12 My Computer Screen When RV is “Not Ready” and cannot be accessed, the following message appears. If this dialog appears, RV is successfully unmounted. Figure 2-13 Media Error Message Screen If a message above does not appear and access to the volume of the target RV is allowed, an illegal RV file system is suspected. Restore the system by the restoration procedures. Restoration For restoration, take step 2 according to 2.1.
Chapter 2 Operation and Maintenance 22..22..55 D Doow wnn ooff S Seerrvveerr M Maacchhiinnee C Coonnnneecctteedd ttoo R RV V When the server connected to RV has gone down, RV may not be recognized from the Operating System after restarting the server. This may occur when the server is restarted while the RV is placed in the Not Ready (unavailable for read or write) state by executing Replicate or Restore or while it is unmounted by the iSMrc_umount command and is in the Not Ready state on Windows 2000.
Chapter 2 Operation and Maintenance (2) If server is restarting Execute the procedure below so that the OS to recognize the RV again. Step 1. Executing Separate For all RV pairs in Replicate/Restore state, execute Separate. If ordinary Separate fails, execute Forced Separate. Step 2. Recognizing RV again Execute the following command to scan the disks and make the server recognize the disks in the Not Ready state and the volumes which cannot be mounted.
Chapter 2 Operation and Maintenance 22..22..77 IInnffoorrm maattiioonn G Gaatthheerriinngg iinn tthhee E Evveenntt ooff aa FFaauulltt When an error whose reason is unknown has occurred and you want to request the provider to investigate the error, you must collect information required for error analysis. (1) For Replication Management error Collect the necessary information referring to the “User’s Manual”.
Chapter 3 Notes Chapter 3 Notes This chapter describes some notes regarding management and operations of Data Replication. 33..11 W Wiin nd do ow wss S Syysstteem mV Vo ollu um meess aan nd d P Paarrttiittiio on nss Data replication handles target volumes for individual disk array’s logical disk.
Chapter 3 Notes Data replication operation using a logical disk containing multiple partitions or logical volumes is not recommended. In ReplicationControl, when the volume to be operated is recognized from the server (operating system) and can be accessed, and if the volume contains multiple partitions or logical volumes obtained by the disk configuration information of the target volume, operation is not allowed (default).
Chapter 3 Notes 33..22 F Fiillee S Syysstteem mS Seelleeccttiio on n You can configure a file system for the target MV and RV volumes for replication operations. addition, these volumes may be used as RAW devices for ORACLE, etc. In The target MV and RV paired for replication operations must have the same type of partitions and file systems. If these rules are not observed, data consistency is not guaranteed. 33..
Chapter 3 Notes Table 3-2 Copy Control States Copy Control State Foreground Copy Sub-State Sync Mode Copy State • Updates MV and RV synchronously. After completing the MV and RV update, informs the host of I/O completion. • For DDR, copy is done only to the cache. Therefore, this copy mode little lowers the performance. • For RDR, performance lowered by this copy mode is in proportion to the distance between the disk arrays.
Chapter 3 Notes Table 3-3 RV Access Restriction Access restriction Commands Description replicate restore separate Read/Write (RW) RV is enabled for read/write. - - { Read Only (RO) RV is enabled only for reading. ∆ ∆ ∆ Not Ready (NR) RV is disabled for read/write. { { - Not Available (NA) RV is not recognized by the operating system or the LU (Logical Unit) is invalid.
Chapter 3 Notes Usual file As basic operations, first temporarily halt the operations on the MV and flush the MV cache data using the command provided by replication operation. association between the file system and disks. Then, unmount the MV to release At this time, when the MV is used from another operation or service, an unmounting error occurs.
Chapter 3 Notes (3) Restoration and Data Consistency When restoring data upon failure on MV of business server, backup data existing on tape is utilized in the following operations: (i) From backup server, restore data on MV that is connected to business server via network. (ii) If tape device is connected to business server, restore data from tape to MV directly. (iii) Restore data on RV upon backup server, and synchronize MV with RV using the restoration function of data replication.
Chapter 3 Notes 33..88 A Acccceessss R Riig gh htt S Seettttiin ng gss o on n V um meess Vo ollu Access right settings on folders and files in volumes used in MV or RV are reflected on RV (or MV) after replication (or restoration), and existing access right settings are overwritten. If the overwritten access right settings are different from existing settings, the access to folders or files used before may be disabled.
Chapter 3 Notes (3) Separate, Replicate, and Restore are executed in units of disks but not units of partitions. careful in setting and operating partitions. Be To prevent operation errors and trouble, the partition settings on the MV and RV sides must be the same for all the servers. (4) To ensure data consistency, keep the following in mind: • Before executing Separate, unmount the MV. • Before executing Replicate, unmount the RV. • Before executing Restore, unmount the MV and RV.
Chapter 3 Notes (7) Upon failure of unmounting, CHKDSK /F /X is executed with mount point volume name specified. “\” at the end of mount point volume name must be omitted in the name specified for CHKDSK. (8) If you execute replication or disk operation from the terminal service client, the operation is not guaranteed. (9) The difference backup system that operates archive bits is not available for making RV data backup copies in a tape unit.
Chapter 3 Notes • On Windows 2000, when an RV is unmounted, the RV access restriction is changed to Not Ready. Accordingly, when a volume in a multi-partition configuration is unmounted, all volumes (partitions) on the relevant disk cannot be read or written. After that, another partition on the same disk cannot be accessed to read/write or be flushed by the iSMrc_flush command until the RV is mounted by the iSMrc_mount command.
Index information gathering in the event of a fault ............... 68 invalid product............................................................. 67 iSM ................................................................................3 iSMrc_umount command ............................................ 77 iSMvolgather ............................................................... 68 iSMvollist .......................................................... 9, 11, 21 A abnormal end ..............................
signature ...................................................................... 71 software installation .................................................. 4, 6 software uninstallation........................................... 4, 6, 7 software update.......................................................... 5, 7 sync mode.................................................................... 72 restarting......................................................................