Download Print this page

NEC Storage Manager User Manual

Hide thumbs

Advertisement

Quick Links

NEC Storage Manager
Data Replication User's Manual

(Installation and Operation

Guide for Windows)
IS016-5E

Advertisement

loading

  Also See for NEC Storage Manager

  Related Manuals for NEC Storage Manager

  Summary of Contents for NEC Storage Manager

  • Page 1: Installation And Operation

    NEC Storage Manager Data Replication User’s Manual (Installation and Operation Guide for Windows) IS016-5E...
  • Page 2 © 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.
  • Page 3 • NEC Storage BaseProduct Ver3.3 • NEC Storage ReplicationControl Ver3.3 3. 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.
  • Page 4 Description Corresponding Manual Messages Handbook NEC Storage Manager Messages Handbook (IS010) Data Replication User’s Manual NEC Storage Manager Data Replication User’s Manual (Function Guide) (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)
  • Page 5: Table Of Contents

    Contents Chapter 1 Installation Procedure............................1 Installation Procedure..............................1 System Configuration..............................2 1.2.1 Hardware Configuration ............................2 1.2.2 Software Configuration ............................3 Software Installation..............................4 1.3.1 Replication Management.............................4 1.3.2 ReplicationControl ..............................5 Disk Array Configuration............................9 1.4.1 Logical Disk (LD) Selection..........................9 1.4.2 Settings of Disk Array Name, Logical Disk Name, and Port Name ..............11 1.4.3 Access Control Setting ............................13 1.4.4...
  • Page 6 This page is intentionally left blank.
  • Page 7: Chapter 1 Installation Procedure

    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. Installation works are outlined below. For details of the procedures, refer to the associated sections. 1.
  • Page 8: System Configuration

    Chapter 1 Installation Procedure 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 Business Business Backup Server Specific Server Server for Inter- (Operated (Standby) connection primarily) Dir No.1 Port No.1...
  • Page 9: Software Configuration

    Chapter 1 Installation Procedure Select software to be used according to the hardware components, operating conditions, etc. Figure 1-2 shows a software configuration example. Storage Manager Backup Server Business Server Business Server (Operated (Standby) primarily) ReplicationControl PathManager ReplicationControl Dir No.1...
  • Page 10: Software Installation

    Chapter 1 Installation Procedure (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.
  • Page 11: Replicationcontrol

    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.
  • Page 12 To uninstall ReplicationControl, follow the procedure below. Log on as the Administrator. Check whether the Storage Manager Volume List or ReplicationControl command is running and whether the Volume List Display screen is open. Terminate any running command and close any screen.
  • Page 13 • Storage Manager Volume List If the Storage Manager Volume List or ReplicationControl command is running or the Volume List Display screen is open, and uninstallation is performed, a message may appear which prompts you to reboot the operating system. In this case, be sure to reboot the operating system.
  • Page 14 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.
  • Page 15: Disk Array Configuration

    Chapter 1 Installation Procedure For the disk array to be connected, determine the configuration for using the data replication. According to the disk capacity necessary for business or operation conditions, determine the logical disk (LD) and hot spare configurations. For the 4000 series and the 3000 series, disk array configurations are executed by maintenance personnel and therefore should be determined before installation.
  • Page 16 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)”.
  • Page 17: Settings Of Disk Array Name, Logical Disk Name, And Port Name

    Chapter 1 Installation Procedure You can assign identification names to hardware components managed by the iSM. Identification names can be given to the following items: • Disk array subsystem name • Logical disk name (plus OS type) • Port name A disk array subsystem name, logical disk name, and port name may be set without special restrictions, except character types and character length;...
  • Page 18 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.
  • Page 19: Access Control Setting

    Chapter 1 Installation Procedure 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.
  • Page 20: Product License Unlocking

    Chapter 1 Installation Procedure Table 1-5 Access Control Setting Example Director No. Port No. 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).
  • Page 21: Pair Configuration Setting

    Chapter 1 Installation Procedure 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. Disk Array DynamicDataReplication Disk Array...
  • Page 22 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. •...
  • Page 23: Control Volume Setting

    For details of the Volume List Display function, refer to the help of the Volume List Display screen or the “Data Replication User’s Manual (Function Guide)”. Click the Windows [Start] button and select [Storage Manager Volume List] and [Volume List Display] from [Programs] ([All Programs] for Windows Server 2003) to start the Volume List Display function.
  • Page 24: Registering A Control Volume

    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.
  • Page 25: Saving Registered Data

    Chapter 1 Installation Procedure Select a logical disk you want to use as a control volume from “Candidate Volume List”. Click the [Add] button. The selected logical disk is registered in “Selected Volume List”. Figure 1-10 Registering a Control Volume Click the [OK] button on the Define Control Volume screen.
  • Page 26: Reflecting Data To The Volume List

    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.
  • Page 27: Volume List Creation

    Chapter 1 Installation Procedure 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.5, “Control Volume Setting”, you do not have to perform the following operation.
  • Page 28: Preparing Volume

    Chapter 1 Installation Procedure 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.2 or later, if NOTREADY is specified for the UMOUNT_RVACC parameter in the replication operation option setting file, the mount point (drive letter or NTFS folder name) is automatically deleted and the automatic mount becomes unavailable at RV unmounting.
  • Page 29 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.
  • Page 30 Chapter 1 Installation Procedure Step 7. Setting pair Use the Replication Management (GUI) for setting a pair. In addition, the pair setting can also be executed by using the iSMrc_pair command. 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.
  • Page 31 Chapter 1 Installation Procedure Flush Normal End 2001/02/21 11:08:14 disk10 dev001 \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ 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.
  • Page 32 Chapter 1 Installation Procedure Separating… Separate Normal End 2001/02/21 11:08:21 MV:10 dev001 \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\ RV:- dev002 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).
  • Page 33 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. * To use a control volume, before creating a Volume List, select and register the control volume using the Define Control Volume function from the Volume List Display screen.
  • Page 34: Preparation For Operation

    Chapter 1 Installation Procedure 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.
  • Page 35 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 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ Step 3. Executing Replicate Execute Replicate and re-synchronize (Replicate). iSMrc_replicate -mv dev001 -mvflg ld -rv dev002 -rvflg ld Then , the following message appears and data copying from MV to RV is started: Replicate Start 2001/02/21 11:21:15...
  • Page 36: Chapter 2 Operation And Maintenance

    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. This section describes an example of backup operation by using the Data Replication function. Although the text describes the commands in input order, the command execution is automated by job scheduling software on the system built actually.
  • Page 37 Chapter 2 Operation and Maintenance Work flow of the backup example <Business server> <Backup server> Step 1. Terminating applications Step 2. Flushing RV file system Step 3. Unmounting RV Step 4. Executing Replicate Step 5. Terminating applications Step 6. Flushing MV file system Step 7.
  • Page 38 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.
  • Page 39 Chapter 2 Operation and Maintenance Then, the following message appears and RV is unmounted. Umount Start 2001/02/21 12:27:02 disk11 dev002 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ 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 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ Step 4. Executing Replicate (business server) Execute Replicate to copy data from MV to RV.
  • Page 40 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.
  • Page 41 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.
  • Page 42 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 \\?\Volume{ce49f299-614e-11d5-b1df-009027520bce}\ RV:- dev002 Separating..Separate Normal End 2001/02/21 12:23:16 MV:10 dev001 \\?\Volume{ce49f299-614e-11d5-b1df-009027520bce}\ RV:- dev002 If access restrictions for RV is set to Read Only (ro) when Separate is executed, a write error occurs if you execute a write operation to the drive on which the volume is mounted.
  • Page 43 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.
  • Page 44: Example Of Restoring Master Volume Data

    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.
  • Page 45 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.
  • Page 46 Chapter 2 Operation and Maintenance Work flow for an example of the master volume data recovery <Business server> <Backup server> Step 1. Terminating applications Step 2. Repairing MV Step 3. Executing Restore from tape Step 4. Flushing MV file system Step 5.
  • Page 47 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. (Example) Halting service NET STOP (service name) When halting a service “ESMCommonService”, specify as follows:...
  • Page 48 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 Figure 2-5 Restoring Backup Data to RV Step 4.
  • Page 49 Chapter 2 Operation and Maintenance 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.
  • Page 50 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. Figure 2-6 Executing Restoration Step 10. Mounting MV (business server) Use MV again on applications.
  • Page 51 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.
  • Page 52 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. If the services were not halted in step 6, it is not necessary to execute the following.
  • Page 53: Example Of Using Replication Volumes

    Chapter 2 Operation and Maintenance 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. Business Server Backup Server Disk Copy Master Volume Replication Volume Actual Operations Use replication volume.
  • Page 54 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.
  • Page 55 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.
  • Page 56 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. iSMrc_umount –drv H: Then, the following message appears and RV is unmounted: Umount Start 2001/02/21 11:21:14 disk11...
  • Page 57 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.
  • Page 58 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 \\?\Volume{822575dd-63d9-11d5-b1e0-009027520bce}\...
  • Page 59 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. MV is mounted and can be used as a file system. Mount Start 2001/02/21 12:23:17 disk10...
  • Page 60 Chapter 2 Operation and Maintenance Mount Start 2001/02/21 12:26:14 disk11 dev002 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ 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 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ Use RV again for backup on applications. Step 12. Restarting applications (backup server) Restart the applications terminated in Step 1 above.
  • Page 61: Restarting Business/Backup Server

    Chapter 2 Operation and Maintenance This section describes procedures for restarting a server that uses the data replication function. The following describes the procedures for restarting backup server. <Business server> <Backup server> Step 1. Shutting down server Step 2. Executing Separate Step 3.
  • Page 62 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.
  • Page 63 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.
  • Page 64 Chapter 2 Operation and Maintenance Then, the following message appears and RV is unmounted. Umount Start 2001/02/21 11:21:14 disk11 dev002 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ 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 \\?\Volume{37d84cca-2507-11d5-a0f7-00004c714491}\ Step 9. Executing Replicate (business server) Execute replicate for the pair that needs replication.
  • Page 65: Measures For Errors

    Chapter 2 Operation and Maintenance Data replication errors can be categorized as follows: HW fault unique to replication iSM Server or client fault ReplicationControl abnormal end Down of server machine connected to RV Invalid product The data replication function realized by HW may cause errors given below, in addition to ordinary HW faults.
  • Page 66 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”...
  • Page 67: Server Or Client Fault

    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.
  • Page 68: Abnormal End Of Replicationcontrol

    “Messages Handbook”. Take necessary actions depending on the message. The command trace is output in the folder iSMrpl\etc under the folder where ReplicationControl has been installed (\Program Files\NEC\iSMrpl\etc\ by default) with a file name beginning with “iSM_Log”. Check the contents using a text editor.
  • Page 69 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. After verifying halt of applications and services, execute iSMrc_umount again. Step 2.
  • Page 70 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.
  • Page 71 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.
  • Page 72: Down Of Server Machine Connected To Rv

    Chapter 2 Operation and Maintenance 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.
  • Page 73: Invalid Product

    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.
  • Page 74: Information Gathering In The Event Of A Fault

    (1) Log on as a member in the Administrator group. (2) Click the Windows [Start] button and select [Storage Manager Volume List] and [Difficulty Information Gather] from [Programs] ([All Programs] for Windows Server 2003).
  • Page 75: Chapter 3 Notes

    Chapter 3 Notes Chapter 3 Notes This chapter describes some notes regarding management and operations of Data Replication. Data replication handles target volumes for individual disk array’s logical disk. If replication operation is executed for a volume that contains more than one partition or logical volume in one logical disk, for a volume consisting of more than one partition or logical volume and for a volume such as a dynamic disk, data consistency is not guaranteed for certain operations.
  • Page 76 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).
  • Page 77: File System Selection

    Chapter 3 Notes You can configure a file system for the target MV and RV volumes for replication operations. In addition, these volumes may be used as RAW devices for ORACLE, etc. 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.
  • Page 78: Rv Access Restriction Setting

    Chapter 3 Notes Table 3-2 Copy Control States Copy Control State Sub-State Copy State • Updates MV and RV synchronously. After completing the MV Foreground Copy Sync Mode 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.
  • Page 79: Data Replication And Data Consistency

    Chapter 3 Notes Table 3-3 RV Access Restriction Commands Access restriction 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. RV is not recognized by the operating Not Available (NA) system or the LU (Logical Unit) is...
  • Page 80 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. Then, unmount the MV to release association between the file system and disks. At this time, when the MV is used from another operation or service, an unmounting error occurs.
  • Page 81 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: 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.
  • Page 82: Access Right Settings On Volumes

    Chapter 3 Notes 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.
  • Page 83 Chapter 3 Notes Separate, Replicate, and Restore are executed in units of disks but not units of partitions. Be careful in setting and operating partitions. To prevent operation errors and trouble, the partition settings on the MV and RV sides must be the same for all the servers. To ensure data consistency, keep the following in mind: •...
  • Page 84 Chapter 3 Notes 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. If you execute replication or disk operation from the terminal service client, the operation is not guaranteed.
  • Page 85 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.
  • Page 86: Index

    Index information gathering in the event of a fault ....68 invalid product............. 67 iSM ................3 iSMrc_umount command ..........77 iSMvolgather ............... 68 abnormal end ............... 62 iSMvollist ............9, 11, 21 abnormal end of iSMrc_restore command ....63 abnormal end of iSMrc_umount command....62 abnormal suspend ............
  • Page 87 restarting..............55 signature ..............71 restarting master/backup server ........55 software installation ..........4, 6 RO ................73 software uninstallation........... 4, 6, 7 RV ................15 software update............5, 7 RV access restriction ........... 72 sync mode..............72 RW ................73 volume capacities ............