Microsoft Windows NT Microsoft Windows Softek AdvancedCopy Manager Operator's Guide V10.0L30

Transcription

1 Microsoft Windows NT Microsoft Windows 2000 Softek AdvancedCopy Manager Operator's Guide V10.0L30

2 Preface ++ Purpose This manual describes the operations on Softek AdvancedCopy Manager. ++ Intended Readers This manual is intended for a system administrator who performs storage management using Softek AdvancedCopy Manager. ++ Organization This manual has the following chapters: + Chapter 1 Overview of Softek AdvancedCopy Manager This chapter describes the overview of Softek AdvancedCopy Manager. + Chapter 2 Starting and Stopping a Service This section describes starting and stopping a service provided by Softek AdvancedCopy Manager. + Chapter 3 Security Operation Using Authentication Feature This chapter describes the security operation on Softek AdvancedCopy Manager. + Chapter 4 Backup Operation This chapter describes the backup operation. + Chapter 5 Backup Operation in the SP Series This chapter describes the backup operation in the SP series. + Chapter 6 Replication Operation This chapter describes the replication operation. + Chapter 7 Backup and Restore of Exchange Database This chapter describes the procedure when the backup and restore of the Exchange data base are operated. + Chapter 8 Backup and Restore of SQL Server Database This chapter describes the procedure when the backup and restore of the SQL Server data base are operated. + Chapter 9 Operation Maintenance This chapter describes maintaining a database, performing troubleshooting, and other maintenance methods in the operation. + Chapter 10 Commands This chapter describes commands. + Chapter 11 Notes on Operations This chapter describes notes on the operations. + Appendix A Preprocessing and Postprocessing of Backup and Restoration This appendix describes scripts used for preprocessing and postprocessing for backup and restoration. + Appendix B Sample Scripts This appendix describes sample scripts for Softek AdvancedCopy Manager. + Appendix C Replication Scripts This appendix the script which performs processing before and after a replication is described. Related Manuals The following shows the manual system of Softek AdvancedCopy Manager. Softek AdvancedCopy Manager Installation Guide Describes installing Softek AdvancedCopy Manager. Softek AdvancedCopy Manager Operator's Guide (This Manual) Describes operating Softek AdvancedCopy Manager. Softek AdvancedCopy Manager User's Guide i

3 Describes operating the Web-GUI on Softek AdvancedCopy Manager. Softek AdvancedCopy Manager Messages Describes messages output by Softek AdvancedCopy Manager and action required for them. Softek AdvancedCopy Manager Operator's Guide for cluster environment This manual explains the installation, customization, and operation of Softek AdvancedCopy Manager when it is used in a cluster system. You are recommended to read this manual first to have overall understanding before reading other manuals. ++ Conventions Microsoft(R) Windows NT(R) Server network operating system Version 4.0 and Microsoft(R) Windows NT(R) Workstation operating system Version 4.0 are abbreviated as WindowsNT. Microsoft(R) Windows(R) 95 operating system is abbreviated as Windows95. Microsoft(R) Windows(R) 98 operating system is abbreviated as Windows98. Microsoft(R) Windows(R) 2000 Professional, Microsoft(R) Windows(R) 2000 Server, and Microsoft(R) Windows(R) 2000 Advanced Server are abbreviated as Windows2000. Microsoft(R) Windows(R) Millennium Edition is abbreviated as Windows Me. Microsoft(R) Windows(R) XP Professional, and Microsoft(R) Windows(R) XP Home Edition are abbreviated as Windows XP. Manager of Softek AdvancedCopy Manager is abbreviated as Manager of AdvancedCopy Manager. Agent of Softek AdvancedCopy Manager is abbreviated as Agent of AdvancedCopy Manager. ++ Trademarks Windows, WindowsNT, SQL Server, and Internet Explorer are registered trademarks of Microsoft Corporation in the United States and other countries. The Netscape logo and the Netscape product and service names are trademarks or registered trademarks of Netscape Communications Corporation in the United States and other countries. Sun, Sun Microsystems, the Sun Logo, Solaris and all Solaris based marks and logos are trademarks of Sun Microsystems, Inc. in the United States and other countries, and are used under license. UNIX is a registered trademark exclusively licensed by X/Open Company Limited in the United States and other countries. ORACLE is a registered trademark of Oracle Corporation. HP-UX is a registered trademark of Hewlett-Packard Company. Linux is a trademark or registered trademark of Mr. Linus Torvalds in the United States and other countries. ii

4 Chapter 1 Overview of Softek AdvancedCopy Manager This chapter describes the overview of Softek AdvancedCopy Manager. 1.1 What is Softek AdvancedCopy Manager? Softek AdvancedCopy Manager is a product that realizes storage management in an open system and provides the following solutions High-speed backup (24-hour basis) A hardware function [Advanced Copy Function (OPC,EC)] of Fujitsu's disk array units (ETERNUS/GR Series) is used to back up data fast. The advanced copy function, being a fast data copy function independent of a data size, can always maintain fixed backup time even if the data to be backed up increases. Thus, the backup time does not increase even if the data amount increases. This function can drastically reduce the time in which work must be stopped to perform backup. In addition, since operations management is linked to the following DBMS, high-speed backup can be performed without interruption to daily work. Oracle SQL Server 2000 If work uses databases other than the above-mentioned ones or uses a general file system, the time that work is interrupted is still significantly reduced. In addition, to support copy between remote sites, remote copy function between Fujitsu disk array units on a SAN-WAN-SAN connection can be used. Remote copying can also provide a disaster recovery solution because disk arrays containing backup data can be stored in an earthquake-resistant location Non-stopped operating backup database By using Softek AdvancedCopy Manager, the database of Oracle and SQL Server can be backed up by no operating stopping. Please refer to an appendix B sample script about the backup method of the database of Oracle, and refer to cooperation with Chapter 8"Backup and Restore of SQL Server Database" about the backup method of the database of SQL Server High-speed replication The hardware function (advanced copy function [OPC/EC]) of the Fujitsu disk array unit (ETERNUS/GR Series) enables data to be used for purposes other than the original purpose and replicated data (copy) to be collected as a protection against data corruption. If recovery from a disaster is necessary, replication (copying) can be performed for disk array units located at a remote site that has an SAN environment. In addition, since operations management is linked to the following DBMS, high-speed copy of a database can be performed without interruption to daily work. SQL Server Product Configuration of Softek AdvancedCopy Manag er Function system Softek AdvancedCopy Manager consists of the following two functions: [Table 1.1 Functions] Function name Manager of Softek AdvancedCopy Manager Agent of Softek Description Operates on the Storage management server, and two or more Storage servers are managed. Backup management and replication management are performed. Operates on the Storage server with which the storage device is 1

5 AdvancedCopy Manager connected. Backup management and replication management are performed. This product is used combining the manager of Softek AdvancedCopy Manager of the Solaris OE version, the Windows version, or the Linux version. This product, which is included as a component of the SP5000 Basic Package, enables integrated backup in the SP series. For more information on the SP series, see the Storage Management Processor Operator's Manual. The Manager product includes the Agent function. The Softek AdvancedCopy Manager server type depends on the operating environment. Storage server The Storage server is a server which executes the backup business and the replication business that AdvancedCopy Manager offers. The Agent of softek AdvancedCopy Manager is introduced into the Storage server. However, only when the Storage server is one, the Manager of Softek AdvancedCopy Manager is introduced on the system. Storage management server The Storage management server manages the Storage servers and only one Storage management server can be set in the system. The Manager of softek AdvancedCopy Manager is introduced into the Storage management server. Three operating environment forms shown below can be built with the number of the Storage servers which can be used by operating of Softek AdvancedCopy Manager. When only one Storage server is set In this operating environment, only Manager of AdvancedCopy Manager needs to be installed (Manager of AdvancedCopy Manager includes the Agent functions of AdvancedCopy Manager). [Figure 1.1 When only one Storage server is set] When two or more Storage servers are set When two or more AdvancedCopy Manager servers are available, set only one of them up as the Storage management server or set up a new server with no disk drive connected as the Storage management server. Each operation environment is explained below. a. When the Storage server is operated as a Storage management server One of the servers functions as a Storage management server. The Storage management server has a repository where the information on operating and management of all Storage servers is stored. When many Storage servers exist, all of them compete for accesses to the repository. This will affect other applications running on to the same server. Therefore, the Storage management server should be considered as a dedicated server. When a special Storage management server cannot be prepared with the system configuration, becomes an operation form shown in Figure 1.2. (One Storage management server and others become a Storage server.) 2

6 [Figure 1.2 When the Storage server is operated as a Storage management server ] a. Setting up the special Storage management server This setup composes of two or more Storage servers with a dedicated Storage management server. [Figure 1.3 When a special Storage server is a Storage management server ] System configuration The system configuration of Softek AdvancedCopy Manager is shown below. 3

7 [Figure 1.4 System configuration used when the storage management server runs on Windo wsnt/2000] 4

8 [Figure 1.5 System configuration used when the storage management server runs on Solaris OE / Linux] 1.3 Function Overview of Softek AdvancedCopy Manager What is the backup function? The backup function of Softek AdvancedCopy Manager provides operation management for high-speed backup by using the OPC (One Point Copy) function of a Fujitsu disk array unit (ETERNUS3000, GR720, GR730, GR740) and the ROPC (Remote One Point Copy), EC (Equivalent Copy), and REC (Remote Equivalent) functions of a GR740, GR820 and GR840. This function realizes the following backup operation: +High-speed backup operation The advanced copy function (OPC/EC function) of the disk array unit is used to perform high-speed backup between volumes regardless of volume capacities. This function drastically reduces the length of time that work is inevitably interrupted during backup. +Backup operation in the SP series SP series products work closely with GR series disk array units in the management and operation of storage that is independent of the server. With Softek AdvancedCopy Manager, a backup/restore function linked to the backup function of the SP series is provided so that SP series disks can be integrated in the same way that volumes of other GR series disk array. This function is in addition to the management of SP series disks already available in the SP series. +Cooperation with ISV software (sample scripts) Sample scripts with the following functions are provided. These scripts consist of Softek AdvancedCopy Manager 5

9 commands, a DBMS, and backup software commands. Acquisition of DBMS (Oracle) resource information Synchronization with a DBMS (Oracle), copying of volumes, and saving of copy destination volumes to tape (ARCserve) Additionally, the following functions allow you to manage the backup operation. +Policy management function The policy management function manages the number of preservation generations of backup and the number of interval days in which backup should be performed (displays the delay when displaying information) for a volume to be backed up. +Storage configuration management function The storage configuration management function manages the configurations of volumes to be backed up and volumes to which a backup should be saved. On Softek AdvancedCopy Manager, a volume to be backed up is called a transaction volume; a volume to which a backup should be saved is called a backup volume. +Backup and restore functions The backup and restore functions back up and restore a specified volume. The backup function with ROPC/REC is available only for backup disk array units on the same storage server. +History information management function The history information management function manages, out of the information that has been backed up in the past, the information in preservation generations as history. +Consistency recovery function The consistency recovery function resolves inconsistencies in the Softek AdvancedCopy Manager backup management information caused by a system or other type of failure What is the replication function? The replication function of Softek AdvancedCopy Manager provides operation management of replications by using the OPC (One Point Copy) function of a Fujitsu disk array unit (ETERNUS3000, GR720, GR730, GR740) and the ROPC (Remote One Point Copy), EC (Equivalent Copy), and REC (Remote Equivalent) functions of the GR740 GR820 and GR840. As a result, the following replication operations become possible. +High-speed replication operation The advanced copy function (OPC/EC function) of the disk array unit is used to perform high-speed replication between volumes regardless of volume capacities. This function drastically reduces the length of time that work is inevitably interrupted during replication. Since this function, unlike the backup function, does not manage histories, it is suitable for temporary backup. In addition, when the replication function is used with EC, this kind of replication can also be used as an update (incremental) backup operation. +Consistency recovery function The consistency recovery function resolves inconsistencies in the Softek AdvancedCopy Manager replication management information caused by a system or other type of failure Authentication feature function In relation to the backup function provided by Softek AdvancedCopy Manager, this function manages users who have acquired access rights, providing security controls in the identification of function users. For more information, see Chapter 3, "Security Operation Using Authentication Feature". Note also that the replication function is not a target of the authentication feature. 6

10 1.3.4 Web client screen At Softek AdvancedCopy Manager, they are an environmental setup and employment. It is possible to carry out on a Web client screen. The main functions are as follows. Security management Operation restrictions of the user of Softek AdvancedCopy Manager can carry out by GUI operation. Backup management Employment (a definition of a server or a device, backup, restoration, etc. to employ) of backup management of Softek AdvancedCopy Manager can carry out by GUI operation. By the web browser, a Web client screen can be used by accessing a management server. (It can be operated from the terminal with which AdvancedCopy Manager is not installed) Not only a Web client screen but the operation by the command is possible for employment of backup management. For more information, see " Chapter 1 Softek AdvancedCopy Manager Web Client" in "Solaris OE, Windows or Linux version Softek AdvancedCopy Manager User's Guide". 1.4 Operating Environment of Softek AdvancedCopy Mana ger Hardware requirements One of the following hardware devices is required to perform backup management or replication management. In addition, an advanced copy license and copy table size need to be set up. ETERNUS3000 disk array unit GR720 disk array unit GR730 disk array unit GR740 disk array unit GR820 disk array unit GR840 disk array unit Software requirements Manager of Softek AdvancedCopy Manager The following table lists the software requirements for Manager of Softek AdvancedCopy Manager [Table 1.2 Software requirements for Manager of Softek AdvancedCopy Manager] Product name Requirement Remarks Microsoft(R) WindowsNT(R) Server V4.0 SP5 to SP6a Microsoft(R) WindowsNT(R) Server V4.0 Enterprise Edition SP5 to SP6a Microsoft(R) Windows(R) 2000 Server SP1-3 Microsoft(R) Windows(R) 2000 Advanced Server SP1-3 Microsoft(R) Internet Information Server 3.0 Microsoft(R) Internet Information Server 4.0 Microsoft(R) Internet Information Services 5.0 Microsoft(R) Windows Scripting Host Multipath Control for WindowsNT/2000 V2.0L12 GR multipath driver Required Conditionally required Conditionally required Conditionally required Conditionally Support OS When a Web client is used If a storage management server serves also as a storage server (*1) When a Storage management server serves as a Storage server, and when multipass disk control is carried out When a Storage management server serves as a Storage server, and when it carries out multipass 7

11 (GRMPD)1.0 for Windows required disk control and load distribution of a path is carried out further Microsoft(R) SQL Server(TM) 2000 SP2 or later Microsoft(R) Exchange 2000 Server SP3 Microsoft(R) Exchange 2000 Server system management tool SP3 MSCS V1.0 Oracle 7.x, 8.x, 8i, 9i Conditionally required Conditionally required Conditionally required Conditionally required Conditionally required If a storage management server serves also as a storage server and backup employment of the database of SQL Server is carried out If a storage management server serves also as a storage server and backup employment of the Exchange database is carried out When a Storage management server serves as a Storage server, and when using it as a backup server in backup employment of the Exchange database by the replication management function When MSCS operation is performed with Manager of Softek AdvancedCopy Manager In linkage with Oracle (*1) This software can be downloaded from the following URL: Agent of Softek AdvancedCopy Manager [Table 1.3 Software requirements for Agent of Softek AdvancedCopy Manager] Product name Requirement Remarks Microsoft(R) WindowsNT(R) Server V4.0 SP5 to SP6a Microsoft(R) WindowsNT(R) Server V4.0 Enterprise Edition SP5 to SP6a Microsoft(R) Windows(R) 2000 Server SP1-3 Microsoft(R) Windows(R) 2000 Advanced Server SP1-3 Solaris OE version Manager of Softek AdvancedCopy Manager 10.2 or Windows version Manager of Softek AdvancedCopy Manager V10.0L30 or Linux version Manager of Softek AdvancedCopy Manager V10.0L30 Microsoft(R) Windows Scripting Host Multipath Control for WindowsNT/2000 V2.0L12 GR multipath driver (GRMPD) 1.0 for Windows Microsoft(R) SQL Server(TM) 2000 SP2 or later Microsoft(R) Exchange 2000 Server SP3 Microsoft(R) Exchange 2000 Server system management tool SP3 Required Required Support OS The manager product of Softek AdvancedCopy Manager Required Script execution software (*1) Conditionally required Conditionally required Conditionally required Conditionally required Conditionally required If the multipath disk control is performed For multipath disk control and path load balancing When backup employment of the database of SQL Server is carried out When backup employment of the Exchange database is carried out When using it as a backup server in backup employment of the Exchange database by the replication management function MSCS V1.0 Conditionally When MSCS operation is performed with 8

12 Oracle 7.x, 8.x, 8i, 9i required Conditionally required Agent of Softek AdvancedCopy Manager In linkage with Oracle (*1) This software can be downloaded from the following URL: Web Browser In order to use the Web client of AdvancedCopy Manager, Windows NT, Windows 2000, and a Windows 95/98-/ME/XP system are needed. (It does not operate in Solaris OE, Linux, and HP-UX.) Moreover, following Web Browser and Plugin are needed. In addition, it is not required when not using a Web client. [Table 1.4 Software requirements for Web browsers] Product name Requirement Remarks Microsoft(R) Internet Explorer 4.0 or later Netscape Communicator 4.04 or later Required Web Browser Java Plugin 1.3.1_02 or later Required Java Plugin 1.5 Managing a Device on Softek AdvancedCopy Manager Softek AdvancedCopy Manager manages a device (physical disk) in a disk array unit. Each device is managed using a unique identifier for the device (AdvancedCopy Manager device name). A AdvancedCopy Manager device name must be in the following format: [Table 1.5 AdvancedCopy Manager device name] Device name g?d?p? or Disk class name/mirror volume name: g?d?p? Description The characters "g," "d," and "p" indicate the following. [GR device] The character "g" indicates a GR device number, "d" indicates an OLU number, and "p" indicates a partition number. [Non-GR device] The character "g" indicates a fixed value of 0, "d" indicates a serial number used on the server, and "p" indicates a partition number. For the SDX object Disk class name: Disk class name of SDX object * About the device name of a non-g device (g?d?p?) The character "g" is always 0 for non-gr devices. Mirror volume name: Mirror volume name of SDX object The character "d" indicates a AdvancedCopy Manager specific number that is unique on the server to which devices are connected. This number is different from that used by Disk Administrator. The character "p" indicates a partition number. * Devices not to be processed The following devices are not to be processed by any part of AdvancedCopy Manager. FT disk (Windows) Dynamic volume (Windows 2000) Device with more than one mount point (mounted at two or more locations) Use the AdvancedCopy Manager device name in the backup operation on Softek AdvancedCopy Manager. A AdvancedCopy Manager device name corresponds to a management name (partition/logical drive) on Disk Administrator on a one-on-one basis but does not match a management number on Disk Administrator. Thus, Softek AdvancedCopy Manager displays a "block device name" on the window to facilitate the correspondence between a AdvancedCopy Manager device name and a Disk Administrator indication. 9

13 A "block device name" is in the following format: disk?p? disk?: A disk physical number, i.e., a disk number displayed on Disk Administrator p?: The same value as p? in a AdvancedCopy Manager device name You can see the relationship between a "AdvancedCopy Manager device name" and a "block device name" in the device list window. For more information on the device list window, see Chapter 1.2.3, "Device list window" in the "Softek AdvancedCopy Manager User's Guide". Please refer to " Device information display command (stgxfwcmdispdev)" of this manual about the details of a device information display command. +Target file system The following shows the device file systems that can be registered in jobs. FAT(File allocation System) FAT32 NTFS(NT File System) 10

14 Chapter 2 Starting and Stopping a Service This chapter describes starting and stopping a service provided by Softek AdvancedCopy Manager. 2.1 Services of Softek AdvancedCopy Manager Manager of Softek AdvancedCopy Manager consists of the following services: [Table 2.1 Services of Manager of Softek AdvancedCopy Manager] Displayed service name AdvancedCopy Manager GUI Service AdvancedCopy Manager ACL Service AdvancedCopy Manager COM Service SymfoWARE RDA RDBSWSTF SymfoWARE RDB RDBSWSTF Description A service that manages GUI windows A service that manages the authentication feature A service that communicates with a storage server A service that performs repository access A service that performs repository access Agent of Softek AdvancedCopy Manager consists of the following service: [Table 2.2 Services of Agent of Softek AdvancedCopy Manager] Displayed service name AdvancedCopy Manager COM Service Description A service that communicates with a storage management server 2.2 Starting a Service Normally, you need not manually start services of Softek AdvancedCopy Manager because they are automatically started when the system is started. However, you need to manually start a service of Softek AdvancedCopy Manager if: The startup of the service has failed due to some cause. The service has been intentionally stopped. Manually start a service as follows: For Windows NT 1. Click [Control Panel]->[Services] to display the service window. 2. A list of services registered in the system will be displayed. Select a service to be started and click the [Start] button. For Windows Click [Control Panel]->[Administrative Tools]->[Services] to display the service window. 2. A list of services registered in the system will be displayed. Select a service to be started and click the [Start] button About starting the service on the cluster operation, see Chapter 6, "Starting and Stopping a Service," in the Softek AdvancedCopy Manager Operator's Guide for cluster environment. 2.3 Stopping a Service Services of Softek AdvancedCopy Manager are automatically stopped when the system is stopped. If you need to stop an individual service for some reason, manually stop the service as follows: For Windows NT 1. Click [Control Panel]->[Services] to display the service window. 2. Select a service to be stopped and click the [Stop] button. For Windows Click [Control Panel]->[Administrative Tools]->[Services] to display the service window. 2. Select a service to be stopped and click the [Stop] button. 11

15 About starting the service on the cluster operation, see Chapter 6, "Starting and Stopping a Service," in the Softek AdvancedCopy Manager Operator's Guide for cluster environment. 12

16 Chapter 3 Security Operation Using Authentication Feature This chapter describes the security operation using the authentication feature provided by Softek AdvancedCopy Manager. 3.1 Overview Softek AdvancedCopy Manager provides features for backup management, and replication management or operation. If any of the features is incorrectly used, the operation may stop. Thus, Softek AdvancedCopy Manager provides a function of setting access permissions for each user on the backup operation (authentication feature). Use this function to realize security of the backup operation. On Softek AdvancedCopy Manager, you can use only a user who: Has a user name consisting of up to 20 alphanumeric characters Has a password consisting of up to 14 alphanumeric characters The following precautions exist for the operation on Windows(R) Setup of NetBIOS over TCP/IP When you use the backup function on Windows(R) 2000, do not disable NetBIOS over TCP/IP in the detailed settings of TCP/IP. This setting has been enabled upon installation of Windows(R) If you disable this setting by mistake, enable it as follows: 1. Access Control panel, then [Network and Dial-up Connections] and open the property of [Local Area Connection]. 2. Select the [Advanced...] button of [Internet Protocol(TCP/IP) Properties] to open the [Advanced TCP/IP Settings] window. 3. Open the WINS tag and check "Enable NetBIOS over TCP/IP". Access control using a user principal name The user authentication and the access control using a user principal name that has been introduced on Windows(R) 2000 is not supported. A user principal name is a user representation that can be used if Active Directory is installed on Windows(R) A user principal name is expressed as "user-name@dns-name". Password length on Windows2000 Although a password consisting of up to 127 alphanumeric characters can be specified on Windows2000, only a password consisting of up to 14 alphanumeric characters are valid on Softek AdvancedCopy Manager. 3.2 Access Permission Table 3.1 shows access permissions that can be specified on Softek AdvancedCopy Manager. [Table 3.1 Access permissions on Softek AdvancedCopy Manager] Access permission Write permission Execute permission Read permission Description Allows you to change the operation information (such as policy information) and perform a series of storage operations. A write permission includes execute and read permissions. Only a write permission can be set for a user belonging to the Administrators group. Allows you to perform a series of storage operations and read information. An execute permission includes a read permission. Allows you only to read information. Table 3.2 shows the operations on the initial window, made available due to each of the access permissions. [Table 3.2 Operations on the initial window made available due to access permissions] Operation name Write permission Execute permission Read permission 13

17 Displaying server information Yes Yes Yes Displaying device information Yes Yes Yes Displaying partition information Yes Yes Yes Changing in Displayed Item of Device Yes Yes Yes Updates to Latest Information Yes Yes Yes Addition of server Yes No No Change of server Yes No No Deletion of server Yes No No Acquisition and reflection of information on all the devices Acquisition and reflection of information on specific device Yes No No Yes No No Deleting device information Yes No No Yes: Enabled; No: Disabled The access permission of the initial window follows the access permission of the backup management function. Table 3.3 shows the backup management operations made available due to each of the access permissions. [Table 3.3 Backup management operations made available due to access permissions] Operation name Write permission Execute permission Read permission Window display Yes Yes Yes Backup Yes Yes No Restoration Yes Yes No Recovery Yes Yes No Delete History Yes Yes No Start Backup Synchronization processing Cancel Backup synchronization processing Yes Yes No Yes Yes No Match Resources Yes Yes No Set Backup Policy Yes No No Delete Backup Policy Yes No No Set Device Information Yes No No Set Storage Server Configuration Information Yes No No Yes: Enabled; No: Disabled 3.3 Setup Procedure This section describes how to perform the security operation on Softek AdvancedCopy Manager Flow of setup The following shows the flow of setup procedure. 14

18 3.3.2 Setup work details The following shows the operation work details. For description, operation methods, and notes on each window, see Chapter 2, "Operating the Authentication Feature Window" in the "Softek AdvancedCopy Manager User's Guide". 1. Specify the URL of the initial window of Softek AdvancedCopy Manager to display the initial window. 2. The following login window will be displayed. Specify the user name and the password of a privileged user (a startup account specified when Manager of Softek AdvancedCopy Manager was installed) and click the [OK] button. 3. The initial window of Softek AdvancedCopy Manager will be displayed. 4. Select [Edit] from the initial window authentication feature menu. The following setup window will be displayed. 15

19 5. From the operation menu, select [Add user]. The following window will be displayed. From the User list, select a user to be added to move it to the User list to be added. From the combo box, select an access permission and click the [OK] button. You can add either a specific user or multiple users. After you have set the access permission, click the [OK] button. The addition of a user and the setup of an access permission for this user will be completed. The displayed user names are local user names registered on the storage management server. If the storage management server is the primary domain controller or the backup domain controller, a "domain user name" will be displayed. A user to be added must have permission to local logon to the system. If a user without local logon permission is added, the authentication of this user will encounter an error. A user belonging to the Administrators group is dimmed. Only a "write permission" can be granted to the user. Likewise, only "write permission" can be granted to multiple users if they include a user belonging to the Administrators group. A user name already registered on one of the management systems will not be displayed in the user name list dialog. If no user to be added exists, the following warning dialog will be output and you will be sent back to the authentication feature management window. 16

20 17

21 18

22 Chapter 4 Backup Operation This chapter describes the backup operation for Softek AdvancedCopy Manager on the Windows NT/2000 system. Softek AdvancedCopy Manager backups are created in units of partitions. Throughout this manual, a volume is expressed as a "device". 4.1 Overview This chapter describes the backup and restore functions of Softek AdvancedCopy Manager. Softek AdvancedCopy Manager performs high-speed backup between volumes, regardless of the volume capacities, using the advanced copy function (OPC or EC function) of a disk array unit. Backup that uses the One Point Copy (OPC) or Remote One Point Copy (ROPC) function of a GR series disk array unit is called snapshot fast backup. Backup that uses the Equivalent Copy (EC) or Remote Equivalent Copy (REC) function is called synchronized high-speed backup. Automatic snap shot backup can be scheduled without first estimating the time required because it does not require backup synchronous processing. Note, however, that when the save number is 1, a state in which there is no backup data may occur, because a snap shot backup deletes the history prior to copy processing. Because synchronized high-speed backup deletes the history after the completion of backup processing, there is no status in which backup data does not exist even though the generation number is 1. However, synchronized high-speed backup requires one more backup volume than snapshot fast backup. Synchronized high-speed backup also requires synchronized backup processing before the backup execution command is entered. Therefore, execution of automatic synchronized high-speed backup must be scheduled so that the time required for synchronized processing is estimated in advance. Synchronized backup processing is then started based on the estimated time, and the backup execution command is entered after equivalency maintains status has been achieved. When backing up an Oracle database, it is combining with the sample script which Softek AdvancedCopy Manager's offers, and on-line backup can be performed. Even for online processing, databases such as Oracle and SQL Server can be backed up in combination with the sample script provided by Softek AdvancedCopy Manager. If other files (general files, etc.) are to be backed up, the transaction must be temporarily stopped before and after backup. Softek AdvancedCopy Manager automatically manages and selects a medium to be used for backup (a backup volume). Softek AdvancedCopy Manager also manages the backup carriers and generations and allows you to restore data from the latest or other past generations. [Figure 4.1 Managing a backup volume] 19

23 The One Point Copy (OPC) function can be used for the Fujitsu ETERNUS3000,GR720, GR730, and GR740 disk array units. The Remote One Point Copy (ROPC), Equivalent Copy (EC), and Remote Equivalent Copy (REC) function can be used only for the GR Snapshot backup processing The OPC (One Point Copy)/ ROPC (Remote One Point Copy) function of the disk array unit GR series is used to copy data from a transaction volume to an unused backup volume. The snapshot fast backup performs processing as follows: 1. On the transaction volume list view, select [Backup] from the Operation menu ((1) in Figure 4.2). The following processing will be performed: - If backup volumes under generation management exist for all the generations, the oldest backup volume will be assumed as an unused backup volume. - An unused backup volume will be acquired from the unused backup volume management area. 2. Data on the transaction volume will be copied to the acquired unused backup volume ((2) to (4) in Figure 4.2). 3. Backup carrier information will be set. [Figure 4.2 Snapshot fast backup processing] The snapshot fast backup is completed as soon as you specify to execute backup. The actual data copying will be internally performed by the OPC function of the disk array unit GR series. If all generations of backup volumes are managed, and if no backup volume can be obtained from the unused region in the backup volume management area, backup copies cannot be created. The backup function which used ROPC is restricted to the disk array equipment in the same Storage server. 20

24 4.1.2 Synchronized high-speed backup processing The Equivalent Copy (EC) or Remote Equivalent Copy (REC) function of the GR series of disk array units is used to copy data from a transaction volume to an unused backup volume. Synchronized high-speed backup performs processing as follows: 1. On the transaction volume list view, select [Start Synchronized Backup Processing] from the Operation menu ((1) in Figure 4.3). An unused backup volume having the same capacity as the transaction volume is selected from the unused backup management area, and the synchronized backup processing starts. 2. The transaction and backup volumes are both placed in equivalence status. From this point on, equivalence between the transaction volume and backup volume is maintained. This status is referred to as equivalency maintain status ((3) in Figure 4.3). 3. On the transaction volume list view, select [Stop Synchronized Backup Processing] from the Operation menu ((4) in Figure 4.3). The backup synchronization processing stops and the backup history information is set. 4. If the backup data exceeds the number of generations when backup has been completed, the oldest backup volume is treated as an unused backup volume. The backup execution command cannot be executed before the transaction and backup volumes have become equivalent. [Figure 4.3 Backup using the synchronized high-speed backup function] If all generations of backup volumes are managed, and if no backup volume can be obtained from the unused region in the backup volume management area, backup copies cannot be created. 21

25 The backup function which used REC is restricted to the disk array equipment in the same Storage server Restoration processing This chapter describes restoring data on Softek AdvancedCopy Manager. The restoration operation refers to restoring data from a backup volume managed by the backup carrier information to a transaction volume. The restoration operation from a backup volume refers to using the OPC function provided by the disk array unit to restore data from a backup volume to a transaction volume. If the data on a backup volume under carrier management is restored to a transaction volume, the carrier management information will not change. Note that data will be restored to a transaction volume that is the backup source. However, you can change the restoration destination. It is not guaranteed about the newest backup volume extraction time and the data rewritten though the contents of operating volume were rewritten by the time it performed restoration operation. [Figure 4.4 Notes on restore operations in Softek AdvancedCopy Manager] Device name The backup operation on Softek AdvancedCopy Manager is aimed at a device (partition) in a disk array unit. This device is managed by a unique name determined by Softek AdvancedCopy Manager. It is called a "AdvancedCopy Manager device name". For information on a AdvancedCopy Manager device name, see Chapter 1.5, "Managing a Device on Softek AdvancedCopy Manager". 4.2 Operation Design This chapter describes the backup operation on Softek AdvancedCopy Manager. Design a backup operation as follows: 22 Deciding a server on which the backup operation should be performed Deciding a backup target Deciding a backup policy Preparing a backup volume Preparing the automatic backup operation

26 4.2.1 Deciding a server on which the backup operation should be performed The backup operation can be performed on one of the following servers. Storage management server Multiple storage servers are unified and operated centrally. The storage management server can also be used as a storage server. Storage server Softek AdvancedCopy Manager operations are performed. Backup server employment cannot be performed using a backup management function. When you perform backup server employment, please use a replication management function. [Figure 4.5 Configuration of servers on which the backup operation should be performed] Deciding a backup target Softek AdvancedCopy Manager backs up data in units of devices. A device that stores work data is called a transaction volume. A transaction volume to be backed up must be placed on the disk array unit GR series. For information on setting up a transaction volume, see Chapter 4.4.8, "Setting the operation type for a device". In order to set up volume as operating volume, there are some points which should be taken into consideration. For details, please refer to " General notes." 23

27 Please make applicable to backup neither the disk with which the system is stored, nor the disk with which Softek AdvancedCopy Manager is installed Deciding a backup policy To setup a backup policy on a transaction volume, set the following items: +Number of preservation generations The number of preservation generations refers to how many generations of backup data should be kept. The snapshot fast backup first releases the oldest generation from the generation management. If a system failure or any other failure occurs while the backup is running, there may not be as many generations of backup data as required. In such a case, you are recommended to perform backup immediately again. By snapshot type high-speed backup, when employing the number of preservation generations as 1, we recommend you to use together the employment which evacuates backup data to a tape etc. A synchronous high-speed backup operation releases the oldest generation from generation management after backup of the latest generation is completed. Thus, backup volumes for (number of backup generations + 1) are necessary. +Interval days The interval days refers to an interval at which backup should be performed. The delay of backup is displayed if more days than the specified number of interval days have passed after the last backup date. Note that backup is not performed periodically even if you have specified the interval days. For information on setting a backup policy, see Chapter , "Setting a backup policy" Preparing a backup volume Prepare the backup volume. The backup unit of Softek AdvancedCopy Manager is a device. In Softek AdvancedCopy Manager, the device in which the transaction data used as the candidate for backup is stored is called transaction volume. A backup volume must be placed on the disk array unit GR series. A backup volume must have the same size as a transaction volume. For more information, see "Size of a logical disk". The number of backup volumes is determined by whether snapshot fast backup or synchronized high-speed backup is performed: Backup For snapshot fast backup Number of required backup volumes Number of backup generations For synchronized high-speed backup Number of backup generations + 1 When backup policies have already been set for multiple transaction volumes, the registration of a backup policy for a newly registered transaction volume requires that the following number of backup volumes be registered beforehand: Backup For snapshot fast backup For synchronized high-speed backup Number of required backup volumes Total number of backup generations in the registered backup policies + number of generations in the new backup policy being set Total number of backup generations in the registered backup policies + number of registered transaction volumes + number of generations in the new backup policy being set + 1 For backup volumes, do not select disks in which a system is stored or Softek AdvancedCopy Manager is installed. 24

28 For information on setting a backup volume, see Chapter 4.4.8, "Setting the operation type for a device" Preparing the automatic backup operation The backup operation of Softek AdvancedCopy Manager can be automated using SystemWalker/OperationMGR, etc. +Automatic snapshot fast backup Automatic snapshot fast backup can be executed in one of the following two ways. Start the backup command in a job net of a batch job every time when a backup should be collected. Start the backup command at the specified time. +Automatic synchronized high-speed backup For synchronized high-speed backup, the transaction and backup volumes must be in equivalency maintain status at the scheduled time for backup. For this reason, if synchronized high-speed backup is automated, the synchronized backup processing start command and the backup execution command must be started separately, as described below. +Starting the synchronized backup processing start command At first, theoretically calculate the time required for the synchronized backup processing. Execute the synchronized backup processing start command by specifying the time obtained by subtracting that theoretical time or more from the time that the backup execution command is to start. The transaction and backup volumes will then be in equivalency maintain status when backup is executed. The time between the start of synchronized backup processing and the transition to equivalency maintain status depends on the capacity of the volume to be copied. +Starting the backup execution command Use either of the following methods to automatically execute the backup execution command: Start the backup execution command in a job net of a batch job at the same time at which the backup data is to be collected. 25

29 If there are other jobs (jobs A and B in the figure) to be executed before the backup execution command in the job net, the start time of the backup execution command cannot be determined. Assume that the start time of the backup execution command is the time obtained by adding the shortest time required for jobs A and B to the job net start time. Determine the start time of the synchronized backup processing start command by subtracting the estimated time from the start time of the backup execution command. Start the backup execution command with the time specified. 4.3 Flow of Operation The following shows the flow of backup operation on a regular transaction volume. 26

30 4.4 Preparations The following preparations are required before the backup operation is started. 27

31 4.4.1 Starting a service Before the backup operation is started, the services of Softek AdvancedCopy Manager must be started on the storage management server and the Storage servers. Normally, these services are automatically started up when the system is started. If the startup of a service fails for some reason or if a service has been stopped, you need to start the service on each server. For information on starting a service, see Chapter 2, "Starting and Stopping a Service" Setting an access permission When performing backup employment from a backup management screen, an access permission of each operation of a backup management screen is set up. For details of the Setting Method, see Chapter 3, "Security Operation Using Authentication Feature". When only a command performs backup employment, a setup of access permission is not required Starting the initial window Specify the following URL to start the initial window of Softek AdvancedCopy Manager. The following GUI (server list view) will be started. When applying only by the command, without using GUI, it is not necessary to perform this operation Registering a storage server The Storage management server registers the Storage server to be managed. When the Storage server is operated as a Storage management server does not need to add a server. Select the [Operation] menu, select [Addition of Server]. The following window will be displayed. 28

32 For the Storage server to be added, specify a server name, IP address, and port number required for communications. The port number is specified as the "communications service port number", when Agent of Softek AdvancedCopy Manager was installed. In cluster operation, specify the logical IP address of the Storage server as IP address. And specify the port number registered at the time of the cluster setup of Storage server transaction. The [OK] button is pushed after inputting the above item, and additional processing of a Storage server is carried out. In addition, this processing can be carried out also by the server information addition command (stgxfwcmaddsrv) Fetching device information on a storage server As part of replication management, device information on a storage server must first be stored in the repository. To acquire information on a device on the storage manager server, the [Operation] menu, select [Acquisition and reflection of Information on all devices]. The following window will be displayed. Check the server from which device information should be acquired and then press the OK button. After device information is acquired from each server, the following dialog will be displayed. 29

33 The new devices detected will be displayed in the uppermost list box. Move a device to be managed to the list box on the left. The second list box displays devices currently under management but not detected. Move a device that you no longer want to manage to the list box on the right. The lowermost list box displays devices whose device information has been updated (e.g., the mount point name has been changed). All the device names displayed in this dialog box are "AdvancedCopy Manager device names". The OK button is pushed after carrying out the above operation, and acquisition processing of device information is carried out. In addition, this processing can be carried out also by the device information collection/reflection command (stgxfwcmsetdev). It takes the time proportional to the total of the device defined in the selected Storage server for this operation. Please execute CPU load and the I/O load low when there are a lot of numbers of devices. It takes about 0.5 seconds a device (partition) as a standard with there no load, and refer, please. When backup synchronous processing or synchronous replication processing is being performed, device information may be unable to be acquired correctly. Therefore, when you take in device information, where all synchronous processing are canceled, please carry out Displaying the backup management window On the server list view, select the [File] menu and then [Backup Management]. The server list view for the backup management will be displayed. 30

34 4.4.7 Setting the environment for a backup operation server Set the environment for each storage server. From the Backup Management window, select backup management in the tree view displayed on the left side. Then, select the storage server in a list view displayed on the right side of the window. Finally, select [Set Storage Server Configuration Information] from the [Operation] menu. The following setup window will be displayed. If the target Storage server is Solaris OE and the SymfoWARE database exists in the Storage server, a recovery control file output place directory and a work directory are inputted. When a SymfoWARE database does not exist in a Storage server, or when a Storage server is WindowsNT/2000, HP-UX or Linux, this input item cannot serve as a half-tone display, and cannot be inputted. After completing the input of necessary items, click the [OK] button. You need to make this environment setting also on the storage management server if it serves also as a storage server. This step is not required if the environment setting has already been made on the storage servers. You can also make this environment setting also using the storage server configuration information setting command Setting the operation type for a device Set up the following device operation type, before backing up in a storage server. The operation type is as follows: Define the volume to be backed up as a transaction volume. Prepare backup volumes. Prepare as many volumes, each of which has the same size as the transaction volume, as the number required for the backup type, and define them as the backup volumes: Backup Number of required backup volumes 31

35 Snapshot fast backup Number of backup generations Synchronized high-speed backup Number of backup generations + 1 Set an operation type on the server list view. On the server list view, select a storage server and select the [Operation] menu and then [Set Device Information]. The following setup window will be displayed. A volume displayed in "Other volume" field has no specified device operation type. Set a device operation type as follows: Setting as a "transaction volume" After selecting a target volume, click the [<] button on the "Transaction volume" side. The target volume will be moved to the "Transaction volume" field. Setting as a "backup volume" After selecting a target volume, click the [<] button on the "Backup volume" side. The target volume will be moved to the "Backup volume" field. After making settings for all the volumes, click the [OK] button. You can make this setting also using the device information setting command (swstdevinfoset). In order to set up volume as operating volume, there are some points which should be taken into consideration. For details, see " General notes" When changing the size of physical disk registered as a transaction volume, or the construction of a volume group, delete the volume from the registered transaction volumes. Next, after following the process of Fetching device information on a Storage server again, re-register the volume by executing the device information setting command. When changing the size of physical disk registered as a backup volume, or the construction of a volume group, delete the volume from the registered backup volumes. Then, after following the process of Fetching device information on a 32

36 Storage server again, re-register the volume by executing the device information setting command. Backup volume needs to be the same size as operating volume. Please make applicable to backup neither the disk with which the system is stored, nor the disk with which Softek AdvancedCopy Manager is installed. You can check what has been registered as follows: Checking on a GUI window You can view information on a transaction volume on the transaction volume list view or information on a backup volume on the backup volume list view. For more information on each of these views, see "Windows, Solaris OE or Linux Softek AdvancedCopy Manager User's Guide". Checking using a command You can view information on a registered transaction volume or backup volume using the device usage status display command Setting options Set options when performing backup to a backup volume in a cabinet that is not the same as the cabinet containing the transaction volume. Create the following files to set options: For normal operation (non-cluster) <environment-setting-directory> etc backup data DEFAULT check.ini For cluster operation <logical-node-environment-setting-directory> etc backup data DEFAULT check.ini Code as follows: [check] RemoteCopy=Yes If the option settings file is changed after operation starts, backup may not be able to continue. For this reason, do not change the option settings file after the start of operation. To change the option settings file, you must set the backup policy again Setting backup policies For a transaction volume registered on a storage server, set the following backup policy: Number of preservation generations Means how many generations of backup data should be kept. Interval days Means the number of days before next backup should be performed. If the specified number of days is exceeded, you will be prompted to perform backup on the GUI window of Softek AdvancedCopy Manager. To set a backup policy on the server list view, you display storage servers in a tree view on the server list view. The list of transaction volumes and backup volumes on this storage server will be displayed. After selecting a transaction volume for which you want to set a backup policy, click the right mouse button. From the popup menu, select [Set Backup Policy]. The following setup window will be displayed. 33

37 On this window, specify the number of interval days and the number of preservation generations and click the [OK] button. Perform this procedure on all the transaction volumes. You can set a backup policy also using the backup policy setting command (swstbkpolset). Even if the number of interval days has been specified, Softek AdvancedCopy Manager does not automatically collect backup. This value is used only to prompt the user to perform backup when the number of backup interval days is exceeded. When you set a backup policy, there must be as many registered backup volumes as required to perform backup according to the specified backup policy. For information on the necessary number of backup volumes, see Chapter 4.2.4, "Preparing a backup volume". Even though the number of backup volumes required for the backup may not have been registered beforehand when backup policies for synchronized high-speed backup were set, the number required can be set if the number of backup volumes that are required for snapshot fast backup have been registered. However, synchronized high-speed backup may not be able to be executed. You can check what has been defined as follows: Checking on a GUI window You can view information on a backup policy on the transaction volume list view. For more information on the window, see the "Softek AdvancedCopy Manager User's Guide". Checking using a command You can view information on a defined backup policy using the backup policy display command (swstbkpoldisp) Customizing preprocessing and postprocessing scripts If the case of the operation explained below, the backup preprocessing and postprocessing scripts need to be customized: When you want to add special preprocessing and postprocessing to the preprocessing and postprocessing scripts When Z drive is not an empty drive When two or more backup execution commands or restoration execution commands are executed simultaneously Refer to Appendix A "Backup and Restoration Preprocessing and Postprocessing," for information on the customization Preparing a device map file In the backup operation on Softek AdvancedCopy Manager, a backup volume with the same capacity as a transaction volume is automatically selected from the registered backup volumes. If the backup volume is recognized in a "Device map file", i.e., a file defining the correspondence between transaction and backup volumes, it must be created. Create a device map file anywhere on the storage server that performs backup. If you specify this file while performing backup, an operation in recognition of the backup destination is enabled. 34

38 Describing a device map file The following shows a description example of a device map file. The following lists rules for creating a device map file. Describe a transaction volume and a corresponding target backup volume in one line. Separate a transaction volume and a backup volume with one or more "half-size blank or tab characters". One or more "half-size blank or tab characters" may be included between the beginning of a line and a transaction volume name or between the end of a backup volume name and the end of a line (new line character). A blank line ("half-size blank or tab characters") may be included in a file. The portion from the symbol "#" to the end of a line is assumed as a comment. You cannot specify more than one target backup volumes for one work disk in one device map file. In such a case, the information in the line first found will be valid. While a device map file is read, the system will not detect such a redundant line. A device map file may include descriptions of transaction volumes other than the processing target (Device-Name or Log-Group-Name). (See the description example provided in the beginning of this chapter.) 4.5 Operation This chapter describes the backup operation on Softek AdvancedCopy Manager. Before performing the backup operation, make environment settings required for the backup operation according to Chapter 4.4, "Preparations". There are the following two kinds of employment of backup of Softek AdvancedCopy Manager. Snapshot type high-speed backup employment synchronous high-speed backup employment Performing the snapshot fast backup Perform the snapshot fast backup as follows: 1. Before backing up a general file system, stop work. 2. Display the transaction volume list view and select a volume to be backed up. 35

39 3. From the Operation menu, select [Backup] to display the following window. 4. Check the displayed server names and transaction volume names and perform the following: - To use a volume automatically selected by Softek AdvancedCopy Manager a backup volume: Click the [OK] button. - To use a specific volume as a backup volume: Specify a device map file created on the storage server that performs backup (e.g., C: stgmgr devmap1) and then click the [OK] button. 5. After the backup is completed, the following window will be displayed. Click the [OK] button and you will be sent back to the transaction volume list view. 36

40 6. This completes backup. Now you can restart work. At this point, however, the physical copying of a volume is not completed at the back end. To check the status of physical copying, do as follows: 7. Display the transaction volume list view and check the [Status] field of a target transaction volume. You can check the current copying status because this field displays the progress status of copying processing. 8. To check the latest copying status, either: - Click the [PF5] key, or - Select [Refresh] from the View menu. 9. If you have stopped work in Step 1, restart the work. You can perform backup also using the backup execution command. You can check the backup status also using the backup execution status display command Performing the synchronized high-speed backup Perform the synchronized high-speed backup for a transaction volume as follows: 1. Display the transaction volume list view and select a volume to be backed up. 37

41 2. On the Operation menu, select [Start Synchronization processing] to display the following window. 3. Check the displayed server name and transaction volume name, and perform one of the following operations: - To use a volume automatically selected by Softek AdvancedCopy Manager as a backup volume: Click the [OK] button. - To use a specific volume as a backup volume: Specify a device map file name created on the storage server (e.g., C: stgmgr devmap1) for which backup will be performed and then click the [OK] button. 4. When the synchronized backup processing is completed, the window shown below appears. Click the [OK] button to return to the transaction volume list view. 38

42 5. Physical copying from the transaction volume to backup volume now starts. To check the status of the physical copying, do the following: 6. Display the transaction volume list view and check the [Status] field of the target transaction volume. This field displays the progress of the coping processing. Use it to check the current status of the copying. 7. To check the latest copying status, perform one of the following operations: - Click the [PF5] key. - Select [Refresh] from the View menu. 8. The transaction and backup volumes enter equivalency maintain status when the [Status] field indicates [Backup Preparation Completed]. 9. To create a backup history, select the target transaction volume from the transaction volume list view and select [Backup] from the Operation menu. The following window appears. 10. Check the displayed server name and transaction volume name, and click the [OK] button. 11. When the backup is completed, the window shown below appears. Click the [OK] button to return to the transaction volume list view. The backup execution command causes an error if it is executed before the transaction and backup volumes 39

43 have entered equivalence status. The device map cannot be specified during backup. Backup synchronous processing is started with Backup synchronous processing start command. A backup synchronous processing state is checked with Backup synchronous processing progress display command. Backup can also be executed with the backup execution command. The backup status can also be checked with the backup execution status display command Performing restoration This chapter describes restoring a volume or data that has been backed up Restoring an entire volume Restore all the data in a volume, which has been backed up in the snapshot fast backup as follows: 1. Stop work if you want to perform restoration on a general file system. 2. Display the transaction volume list view. Select a volume to be restored. 3. From the Operation menu, select [Restore] to display the following window. As the restore source volume, the latest backup destination volume for the concerned transaction volume will be selected. 4. Check the name of volume to restore. As the name of volume to restore, a transaction volume name selected in the transaction volume list view will be displayed. Click the [OK] button to restore data to this transaction volume. To change the restore destination, mark the Name of volume to restore checkbox, and then click the [...] button. The following window will be displayed. 40

44 Select a volume to which you want to restore data and then click the [OK] button. You will be sent back to the restore window. Check that the name of volume to restore is correct and then click the [OK] button on the [Restore Window]. 5. The following window will appear when the restoration is completed. Click the [OK] button and you will be sent back to the transaction volume list view. 6. This completes restoration. Now you can restart the work. At this point, however, the physical copying of a volume is not completed at the back end. To check the status of physical copying, do as follows: 7. Display the transaction volume list view and check the [Status] field of a target transaction volume. You can check the current restoration (physical copying) status because this field displays the progress status of copying processing. 41

45 8. To check the latest information, either: - Click the [PF5] key, or - Select [Refresh] from the View menu. 9. Business is resumed when business is not resumed. You can perform restoration also using the restore execution command. You can check the restore status also using the restore execution status display command (swstreststat). See the Softek AdvancedCopy Manager User's Guide for restoration in which absolute generations and relative generations are indicated in the backup data that is subject to history management. (For absolute generations, 1 is assigned to the data backed up first and the number increases sequentially. For relative generations, 1 is assigned to the latest data, and the number increases as the data becomes older.) Restoring an individual file Restore an individual file as shown below. Note that you cannot restore an individual file on the GUI window. 1. Using the drive letter allocation command, assign a drive letter to a backup volume. 2. Either execute the COPY command on the DOS prompt window or copy the file using Explorer. 3. Using the drive letter deallocation command, do not assign the drive letter that has been allocated to the backup volume Managing a backup history Display backup history information to check backup volume names, backup date, etc. of backup data under generation management for a transaction volume. Backup history information is used to manage only information stored on a backup volume. Any backup history information exceeding the number of preservation generations defined in a backup policy will be automatically deleted Displaying a backup history You can display a backup history on the backup history list view. To display the backup history list view, first access the server list view, display a storage server in a tree view, and select a transaction volume on the storage server. You can display a backup history also using the history information display command. 42

46 Deleting a backup history Delete a backup history on the server list view. If you display a storage server in a tree view on the server list view, a list of transaction volumes on this storage server will be displayed. After selecting a transaction volume history for which you want to delete a backup history, click the right mouse button and, from the popup menu, select [Delete History]. The following setup window will be displayed. Carefully check the displayed server name and transaction volume name and click the [OK] button. You can delete a backup history also using the history information delete command. 4.6 Changing the setting information You need to change the setting information of Softek AdvancedCopy Manager if any change is made on a storage server or device used in the backup operation. This chapter describes changing the setting information when various changes are made Adding a device After a device is added to any storage server, incorporate it in the backup operation of Softek AdvancedCopy Manager as follows: 1. Display the initial window. For more information, see Chapter 4.4.3, "Starting the initial window". 2. Fetch all the device information for a storage server. When device information is fetched, a newly added device will be detected. Move it to the [Device to be added] field. For information on fetching device information, see Chapter 4.4.5, "Fetching device information on a storage server". 3. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup management window". 4. Set the operation type for a device that has been added. For more information, see Chapter 4.4.8, "Setting the operation type for a device". 5. If the added device has been defined as a transaction volume, set a backup policy for it. For more information, see Chapter , "Setting backup policies" Deleting a device This chapter describes deleting a device depending on the device type Deleting a transaction volume To delete a transaction volume, follow the steps shown below. Please be sure to do this work before removing the operating volume for deletion. 1. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup management window". 2. Delete a backup history for the transaction volume to be deleted. For more information, see Chapter , "Deleting a backup history". 3. Delete a backup policy for the transaction volume to be deleted. If you display a storage server in a tree view, a list of transaction volumes on this storage server will be displayed. After selecting the transaction volume for which you want to delete, select delete backup policy. You can click the right mouse button or from the popup menu, select [Delete backup policy]. The following setup window will be displayed. 43

47 Carefully check the displayed server name and transaction volume name and click the [OK] button. 4. Delete device information for a transaction volume to be deleted. After selecting a storage server, select [Set Device Information] from the [Operation] menu. The following setup window will be displayed. Move a target transaction volume displayed in the "Transaction Volume" field to the "Other Volume" field. Click the [>] button to move a transaction volume Deleting a backup volume To delete a backup volume follow the steps as shown below. Please be sure to do this work before removing the operating volume for deletion. 1. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup management window". 2. Send the backup volume to be deleted into the unused status. When a volume is unused, this volume does not exist in a backup history. If the volume exists in a backup history, delete the backup history. If the volume is already unused, skip to the next step. 3. Delete device information for the backup volume to be deleted. After selecting a storage server, select [Set Device Information] from the [Operation] menu. Then, the following setup window will be displayed. 44

48 Move a target backup volume displayed in the "Backup Volume" field to the "Other Volume" field. Click the [>] button to move a backup volume. If a backup volume is deleted, an already defined backup policy may no longer be met (e.g., the number of backup volumes is less than the number of preservation generations). In such a case, the backup operation can no longer be continued. To avoid such a status, be sure to check already defined backup policies before deleting a backup volume. If only an insufficient number of backup volumes exist as described earlier, first register a backup volume and then delete the target backup volume Adding a storage server Add a storage server to the backup operation as follows: 1. Display the initial window. For more information, see Chapter 4.4.3, "Starting the initial window. 2. Register a storage server. For more information, see Chapter 4.4.4, "Registering a storage server". 3. Fetch all the information of devices connected to the added storage server. For more information, see Chapter 4.4.5, "Fetching device information on a storage server". 4. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup management window". 5. Set the information for the storage server. For more information, see Chapter 4.4.7, "Setting the environment for a backup operation server". 6. Set the operation type for a device whose information has been fetched in Step 3. For more information, see Chapter 4.4.8, "Setting the operation type for a device". 7. Set a backup policy for all the transaction volumes registered in Step 5. For more information, see Chapter , "Setting a backup policy" Deleting a storage server To delete a storage server follow the steps as shown below. Please be sure to do this work before removing the operating volume for deletion. 1. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup management window". 2. Delete the backup history for all the transaction volumes on the storage server to be deleted. For more information, see Chapter , "Deleting a backup history". 3. Delete the backup policy for all the transaction volumes on the storage server to be deleted. 45

49 If you display a storage server in a tree view, a list of transaction volumes on this storage server will be displayed. After selecting a transaction volume for which you want to delete, delete the backup policy. Click the right mouse button and from the popup menu, select [Delete backup policy]. The following setup window will be displayed. Carefully check the displayed server name and transaction volume name and click the [OK] button. 4. Delete device information on the storage server to be deleted. After selecting a storage server, select [Set Device Information] from the [Operation] menu. The following setup window will be displayed. Move all the volumes displayed in the "Transaction Volume" and "Backup Volume" fields to the "Other Volume" field. Click the [>] button to move volumes. 5. Display the initial window. For more information, see Chapter 4.4.3, "Starting the initial window". 6. Delete a Storage server. Select a Storage server and select [Deletion of Server] from the Operation menu. The following window will be displayed. 46

50 Carefully check the server name and click the [OK] button. You can delete server information also using the server information deletion command (stgxfwcmdelsrv). 4.7 Stopping the Operation To stop the backup operation, stop services on a Storage server. Normally, services are automatically stopped when the system is stopped. You can stop an individual service if you need to do so for some reason. For more information, see Chapter 2, "Starting and Stopping a Service". When the service stops, all functions of AdvancedCopy Manager running on the Storage server stop. Stop services on a Storage management server only after checking that all the Storage servers that it manages are stopped. 47

51 48

52 Chapter 5 Backup with the SP Series This chapter describes backup with the SP Series. 5.1 Overview In backup management, the volumes that are backed up with linkage to models of the SP series are managed as transaction volumes under control of the SP series models. At the time of performing backup/restore, these volumes are backed up/restored with models of the SP series. See the Storage Management Processor Administrator's Guide for details on how to back up/restore these volumes. [Figure 5.1 Backup management configuration ] 5.2 Operation Design Design/set up the backup operation as described below: 1. Determining the server to perform backup 2. Determining the backup target 3. Determining a backup policy 4. Preparing a backup volume Determining the server to perform backup Determine the server that will be used to perform backup. The following servers can be used to perform backup: Storage management server This server performs central management and operation of multiple Storage servers. The Storage management server can also act as a Storage server Storage server 49

53 This server controls Softek AdvancedCopy Manager. The locale of the internal code system (code system specified when installing Softek AdvancedCopy Manager on the Storage management server) used by Softek AdvancedCopy Manager must be installed on all Storage servers. 50

54 [Figure 5.2 Example of Storage management server and Storage server configuration] Determining the backup target To perform backup management in linkage with models of the SP series, define the backup target as a transaction 51

55 volume of the SP series. Because the device to be backed up must be managed by a model of the SP series, system design and setup with respect to the SP series models must be performed first. See the Storage Management Processor Administrator's Guide and Storage Management Processor Installation Guide for details on how to perform system design and setup with respect to the devices of the SP series. Specify the devices for which backup is to be performed with the device information setting command. The setting status with respect to the devices for which backup is to be performed can be referenced by the device usage status display command. In order to set up volume as operating volume, there are some points which should be taken into consideration. For details, please refer to " General notes." Please make applicable to backup neither the disk with which the system is stored, nor the disk with which Softek AdvancedCopy Manager is installed Determining a backup policy Set a backup policy for the transaction volume controlled by the SP series. Do not use Softek AdvancedCopy Manager. Instead, use the SP series GUI. See the Direct Backup User's Guide for details on how to set the backup policy via the SP series GUI. Because the policy for the transaction volume operated by the SP series must be set by the SP series GUI, the following commands cannot be executed for a transaction volume controlled by the SP series: Backup policy setting command Backup policy display command Backup policy deletion command Preparing a backup volume In backup/restore linking with the SP series, a backup volume is managed by the SP series. When you design/setup the backup volume, do not use Softek AdvancedCopy Manager. Instead, use the SP series GUI. For more information about the SP-series GUI, see the Direct Backup User's Guide. 5.3 Flow of Operation The following figure shows the flow of backup with the SP series. 52

56 5.4 Preparations Before the start of backup, the following preparations are required Starting a service Before backup is started, the Softek AdvancedCopy Manager service must be started on the storage management server and storage server when these servers are Windows servers. In general, the service is automatically started at 53

57 system startup. However, if the service failed to start for some reason or has stopped, it must be started on each server. For information about starting the service, see Chapter 2, "Starting and Stopping a Service" Setting an access permission When performing backup employment from a backup management screen, an access permission of each operation of a backup management screen is set up. For details of the Setting Method, see Chapter 3, "Security Operation Using Authentication Feature". When only a command performs backup employment, a setup of an access permission is not required Starting the initial window Use the following URL to start the Softek AdvancedCopy Manager initial window: The following GUI (server list view) starts. When applying only by the command, without using GUI, it is not necessary to perform this operation Registering Storage server and SP server Register the Storage server and SP server to be managed. When the Storage server is operated as a Storage management server does not need to add a server. Select [Addition of Server] from the Operation menu. The following window appears. 54

58 For the Storage server to be added, specify a server name, IP address, and port number required for communications. The port number is specified as the "communications service port number", when Agent of Softek AdvancedCopy Manager was installed. In cluster operation, specify the logical IP address of the Storage server as IP address. And specify the port number registered at the time of the cluster setup of Storage server transaction. The [OK] button is pushed after inputting the above item, and additional processing of a Storage server is carried out. In addition, this processing can be carried out also by the server information addition command (stgxfwcmaddsrv). When the SP server is registered, the Softek AdvancedCopy Manager server list view appears, as shown below. The Storage management server need not be registered because it is registered during repository setup Fetching device information on a storage server To perform backup management, information on the devices of each Storage server must be stored in the repository. To fetch information on the devices of each Storage server, choose [Acquisition and reflection of information on all devices] from the [Operation] menu. The following window opens. Information about the hardware of the SP server need not be acquired because the SP server is not managed by AdvancedCopy Manager. Confirm the server for which you want to fetch device information, and then click the [OK] button. After device information is fetched from each server, the following dialog box appears. 55

59 The uppermost list box is displayed when a new device is detected. Move the entries for devices to be managed into the left box. The second list box displays currently managed devices that cannot be detected at this time. When you want to exclude a device from management, move the device entry into the right-hand box. The lowermost list box displays devices for which information has been updated (those, for example, for which the mount point name has been changed). When the Storage server is Windows server, "AdvancedCopy Manager device name" is displayed in the device name. The OK button is pushed after carrying out the above operation, and acquisition processing of device information is carried out. In addition, this processing can be carried out also by the device information collection/reflection command (stgxfwcmsetdev). It takes the time proportional to the total of the device defined in the selected Storage server for this operation. Please execute CPU load and the I/O load low when there are a lot of numbers of devices. It takes about 0.5 seconds a device (partition) as a standard with there no load, and refer, please. When backup synchronous processing or synchronous replication processing is being performed, device information may be unable to be acquired correctly. Therefore, when you take in device information, where all synchronous processing are canceled, please carry out Displaying the backup management window When [Backup Management] is selected from the [File] menu of the server list view, the backup management server list view appears. 56

60 5.4.7 Setting the environment for a backup operation server Set the environment for each storage server. When [Set Server Information] is selected from the Operation menu while the storage server is selected on the backup management window, the following setting window appears. If the target Storage server is Solaris and the Symfoware database exists in the Storage server, a recovery control file output place directory and a work directory are inputted. When a Symfoware database does not exist in a Storage server, or when a Storage server is WindowsNT/2000, HP-UX or Linux, this input item cannot serve as a half-tone display, and cannot be inputted. After completing the input of necessary items, click the [OK] button. You need to make this environment setting also on the storage management server if it serves also as a storage server. This step is not required if the environment setting has already been made on the storage servers. You can also make this environment setting also using the storage server configuration information setting command Setting the operation type for a device Before performing backup, set the operation type of the device as follows: Define each volume to be backed up as a transaction volume. Define each backup destination volume as a backup volume. +Defining the transaction volume Set an operation type on the server list view. On the server list view, select a storage server and select the [Operation] menu and then [Set Device Information]. The following setup window appears. 57

61 A volume displayed in "Other volume" field has no specified device operation type. Set a device operation type as follows: Setting as a "transaction volume which performs SP series employment" After selecting a target volume, click the [<] button on the "Transaction volume(sp)" side. The target volume will be moved to the "Transaction volume(sp)" field. You can make this setting also using the device information setting command (swstdevinfoset). Because the device to be backed up must be managed by a model of the SP series, system design and setup must have been performed with respect to the SP series. See the Storage Management Processor Administrator's Guide and Storage Management Processor Installation Guide for details on the method of design and setup with respect to the SP series. Since it once deletes from registration of operating volume and a Storage server subordinate's device information is again taken in when the slice composition of the volume set up as operating volume etc. is changed, it is necessary to reregister by the device information setting command (swstdevinfoset). 58

62 The setting status of the device to be backed up can be referenced with the device usage status display command. +Defining the backup volume For backup/restore in linkage with a model of the SP series, the backup volume specified as the backup destination is managed by the SP series model and system design and setup of the backup volume is to be performed via the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI Setting backup policies Set the backup policy for the transaction volume under control of the SP series model by using the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI. Because the backup policy for the transaction volume controlled by the SP series model is set by the SP series model, the following commands cannot be executed for the transaction volume operated by the SP series model: Backup policy setting command Backup policy display command Backup policy deletion command Customizing preprocessing and postprocessing scripts If the case of the operation explained below, the backup preprocessing and postprocessing scripts need to be customized: When you want to add special preprocessing and postprocessing to the preprocessing and postprocessing scripts Refer to Appendix A "Backup and Restoration Preprocessing and Postprocessing," for information on the customization. 5.5 Operation This chapter describes how to perform backup with models of the SP series. Before performing backup, set up the environment needed for backup, as described in Chapter 5.4 "Preparations". The same operations as performed by the commands used for backup can also be performed via the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI Executing backup Perform backup in linkage with models of the SP series with the backup execution command. Because the SP series manages disks for backup in linkage with the SP series, confirm the backup status by using the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI. +Snap shot backup To perform snap shot backup, use the backup execution command. 59

63 +Synchronous high-speed backup Perform synchronous high-speed backup as described below: 1. Start backup synchronous processing by executing the backup synchronous processing start command. To cancel backup synchronous processing, use the backup synchronous processing cancel command. 2. You checks that the backup volume under backup synchronous processing is in an equivalent nature maintenance state. It carries out by the situation check of backup, and GUI of SP series. 3. Execute the backup execution command Executing restore Perform restore in linkage with models of the SP series by using the restore execution command.to stop restore operations, and to terminate restore operations that cannot be terminated even if an error occurs, use the GUI of the SP series. For information about the GUI of the SP series, refer to the Direct Backup User's Guide. Contents of a transaction volume cannot be used if a restore operation for the volume has been canceled. In linkage with models of the SP series, the SP series models manage the disks for restore. Therefore, confirm the restore status by using the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI Managing backup histories In linkage with models of the SP series, the SP series models manage the history of backups. Therefore, the backup history cannot be displayed or deleted using Softek AdvancedCopy Manager. Use the SP series GUI to display or delete the backup history. See the Direct Backup User's Guide for details on the SP series GUI. 5.6 Stopping Backup To stop the backup, stop the service on the Storage server. In general, the service stops when the system stops, although it can be stopped independently if it needs to be stopped for some reason. For more information, see Chapter 2, "Starting and Stopping a Service". When the service stops, all functions of AdvancedCopy Manager running on the Storage server stop. Before stopping the service running on the Storage management server, confirm that the operations on all managed Storage servers have stopped. 5.7 Steps for Increases/Decreases in the Number of GR C abinets to Be Managed In Softek AdvancedCopy Manager, information about GR cabinets managed by devices of the SP series is stored in a repository. When adding GR cabinets to or removing GR cabinets from those managed by devices of the SP series, these changes must be reflected in the repository Reflecting changes After starting the Web GUI of Softek AdvancedCopy Manager, refer to Chapter , "Changing GR cabinet management information of the SP series," in the Softek AdvancedCopy Manager User's Guide, to perform the operation to reflect changes. 60

64 Chapter 6 Replication Operation This chapter explains Softek AdvancedCopy Manager replication in a WindowsNT/2000 system. Softek AdvancedCopy Manager uses a partition as the replication unit. In this manual, the term "volume" is used instead of "partition." 6.1 Overview This chapter explains the Softek AdvancedCopy Manager replication function. Using the advanced copy function (OPC or EC function) of a disk array unit, the Softek AdvancedCopy Manager replication function performs high-speed replication between volumes, regardless of the volume capacities. Replication that uses the One Point Copy (OPC) or Remote One Point Copy (ROPC) function of a GR series disk array unit is called snapshot replication. Replication that uses the Equivalent Copy (EC) or Remote Equivalent Copy (REC) function is called synchronized replication. The replication function creates copies so that the information at a certain point of time can be used for some other purpose than the original one. It can be used independently of or combined with the backup function Snapshot replication processing Replicas are created by copying from an original volume to a replica volume using the OPC or ROPC function of a GR series disk array unit. The snapshot replication performs the following two types of processing: 1. When a copy is created, the snapshot processing (OPC or ROPC) from the original volume to the replica volume is executed with the replication creation command (swsrpmake). The replication creation command dismounts or mounts the original volume. This processing determines the original data (for details, see Appendix C, "Replication Script"). ((1) to (4) in Figure 6.1) 2. If the user wants to re-create a replica, only the replication creation command is required. If the previous snapshot processing is in progress, it is stopped and new snapshot processing is started. 61

65 [Figure 6.1 Snapshot replication processing] Snapshot replication is completed when the replication creation command is issued. The actual data is internally copied by the OPC or ROPC function of the GR series disk array unit. The GR740 unit is required when snapshot replication uses the ROPC function of a GR series disk array unit Synchronized replication processing Replicas are created by copying from the original volume to the replica volume using the EC or REC function of a GR series disk array unit. Synchronized replication uses two methods to create a copy: full copying and incremental copying. (In full copying, the original volume is completely copied; it is not partially copied. In incremental copying, only the data from the previous copy that has been updated is copied.) Creating replicas with full copying Use this method to create the first copy in a replication. Creating copies with incremental copying Use this method to create later copies once a previous replica already exists. Copies are created by reflecting the data that has been updated after a previous has been made (full copying and incremental copying). The following is the procedure for synchronized replication: 1. Upon starting synchronized processing from the original volume to the replica volume, using the synchronous processing start command (swsrpstartsync), full copying, likewise, starts. ((1) in Figure 6.2) 62

66 2. Full copying is complete. The original volume and replica volume both enter equivalence status. From this point on, updating of the original volume is sequentially reflected in the replica volume so that data equivalence is always maintained (equivalency holding state). (States in (2) and (3) in Figure 6.2) 3. Synchronized processing is temporarily stopped with the replication creation command (swsrpmake) to create a copy of the original volume. The replication creation command dismounts or mounts the original volume. This processing determines the original data (for details, see Appendix C, "Replication Scripts"). After execution of the replication creation command, the replica volume can be accessed (copy established status). (States in (3) and (4) in Figure 6.2) 4. To create another copy, the synchronized processing that has been temporarily stopped is restarted with the synchronous processing start command. For this copy, only the updated data (incremental) on the original volume since the previous copy was made until the restart of synchronized processing is copied to the replica volume. ((4) in Figure 6.2) 5. When copying of the incremental data has been completed, the status returns to equivalency holding state again. (States in (5) and (6) in Figure 6.2) 6. When this status has been set, the copy is re-created with the replication creation command. ((6) in Figure 6.2) [Figure 6.2 Synchronized replication processing] The GR740 is required to use the EC or REC function of a GR series disk array unit for synchronized replication. The replication creation command cannot be executed unless both the original volume and replica volume are in equivalence status Device name A device (partition) in the disk array unit is the target of Softek AdvancedCopy Manager replication. Softek AdvancedCopy Manager manages the device with a unique name in the form "AdvancedCopy Manager device name." For details of the AdvancedCopy Manager device name, see Chapter 1.5, "Managing a Device on Softek 63

67 AdvancedCopy Manager". 6.2 Operation Design This chapter explains the operation of Softek AdvancedCopy Manager replication. Design replication with the following procedure: Determine the server that performs replication. Determine the replication target Determining the server that performs replication Determine the server that performs replication. The following servers are used to perform replication: Storage management server Multiple storage servers are unified and operated centrally. The storage management server can also be used as a storage server. Storage server Softek AdvancedCopy Manager operations are performed. [Figure 6.3 Configuration of the servers that perform replication] The following requirements apply when box-to-box replication is performed using the remote copying function (ROPC or REC) of a GR series disk array unit: The ROPC or REC function must be installed in both boxes. Both boxes must already be connected using an FC remote adapter (FCRA). In a connection that uses an FCRA, data flows only from INIT side to TARG side. For bi-direction copying, at least two FCRA connections are required. When performing a replication between servers, and data needs to be returned to a reproducing agency from a 64

68 duplicate place like backup server employment and data is returned, it needs to be cautious of the handling of the data in a duplicate place so that it can access normally. If the replication of the NTFS volume on a WindowsNT server is carried out to the volume on Windows2000 server, a file system will be automatically upgraded by OS (Windows2000). When this volume is returned to a WindowsNT server, since the file system is upgraded, there is a problem of it becoming impossible to use chkdsk.exe etc. Therefore, when performing a replication between servers and data needs to be returned to a original from a replica, please make OS of a server the same. Please return data per file without using a replication management function, when it is necessary to perform the replication between servers between different OS's (WindowsNT/Windows2000) and data needs to be returned to a original from a replica Determining a replication target Determine the original volume and replica volume to be used in the replication. The original volume is the volume on which the data to be copied is stored. The replica volume is the volume on which a copy of the data on the originarl volume is stored. In addition, determine the following attributes to be assigned to the original volume and replica volume: 1. Copy direction Determine the direction of copying used in replication. Specify one of the following directions: - bi-direction: Copying is bidirectional between the original volume and replia volume. - uni-direction: Copying is done only from the original volume to the replica volume. During this operation, copying from the replica to the original volume is to be disabled. 2. Operation servers (used only for server-to-server replication) For server-to-server replication, replication of the target original volume or replica volume can be performed only with either the original sever or replica server. - Original server: Storage server to which the original volume is connected - Replica server: Storage server to which the replica volume is connected [Figure 6.4 Servers used in performing replication] In this manual, a storage server used to perform replication is called the operation server. An original server or replica server is specified as the operation server. An operation server can use all of the replication functions. In contrast, any other type of server can use only the information display function and operation release function. In order to set up volume as operating volume, there are some points which should be taken into consideration. For details, please refer to " General notes." 65

69 Please make into a replication object neither the disk with which the system is stored, nor the disk with which Softek AdvancedCopy Manager is installed. 6.3 Flow of Operations The following figure shows the flow of the replication operations. 6.4 Preparations The following preparations are required before replication can start Starting a service Before replication is started, the Softek AdvancedCopy Manager service must be started on the storage management server and storage server. In general, the service is automatically started at system startup. However, if the service failed to start for some reason or has stopped, both servers must restart the service. For information about starting the service, see Chapter 2, "Starting and Stopping a Service" Starting the initial window Use the following URL to start the Softek AdvancedCopy Manager initial window: storage-management-server-address(:port-number)/swstorage/index.html The following GUI (server list view) will be started. 66

70 When applying only by the command, without using GUI, it is not necessary to perform this operation Registering a storage server The Storage management server registers the Storage server to be managed. When the Storage server is operated as a Storage management server does not need to add a server. Select [Addition of Server] from the [Operation] menu. The following window appears. For a storage server to be added, specify a server name, IP address, and port number required for communications. The port number is specified as the "communications service port number", when Softek AdvancedCopy Manager's Agent was installed. In cluster operation, specify the logical IP address of the Storage server as IP address. And specify the port number registered at the time of the cluster setup of Storage server transaction. The [OK] button is pushed after inputting the above item, and additional processing of a Storage server is carried out. In addition, this processing can be carried out also by the server information addition command (stgxfwcmaddsrv) Fetching device information from a storage server As part of replication management, device information on a storage server must first be stored in the repository. To a storage server device, select [Acquisition and Reflection of information on all devices] on the [Operation] menu. The following window appears. 67

71 After checking the server from which device information should be acquired, click the [OK] button. After the device information has been obtained from each server, the following dialog box appears. There are 5 list boxes in the dialog box: the top list box, which is displayed when a new device is detected; the second list box, which lists the devices not currently detected from the devices being managed; the bottom list box, which lists the devices whose information has been updated(for example, the mount point name was changed); the left list box; and the right list box. Move the device to be managed to the left list box, wehereas, move the device to be excluded from the management to the right list box. Please note that the device name displayed here is "AdvancedCopy Manager device-name". After the above operations, click the [OK] button to accept the configuration information. In addition, this processing can be carried out also by the device information collection/reflection command (stgxfwcmsetdev). The time required for this operation is proportional to the total number of devices defined on the Storage server. If the 68

72 number of devices is large, perform this operation while the CPU load and I/O load are low. As a guideline for reference, each operation takes about 0.5 s per device (partition) in a state without load. When backup synchronous processing or synchronous replication processing is being performed, device information may be unable to be acquired correctly. Therefore, when you take in device information, where all synchronous processings are canceled, please carry out Setting the original volume and replica volume Use the replication volume information setting command (swsrpsetvol) to set the original volume and replica volume that will be used in the replication. The information on the registered original volume and replica volume can be checked with the replication volume information display command (swsrpvolinfo). When specifying the volume of another storage server in server-to-server replication, specify the volume in the format "volume-name@storage-server-name." Customizing preprocessing and postprocessing scripts When the operation is as follows, the replication preprocessing and postprocessing scripts need to be customized: When you want to add special preprocessing and postprocessing to the preprocessing and postprocessing scripts When Z drive is not an empty drive When two or more duplicate creation commands are executed simultaneously Refer to Appendix C, "Replication Script," for information on the customization. 6.5 Operations This chapter explains Softek AdvancedCopy Manager replication. Before performing replication, see Chapter 6.4, "Preparations" to set up the environment required for replication. Employment of a replication is offer of only a command. Operation by GUI cannot be performed Executing snapshot replication Use the replication creation command (swsrpmake) to perform snapshot replication Executing synchronized replication Perform synchronized replication using the following procedure: 1. Start synchronized processing using the synchronous processing start command (swsrpstartsync). Use the replication cancellation command (swsrpcancel) to cancel synchronized processing that has already started. 2. After making sure that equivalency holding state has been established with the operation status display command, temporarily stop synchronized processing with the replication creation command (swsrpmake) to create a replica of the original volume. 3. To copy the updated (incremental) data, restart synchronized processing with the synchronous processing start command Backup and restoration using the replication function Data can be restored from the replica volume to the original volume if a volume pair has been defined bi-direction copying with the replication volume information setting command (swsrpsetvol). In contrast to executing replication, restoration can also be performed by specifying the original volume and replica volume in the replication creation command (swsrpmake). 6.6 Changing the Setting Information When a storage server or device required in the replication operation has been changed, the information set in Softek AdvancedCopy Manager must be changed. This chapter explains how to change the information set in Softek AdvancedCopy Manager. 69

73 6.6.1 Changing an original volume or replica volume To change the attributes (copy direction, operation servers of server-to-server replication) of the original volume and replica volume that are set, delete the information with the replication volume information deletion command (swsrpdelvol) and then reexecute the replication volume information setting command (swsrpsetvol) Deleting an original volume or replica volume To delete the original volume or replica volume that are set, use the replication volume information deletion command (swsrpdelvol) Changing the device information of an original or replica volume When making the size of device information and composition change which are used for an original / replica volume, a device composition is changed after deletion processing of the original / replica volume, and setting processing of the volume is performed. Be sure to do the following work before making the size of an original / replica volume or a composition change. When not doing this work, deletion of the original / replica volume after device composition change may not be able to be performed. 1. Perform deletion processing to the original / replica volume for device change. For details, see Chapter 6.6.2, "Deleting an original volume or replica volume". 2. Change the device composition. 3. Perform the additional processing of a device. For more information, see Chapter 6.4.4, "Fetching device information from a storage server". 4. Perform setting of the original / replica volume. 6.7 Stopping the Operation To stop the replication processing, that is in progress, or to change the snapshot replication into the synchronized replication, use the replication cancellation command (swsrpcancel). To stop replication operation, stop the service on the storage server. In general, the service stops when the system stops. The service can be stopped independently if it needs to be stopped for some reason. For more information, see Chapter 2, "Starting and Stopping a Service". When the service stops, all functions of AdvancedCopy Manager running on the storage server stop. Before stopping the storage management server service, make sure that operations on all storage servers under management have stopped. 70

74 Chapter 7 Backup and restore of Exchange Database This chapter explains how to perform backup and restore of the Microsoft Exchange Server databases by employing the backup management function or the replication management function of Softek AdvancedCopy Manager. Before reading this chapter, Fujitsu recommends reading the document "Disaster Recovery for Microsoft Exchange 2000 Server" issued by Microsoft Corporation. The latest version of this document can be downloaded from the following URL: Exchange Server is a trademark or a registered trademark of Microsoft Corporation in the United States and other countries. 7.1 Overview Softek AdvancedCopy Manager performs storage management for Microsoft Exchange Server databases (it is henceforth called Exchange database). The functions of this software are as follows: Backup of Exchange Database Using the advanced copy function of the Fujitsu GR-series disk array units, Softek AdvancedCopy Manager implements high-speed offline backup of Exchange databases. The Exchange Server linkage function of Softek AdvancedCopy Manager supports the following backup methods of Exchange databases: Snapshot type backup (OPC mode) A snapshot image of a transaction volume is created to take a backup. Synchronous type backup (EC mode) Mirroring between a transaction volume and backup volume is stopped (under backup management) or suspended (under replication management) to take a backup Restore of Exchange Database Using the advanced copy function of the Fujitsu GR-series disk array units, Softek AdvancedCopy Manager implements high-speed restoration of Exchange databases. The Exchange Server linkage function of Softek AdvancedCopy Manager supports the following restoration methods of Exchange databases: Point-in-time restore The Exchange database is restored to the state it was in immediately before it was a backup. Roll-forward The Exchange database is restored in the latest state. 7.2 Description of Function This section explains the backup and restoration functions of the Exchange Server linkage function. Softek AdvancedCopy Manager provides two types of Exchange linkage function commands: commands for the backup management function and commands for the replication management function. Use swstxxx_exchange commands for operation that uses the backup management function, and use swsrpxxx_exchange commands for operation that uses the replication management function. No Backup management function command Replication management function command 1 Exchange database information registration command (swstdbinfo_exchange) Exchange database information registration command (swsrpdbinfo_exchange) 2 Exchange device display command Exchange device display command 71

75 (swstdevdisp_exchange) Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deletion command (swstbkpoldel_exchange) Exchange synchronous processing start command (swststartsync_exchange) Exchange backup command execution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore execution command (swstrestore_exchange) Exchange history display command (swsthistdisp_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) (swsrpdevdisp_exchange) Exchange replication start command (swsrpstartsync_exchange) Exchange backup execution command (swsrpbackup_exchange) Exchange data check command (swsrpchkdata_exchange) Exchange restore execution command (swsrprestore_exchange) Exchange operation status display command (swsrpstat_exchange) Exchange replication cancellation command (swsrpcancel_exchange) Operation in collaboration with an SP series server is disabled when the backup management function is used Backup An Exchange database consists of the following physical files: EDB and STM files (database files) A pair of EDB and STM files constitute a database. One set of EDB and STM files exists in each information store. LOG file (transaction log file) The log file contains a transaction log. At least one log file exists in each storage group. CHK file (checkpoint file) The checkpoint file indicates such latest transaction of the transaction log that has already been committed to a database. One CHK file exists in each storage group. The backup of an Exchange database includes the backup of the EDB, STM, CHK, and LOG files. Softek AdvancedCopy Manager uses the advanced copy function of the Fujitsu GR-series disk array units to support the function (commands) for implementing high-speed offline backup of Exchange databases. This function can carry out backup operation very quickly to minimize the load on the server CPU Snapshot type backup The Snapshot type backup is a means of making a backup by performing logical copying of an Exchange database using the OPC/ROPC function of the GR-series disk array units. The Snapshot type backup is performed as follows: 1. The Exchange backup execution command (swstbackup_exchange or swsrpbackup_exchange) is executed to start snapshot processing from a transaction volume to a backup volume (OPC/ROPC logical copying) to create a backup. Snapshot start processing ((3) in the figure shown below) is completed within only a few seconds per volume (partition) (*1). The Exchange backup execution command performs storage group dismount/mount processing and volume preprocessing/postprocessing before and after logical copy start processing. Doing so secures backup data integrity ((1), (2), (4), and (5)). *1 Softek AdvancedCopy Manager performs not only advanced copying but also Exchange Server linkage processing and processing for data integrity checking. For this reason, it takes several tens of seconds to several minutes to complete entire backup processing. 2. The Snapshot type backup is completed when the Exchange backup execution command has returned. Actual 72

76 data copy processing is performed internally by the OPC/ROPC function of the GR-series disk array units ((6) in the figure shown below). 3. The Exchange backup execution command is entered to make another backup (and the above operation is repeated). [Figure 7.1 Snapshot type backup] Synchronous type backup The Synchronous type backup is a means of making a backup by stopping (under backup management) or suspending (under replication management) mirroring (EC/REC) of an Exchange database using the EC/REC function of the GR-series disk array units. The synchronous type backup can be done by performing two functions. The backup and replication management functions makes a backup either by stopping or suspending synchronous processing, respectively. The Synchronous type backup is performed as follows: 1. The Exchange synchronous processing start command (swststartsync_exchange) or the Exchange replication start command (swsrpstrartsync_exchange) starts synchronous processing (EC/REC) from a transaction volume to a backup volume to start total copying ((1) in the figure shown below). After total copying is complete, the transaction and backup volumes become equivalent. After this stage, updates to the transaction volume are successively reflected in the backup volume to keep data equivalency (state of equivalency upkeep). After full copying is complete, the transaction and backup volumes both enter equivalence status. From this point on, updating of the transaction volume is sequentially reflected in the backup volume so that data equivalence is always maintained (equivalency holding state). 2. The Exchange backup execution command (swstbackup_exchange or swsrpbackup_exchange) is executed to stop or suspend synchronous processing and creates a backup. Synchronous processing stop or suspend processing ((4) in the figure shown below) is completed within only a few seconds per volume (partition) (*1). The Exchange backup execution command performs storage group dismount/mount processing and volume 73

77 preprocessing/postprocessing before and after synchronous processing stop or suspend processing. Doing so secures backup data integrity ((2), (3), (5), and (6)). *1 Softek AdvancedCopy Manager performs not only advanced copying but also Exchange Server linkage processing and processing for data integrity checking. For this reason, it takes several tens of seconds to several minutes to complete entire backup processing. 3. To create another backup, the Exchange synchronous processing start command or the Exchange replication start command restarts synchronous processing. The Exchange synchronous processing start command restarts total copying. The Exchange replication start command executes differential copying. In this copy mode, the command copies to the backup volume only the transaction volume data that was updated during the period from the previous replication to the start of synchronous processing. This updated data is called differential data. 4. After data copying is completed, the status returns to equivalency holding state again. 5. After the status returns to equivalency holding state,exchange backup execution command is executed to make another backup (and the above operation is repeated). [Figure 7.2 Synchronous type backup] Restore The Exchange restore execution command recreates all databases in a storage group. Two restoration modes are available, point-in-time and roll-forward Point-in-time restore The Exchange restore execution command with the point option specified executes restoration in point-in-time mode. In point-in-time restore mode, the Exchange database and log files are restored. The database is restored to the state it was in immediately before it was backed up. Data that has been created after the database was backed up is not restored. 74

78 Roll-forward restore The Exchange restore execution command with the roll option specified executes restoration in roll-forward mode. In roll-forward restore mode, previous backup data and the current transaction log are used to restore the database to the latest state. This mode can be used when the log file is normal even though the database is corrupted. It cannot be used if both the database and log files are corrupted. 7.3 Operation Design Exchange database operation can be designed by: Allocating storage group files Determining the server used for backup operation Determining the backup target Determining the backup mode Preparation a backup volume Allocating storage group files File arrangement of a storage group is explained Allocating a database file The Exchange Server linkage function backs up or restores an Exchange database for each storage group. Softek AdvancedCopy Manager copies data in units of volumes (partitions). For this reason, if two or more storage groups exist in the same volume, Softek AdvancedCopy Manager cannot be used for backup and restoration. When designing the physical locations of storage groups, observe the following based on the above restriction: 1. In the volume that is to contain an Exchange database to be backed up, do not store files other than those to be backed up. For instance, if a file other than the Exchange database file is created in the same volume, Softek AdvancedCopy Manager backs up the file as well. Accordingly, when the restore command is executed later, the latest data in files other than the Exchange database file is corrupted. 2. Only one storage group can be stored in the same volume. For instance, when storage groups 1 and 2 are stored in the same volume and storage group 1 is backed up, the files in storage group 2 are also copied. Thereafter, if only storage group 1 is restored, storage group 2 is also restored and accordingly the database in storage group 2 is corrupted (see the figure below). [Figure 7.3 Example of data destruction] If backup is executed while two databases subject to and not subject to backup coexist in the same volume, the data integrity of the latter is not guaranteed. A database cannot be allocated to the volume that contains execution and control files of Exchange Server and Softek AdvancedCopy Manager. When a database file of finishing already needs to be moved, please move a file using an Exchange system manager Allocating a transaction log file Relationship between log file allocation and available restore modes is shown below. 75

79 [Figure 7.4 Relationship between log file allocation and available restore modes] [Table 7.1 Relationship between log file allocation and available restore modes] Restore mode Point-in-time Roll-forward Log file allocation Allocating a database and log file to the same volume Available Unavailable Allocating a database and log file to separate volumes Available Available If the log file is allocated to the same volume as the database, roll-forward restoration cannot be executed. AdvancedCopy copies data in units of volumes. If it copies data while the log file and database exist in the same volume, the latest log file is overwritten by the previous backup of the log file. When roll-forward restore mode is specified, AdvancedCopy Manager checks whether the database and log file exist on the same drive. Roll-forward restoration is enabled when the transaction log file and database are stored on separate drives. Point-in-time restoration is always enabled regardless of the log file location. The CHK file location has nothing to do with the restoration mode. If roll-forward restoration is required for operation, allocate a database and log file to separate volumes. Exchange normally creates a database and transaction log file in the same volume. The storage location of the transaction log file can be changed using the Exchange system manager. If roll-forward restoration is to be used, note the following: 76 Disable the circular logging option to use roll-forward restoration through the storage group properties of the

80 Exchange system manager. This is to prevent a new log entry from overwritting an old one, and enable roll-forward restoration. AdvanceCopy Manager can maintain log file volume by using the Exchange data check command with the dellog option to delete unnecessary log files Distributing EDB and STM files to multiple volumes As shown in the figure below, a database files can be distributed and stored in separate volumes. If a storage group is distributed and stored in multiple volumes, Softek AdvancedCopy Manager backs up all these volumes. [Figure 7.5 Distributing a database files to multiple volumes] Determining the server used for backup operation Decide the server used for backup operation. The following servers can be used for backup operation: +Storage management server The storage management server centrally manages and operates multiple storage servers. The Softek AdvancedCopy Manager manager function must be installed on this server. The storage management server can also be used as a storage server. +Storage server (transaction server) Exchange 2000 Server runs on the storage server. The Softek AdvancedCopy Manager agent function must be installed on this server. Database backup and restore operations are executed from this server. +Storage server (backup server: used for replication management only) This storage server is used as a backup server. The Softek AdvancedCopy Manager agent function must be installed on this server. The Exchange Server system management tool must also be installed to check backup data. A backup volume to which a database volume is to be backed up must be connected to the backup server Determining the backup target Determine the storage group to be backed up and the transaction volumes in which the storage group is allocated. All transaction volumes must be allocated to Fujitsu GR-series disk array units Determining the backup mode Determine the backup mode. The following two backup modes can be selected: +Snapshot type backup The Snapshot type backup uses the OPC function of the Fujitsu GR-series disk array units. A backup is taken by activating the OPC function. +Synchronous type backup This Synchronous type backup uses the EC function of the Fujitsu GR-series disk array units. A backup is taken by stopping (under backup management) or suspending (under replication management) EC in the state of equivalency. 77

81 Preparing a backup volume Prepare a backup volume. Softek AdvancedCopy Manager refers to a volume in which a transaction volume is to be backed up as a backup volume. The backup volume must be stored on a Fujitsu GR-series disk array unit, the size of which must match that of the transaction volume. 7.4 Operation Using the Backup Management Function Preparation Before starting Exchange Server backup operation, perform the following preparations: Defining the Exchange Server environment General preparation Registering database information Setting a backup policy Preparing a device map file (only if the output destination needs to be specified) Preparing for automatic backup operation The following sections refer to the following specifications: <Server configuration> Server type Server name Remarks Storage management server MGR-SVR Storage server EXCHG-SVR - Transaction server (Exchange operation server) - MSCS operation (Exchange virtual server name = VSVR, AdvancedCopy Manager logical node name = nodeagt) 78

82 <Storage group (FirstStorageGroup) file configuration> File type File name Explanation EDB/STM E: Exchsrvr mdbdata priv1.edb E: Exchsrvr mdbdata priv1.stm E: Exchsrvr pdbdata priv1.edb E: Exchsrvr pdbdata priv1.stm E: Exchsrvr mdbdata priv2.edb E: Exchsrvr mdbdata priv2.stm E: Exchsrvr pdbdata priv2.edb E: Exchsrvr pdbdata priv2.stm Database files of mailbox store Mail1 Database files of public store Pub1 Database files of mailbox store Mail2 Database files of public store Pub2 LOG F: Exchsrvr log E00.log FirstStorageGroup transaction log file CHK E: Exchsrvr chk E00.chk FirstStorageGroup checkpoint file <Transaction volume configuration> Drive name AdvancedCopy Manager device name E: g1d1p1 F: g1d2p1 <Backup volume configuration> Drive name AdvancedCopy Manager device name Corresponding transaction volume name E: g1d11p1 g1d1p1 F: g1d12p1 g1d2p Defining the Exchange Server Environment Set up Exchange Server based on the results of backup operation design. +Applying Service Pack This function supports only Exchange 2000 Service Pack 3. Apply Service Pack 3 if it has not been applied. +Allocating EDB, STM, CHK, and LOG files Allocate Exchange Server EDB, STM, CHK, and LOG files. For details, see "Allocating a database file," "Allocating a transaction file," and "Distributing EDB and STM files to multiple volumes." General preparation See Section 4.4 "Preparation"and register transaction volumes and backup volumes. When registering transaction volumes, register all volumes in which database files are allocated. <Example of execution> Register all object database volumes as transaction volumes with AdvancedCopy Manager. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -t g1d1p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -t g1d2p1 swstdevinfoset completed C: > Register a backup volume with AdvancedCopy Manager. C: >set SWSTGNODE=nodeAGT 79

83 C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -b g1d11p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -b g1d12p1 swstdevinfoset completed C: > Registering database information Use the Exchange database information registration command (swstdbinfo_exchange) to: Register Exchange database information in the management file Perform the initial settings before backing up or restoring an Exchange database After the Exchange Server configuration has been changed. <Example of execution> Store database information for storage group FirstStorageGroup. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstdbinfo_exchange -evs VSVR -sgname FirstStorageGroup swstdbinfo_exchange successfully completed C: > Setting a backup policy Execute the Exchange backup policy setting command (swstbkpolset_exchange) to set the same backup policy for all transaction volumes in the storage group. Use the backup policy display command (swstbkpoldisp) to check the backup policy that has been set. <Example of execution> Set a backup policy (the number of generations to be saved = 1, the number of interval days = 7) for storage group FirstStorageGroup. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstbkpolset_exchange -evs VSVR -s 1 -i 7 -sgname FirstStorageGroup swstbkpolset_exchange successfully completed C: > Preparing a device map file (for specified output destinations) If the output destination backup volume is to be specified, allocate a device map file by referring to "Preparing a device map file." Preparing for automatic backup operation Backup operation by Softek AdvancedCopy Manager can be automated using SystemWalker/OperationMGR. For this purpose, use commands provided by Softek AdvancedCopy Manager. Please refer to chapter 10 "Commands" of this manual Executing backup operation The backup operation for Exchange Server databases can be performed by following the procedure below: Starting synchronous processing (only if synchronous backup operation is to be performed) Executing backup operation Starting synchronous processing (for synchronous backup operation) If backup operation is to be performed in synchronous backup operation mode, synchronous processing (EC) must be started in advance. To start synchronous processing, use the Exchange synchronous processing start command (swststartsync_exchange). 80

84 <Example of execution> Start synchronous processing for storage group FirstStorageGroup. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swststartsync_exchange -evs VSVR -sgname FirstStorageGroup swststartsync_exchange successfully completed C: > Backing up databases To back up an Exchange database, use the Exchange backup execution command (swstbackup_exchange). This command backs up databases in units of storage groups. The Exchange backup execution command performs the following to back up all databases in the storage group in offline mode: 1. Dismounts all information stores in the storage group. 2. Issues the backup execution command (swstbackup) to copy to the backup volume all files (EDB, STM, CHK, and LOG) constituting the storage group, with the advanced copy function. 3. Mounts the information stores. [Figure 7.6 Offline backup] If an error occurs while the Exchange backup execution command (swstbackup_exchange) is processing a database constituting multiple volumes using the backup execution command (swstbackup), the processing is interrupted immediately. In the case of synchronous backup operation, synchronous processing may have already been stopped for some transaction volumes. After removing the error cause, use the Exchange synchronous processing start command (swststart_exchange) to start synchronous processing for these transaction volumes. <Example of execution> Execute backup operation for storage group FirstStorageGroup. In the case of synchronous backup operation, use the backup synchronous processing progress display command (swstsyncstat) to verify that synchronous processing for all transaction volumes is in the state of equivalence (100% indicated in the Execute column). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstbackup_exchange -evs VSVR -sgname FirstStorageGroup swstbackup_exchange successfully completed 81

85 C: > To confirm backup history information, use the Exchange history display command (swsthistdisp_exchange). <Example of execution> Display backup history information for storage group FirstStorageGroup. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsthistdisp_exchange -evs VSVR -sgname FirstStorageGroup Exchange Storage Group:FirstStorageGroup Generation Version Backup-Date Transaction-Device /12/01 22:00 g1d1p1 Mount-Point=E: (NTFS) /12/01 22:00 g1d2p1 Mount-Point=F: (NTFS) Server=EXCHG-SVR Device=g1d1p1 Mount-Point=E: (NTFS) Generation Version Backup-Date Backup-Disk Status Execute /12/01 22:00 g1d11p1 succeeded ---- Server=EXCHG-SVR Device=g1d2p1 Mount-Point=F: (NTFS) Generation Version Backup-Date Backup-Disk Status Execute /12/01 22:00 g1d12p1 succeeded ---- C: > Verifying backup data After executing the Exchange backup execution command (swstbackup_exchange), execute the Exchange data check command (swstchkdata_exchange) to verify the backup data. Backup data is not considered valid for restoration until it has been verified by the Exchange data check command. After backup, be sure to verify the data to determine that it is valid. If data must be saved to a tape library, verify the backup data before saving it. The time required for backup data verification depends on the storage group capacity. The time required increases as the size of the resources making up the storage group increases. When planning a backup schedule, be sure to consider the backup data verification time. This command provides a function (dellog) that deletes unnecessary log files created before database backup from the transaction volume. Using the function when the circular logging option is disabled can suppress any increase of space requirements for a volume in which log files are stored. <Example of execution> Verify the backup data of storage group FirstStorageGroup after backup execution. Specify the dellog option to delete unnecessary log files. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstchkdata_exchange -evs VSVR -dellog -sgname FirstStorageGroup swstchkdata_exchange successfully completed C: > Executing restore operation Point-in-time restoration (restoration to the state at the time of backu p) The point-in-time restoration restores all databases in the storage group to the state they were in immediately before they were backed up. It thus does not restore data that has been created after backup. Point-in-time restoration can be executed by issuing the Exchange restore execution command (swstrestore_exchange) with the point operation specified. When the point option is specified, the Exchange restore execution command performs the following to 82

86 restore the storage group to the state it was in immediately before it was backed up: 1. Dismounts all information stores in the storage group. 2. Issues the restore execution command (swstrestore) to restore from the backup volume all files (EDB, STM, CHK, and LOG) constituting the storage group, with the advanced copy (OPC) function. 3. Mounts the information stores. [Figure 7.7 Point-in-time restoration] <Example of execution> Execute point-in-time restoration for storage group FirstStorageGroup. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstrestore_exchange -evs VSVR -point -sgname FirstStorageGroup swstrestore_exchange successfully completed C: > Roll-forward restoration (restoration to the latest state) The roll-forward restoration restores only the database (EDB/STM) files using the advanced copy (OPC) function and does not restore the LOG file. If a LOG file coexists in a database drive, roll-forward restoration cannot be executed. Roll-forward restoration can be executed by issuing the Exchange restore execution command (swstrestore_exchange) with the roll option specified. When the roll option is specified, the Exchange restore command performs the following to restore the storage group to the latest state: 1. Verifies that the EDB and STM files are stored on a drive separate from the one on which a LOG file is stored. 2. Dismounts all information stores in the storage group. 3. Issues the restore execution command (swstrestore) to restore the EDB and STM files from the backup volumes. 4. Checks the last consistent log for the database to make sure that all transaction logs required for roll-forward are included in the log file. 5. Deletes the CHK file (this causes roll-forward processing to be executed after mounting). 6. Mounts the information stores. 83

87 [Figure 7.8 Roll-forward restoration] <Example of execution> Execute roll-forward restoration for storage group FirstStorageGroup. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstrestore_exchange -evs VSVR -roll -sgname FirstStorageGroup swstrestore_exchange successfully completed C: > The following conditions must be satisfied to carry out roll-forward restoration: All transaction logs created after the time when the latest full backup was executed exist. The existing log files have consecutive generation numbers ("XXXXX" of E0nXXXXX.log). A new backup was created immediately after the database path was changed. A new backup was created immediately after ESEUTIL /p (for restoration of a corrupted database) or ESEUTIL /d (database defragmentation or compression) was executed. All databases in the storage group were backed up immediately after a database was added to the storage group or deleted from it Checking the operation status To check the copy status, use the backup synchronous processing progress display command (swstsyncstat), backup execution status display command (swstbackstat), or restore execution status display command (swstreststat) Stopping operation To stop Synchronous type backuping, use the Exchange synchronous processing cancel command (swstcancelsync_exchange). <Example of execution> Stop synchronous processing in execution. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstcancelsync_exchange -evs VSVR -sgname FirstStorageGroup swstcancelsync_exchange successfully completed C: > 84

88 7.4.7 MSCS operation Softek AdvancedCopy Manager supports Microsoft Clustering Service (MSCS). For more information, see the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." About note of Backup operation for Exchange Database, see Chapter 7.3, "Backup Operation", in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." 7.5 Operation Using the Replication Management Function Preparation Before starting Exchange Server backup operation, perform the following: Defining the Exchange Server environment General preparation Registering database information Preparing a device map file Preparing for automatic backup operation The following sections refer to the following specifications: <Server configuration> Server type Server name Remarks Storage management server Storage server MGR-SVR EXCHG-SVR - Transaction server (Exchange operation server) - MSCS operation (Exchange virtual server name = VSVR, AdvancedCopy Manager logical node name = nodeagt) Storage server BKUP-SVR - Backup server <Storage group (FirstStorageGroup) file configuration> 85

89 File type File name Explanation EDB/STM E: Exchsrvr mdbdata priv1.edb E: Exchsrvr mdbdata priv1.stm E: Exchsrvr pdbdata priv1.edb E: Exchsrvr pdbdata priv1.stm E: Exchsrvr mdbdata priv2.edb E: Exchsrvr mdbdata priv2.stm E: Exchsrvr pdbdata priv2.edb E: Exchsrvr pdbdata priv2.stm Database files of mailbox store Mail1 Database files of public store Pub1 Database files of mailbox store Mail2 Database files of public store Pub2 LOG F: Exchsrvr log E00.log FirstStorageGroup transaction log file CHK E: Exchsrvr chk E00.chk FirstStorageGroup checkpoint file <Transaction volume configuration> Drive name AdvancedCopy Manager device name E: F: <Backup volume configuration> Drive name AdvancedCopy Manager device name Corresponding transaction volume name E: F: Defining the Exchange Server Environment Set up Exchange Server based on the results of backup operation design. +Applying Service Pack This function supports only Exchange 2000 Service Pack 3. Apply Service Pack 3 if it has not been applied. +Allocating EDB, STM, CHK, and LOG files Allocate Exchange Server EDB, STM, CHK, and LOG files. For details, see "Allocating a database file," "Allocating a transaction file," and "Distributing EDB and STM files to multiple volumes." +Installing the Exchange system management tool (backup server operation o nly) To use backup server operation, be sure to install the Exchange Server system management tool on the backup server and apply Service Pack General preparation Carry out the procedures indicated in Section 6.4 "Preparation"while noting the following: Register all transaction volumes and their target backup volumes. Use a transaction volume only as an original volume and a backup volume only as a replica volume. (Do not use a transaction volume as a replica volume or a backup volume as an original volume.) To perform backup server operation, use the server that operates databases (replica volume server) as an operating server. (Execute the replica volume information setting command with ORG specified in the o option.) To enable restoration, do not specify the u option that restricts copying only in one direction from the original volume (transaction volume) to the replica volume (backup volume). <Example of execution> Define the target transaction volume/backup volume using the replication volume information setting command (swsrpsetvol). Enter the command through the transaction server (EXCHG-SVR). 86

90 C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpsetvol -o ORG g1d1p1 swsrpsetvol completed C: >C: Win32App AdvancedCopyManager bin swsrpsetvol -o ORG g1d2p1 swsrpsetvol completed C: > Registering database information Use the Exchange database information registration command (swsrpdbinfo_exchange) to: Register Exchange database information in the management file Initialize before backing up or restoring an Exchange database After changingthe Exchange Server configuration <Example of execution> Store database information for storage group FirstStorageGroup. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpdbinfo_exchange -evs VSVR -sgname FirstStorageGroup swsrpdbinfo_exchange successfully completed C: > Preparing a device map file Create a device map file used for Exchange linkage commands to reference the correspondence between a transaction volume and backup volume defined in the file. These commands work on the transaction volumes and backup volumes defined in the device map file. Allocate the device map file to an arbitrary location on the original volume server on which Exchange Server runs. Specifying the file when executing a command automatically determines the backup volume. +Definition in a device map file An example of definition in a device map file is shown below. <Sample definition in device map file> # Device map file for Softek AdvancedCopy Manager Exchangr Server support function # Transaction vlumt name backup volume name # (Original volume name) (Replica volume name) # Storage group:firststoragegroup g1d1p1 g1d2p1 g1d11p1@bkup-svr # E:EDB/STM/CHK file g1d12p1@bkup-svr # F:LOG file # Storage group:secondstoragegroup g1d3p1 g1d4p1 g1d13p1@bkup-svr # G:EDB/STM/CHK file g1d14p1@bkup-svr # H:LOG file : The rules for creating a device map are shown below: Write a transaction volume and the target backup volume on one line. Separate the transaction volume name and backup volume name using one or more en-size blanks or tab characters. One or more en-size blanks or tab characters may be included in the section from the beginning of a line to the transaction volume name and the section from the backup volume name to the end of the line (linefeed code). Use the format "volume-name@server-name" to specify a backup volume on a backup server. Only the "volume-name" format can be used to specify a transaction volume. Note that the format "volume-name@exchange-transaction-server-name" cannot be used. Blank lines (en-size blanks or tab characters) can be included in the file. 87

91 Any description between symbol "#" and the end of a line is regarded as a comment. Only one backup volume can be specified for one transaction volume in a single device map file. If two or more backup volumes are specified, the statement on the line where one appears first is used. Processing for detecting duplicated lines is not performed while the device map file is being read. If two or more generations of backup volumes are used, prepare as many device map files as there are generations. The device map file can contain the statement of a transaction volume not included in the storage group to be processed. (See the sample statement shown above.) For a storage group consisting of multiple volumes, provide information on all the transaction volumes in a single device map file. (The information must not be divided into multiple files) Preparing for automatic backup operation Backup operation by Softek AdvancedCopy Manager can be automated using SystemWalker/OperationMGR. For this purpose, use commands provided by Softek AdvancedCopy Manager. Please refer to chapter 10 "Commands" of this manual Executing backup operation The backup operation for Exchange Server databases can be performed by following the procedure below: Starting or restarting synchronous processing (only if synchronous backup operation is to be performed) Executing backup operation Starting or restarting synchronous processing (for synchronous backu p operation) If backup operation is to be performed in synchronous backup operation mode, synchronous processing (EC) must be started or restarted in advance. To start synchronous processing, use the Exchange replication start command (swsrpstartsync_exchange). <Example of execution> Start synchronous processing for storage group FirstStorageGroup. Assume that the device map file that defines the correspondence between the transaction volume (storage group allocation volume) and backup volume is K: STG DEV.map. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpstartsync_exchange -evs VSVR -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpstartsync_exchange successfully completed C: > Backing up databases To back up an Exchange database, use the Exchange backup execution command (swsrpbackup_exchange). This command backs up databases in units of storage groups. The Exchange backup execution command performs the following to back up all databases in the storage group in offline mode: 1. Dismounts all information stores in the storage group. 2. Issues the replication creation command (swsrpmake) to copy to the backup volume all files (EDB, STM, CHK, and LOG) constituting the storage group, with the advanced copy function. 3. Mounts the information stores. 88

92 [Figure 7.9 Offline backup] If an error occurs while the Exchange backup execution command (swsrpbackup_exchange) is processing a database distributed to multiple volumes using the replication creation command (swsrpmake), the processing is interrupted immediately. In the case of synchronous backup operation, synchronous processing may have already been stopped for some transaction volumes. After removing the error cause, use the Exchange replication start command (swsrpstartsync_exchange) to resume synchronous processing for these transaction volumes. <Example of execution> Execute backup operation for storage group FirstStorageGroup. In the case of synchronous backup operation, use the Exchange operation status display command (swsrpstart_exchange) to verify that synchronous processing for all transaction volumes is in the state of equivalence (100% indicated in the Execute column). Assume that the device map file that defines the correspondence between the transaction volume and backup volume is K: STG DEV.map. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpbackup_exchange -evs VSVR -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpbackup_exchange successfully completed C: > Verifying backup data After executing the Exchange backup execution command (swsrpbackup_exchange), execute the Exchange data check command (swsrpchkdata_exchange) to verify the backup data. Backup data is not considered valid for restoration until it has been verified by the Exchange data check command. After backup, be sure to verify the data to determine that it is valid. If data must be saved to a tape library, verify the backup data before saving it. The time required for backup data verification depends on the storage group capacity. The time required increases as the size of the resources making up the storage group increases. When planning a backup schedule, be sure to consider the backup data verification time. The Exchange Server management tool (ESEUTIL command) is used to verify backup data. When a backup server is used, the Exchange Server system management tool must be installed on the backup server. This command provides a function (dellog) that deletes unnecessary log files created before database backup 89

93 from the transaction volume. Using the function when the circular logging option is disabled can suppress any increase of space requirements for a volume in which log files are stored. <Example of execution> Verify the backup data of storage group FirstStorageGroup after execution of backup. Assume that the device map file that defines the correspondence between the transaction volume and backup volume is K: STG DEV.map. Specify the dellog option to delete unnecessary log files. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpchkdata_exchange -evs VSVR -dellog -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpchkdata_exchange successfully completed C: > Executing restore operation Use the Exchange restore execution command (swsrprestore_exchange) to restore an Exchange database. This command carries out restoration in units of storage groups. One of the following two restore modes can be selected: Point-in-time restoration (restoration to the state at the time of backup) Roll-forward restoration (restoration to the latest state) Point-in-time restoration (restoration to the state at the time of backu p) The point-in-time restoration restores all databases in the storage group to the state they were in immediately before they were backed up. It thus does not restore data that has been created after backup. Point-in-time restoration can be executed by issuing the Exchange restore execution command (swsrprestore_exchange) with the point operation specified. When the point option is specified, the Exchange restore execution command performs the following to restore the storage group to the state it was in immediately before it was backed up: 1. Dismounts all information stores in the storage group. 2. Issues the replication creation command (swsrpmake) to restore from the backup volume all files (EDB, STM, CHK, and LOG) constituting the storage group, using the advanced copy (OPC) function. 3. Mounts the information stores. [Figure 7.10 Point-in-time restoration] <Example of execution> Execute point-in-time restoration for storage group FirstStorageGroup. Assume that the device map file that defines the correspondence between the transaction volume (storage group allocation volume) and backup volume is K: STG DEV.map. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT 90

94 C: >C: Win32App AdvancedCopyManager bin swsrprestore_exchange -evs VSVR -point -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrprestore_exchange successfully completed C: > Roll-forward restoration (restoration to the latest state) The roll-forward restoration restores only the database (EDB and STM) files using the advanced copy (OPC) function and does not restore the LOG file. If a LOG file coexists on a database drive, roll-forward restoration cannot be executed. Roll-forward restoration can be executed by issuing the Exchange restore execution command (swsrprestore_exchange) with the roll option specified. When the roll option is specified, the Exchange restore command performs the following to restore the storage group to the latest state: 1. Verifies that the EDB and STM files are stored on a drive separate from the one on which a LOG file is stored. 2. Dismounts all information stores in the storage group. 3. Issues the replication creation command (swsrpmake) to restore the EDB and STM files from the backup volumes. 4. Checks the last consistent log for the database to make sure that all transaction logs required for roll-forward are included in the LOG file. 5. Deletes the CHK file (this causes roll-forward processing to be executed after mounting). 6. Mounts the information stores. [Figure 7.11 Roll-forward restoration] <Example of execution> Execute roll-forward restoration for storage group FirstStorageGroup. Assume that the device map file that defines the correspondence between the transaction volume (storage group allocation volume) and backup volume is K: STG DEV.map. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrprestore_exchange -evs VSVR -roll -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrprestore_exchange successfully completed C: > The following conditions must be satisfied to carry out roll-forward restoration: All transaction logs created after the time when the latest full backup was executed exist. The existing log files have consecutive generation numbers ("XXXXX" of E0nXXXXX.log). 91

95 A new backup was created immediately after the database path was changed. A new backup was created immediately after ESEUTIL /p (for restoration of a corrupted database) or ESEUTIL /d (database defragmentation or compression) was executed. All databases in the storage group were backed up immediately after a database was added to the storage group or deleted from it Checking the operation status Check the copy status using the Exchange operation status display command (swsrpstat_exchange) Stopping operation Stop copy processing using the Exchange replication cancel command (swsrpcancel_exchange). <Example of execution> Stop synchronous processing in execution. Enter the command through the transaction server (EXCHG-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpcancel_exchange -evs VSVR -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpcancel_exchange successfully completed C: > MSCS operation Softek AdvancedCopy Manager supports Microsoft Clustering Service (MSCS). For more information, see the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." About note of Replication operation for Exchange Database, see Chapter 7.4, "Replication Operation", in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." 92

96 Chapter 8 Backup and Restore of SQL Server Database This chapter explains how to perform backup and restore of the SQL Server 2000 databases by employing the backup management function or the replication management function of Softek AdvancedCopy Manager. SQL Server 2000 is a registered trademark of Microsoft Corporation in the U.S.A. and elsewhere. 8.1 Overview SQL Server 2000 is an enterprise database software that serves as the core of Microsoft(R).NET Enterprise Servers family. Softek AdvancedCopy Manager performs high-speed backup and restore of SQL Server 2000 databases constructed on GR series by cooperating with SQL Server Softek AdvancedCopy Manager provides the functions (commands) to perform high-speed backup and restore of SQL Server 2000 databases. SQL Server backup execution command SQL Server restore execution command As for the SQL Server backup execution command and the SQL Server restore execution command, two kinds are provided for the backup management function and for the replication management function. Swstbackup_sqlsvr and swstrestore_sqlsvr are used when operating by the backup management function, and swsrpbackup_sql and swsrprestore_sql are used when operating by the replication management function. SQL Server backup execution command SQL Server restore execution command Backup Function For backup management function swstbackup_sqlsvr swstrestore_sqlsvr For replication management function swsrpbackup_sql swsrprestore_sql An SQL Server 2000 database consists of the following physical files (database files): Primary data file (One file is required per database.) Secondary data files (There may be no file or more than one file.) Transaction log files (At least one file is required per database.) Backing up all database files is called the "database backup" or "full backup". Backing up only logs is called the "log backup". The SQL Server backup execution command performs the database backup at high speed: Copies the database files (primary data file, secondary data files, and transaction log files) onto the backup volumes. Executes the data copy instantly by the advanced copy function, without utilizing server CPUs. Realizes an online backup by cooperating with the VDI(Virtual Device Interface) mechanism of SQL Server

97 [Figure 8.1 Backup Function Overview] In the backup operation of SQL Server 2000, both the "database backup" and the "log backup" are generally used in combination. The following figure shows an example of backup operation that combines the database backup using Softek AdvancedCopy Manager and the log backup using SQL Server. In this example assuming the operation cycle as one week, the database backup is performed on Sunday and the log backup is performed on weekdays: 94

98 [Figure 8.2 Example of backup operation] Softek AdvancedCopy Manager provides the "database backup" function. Therefore, backup and restore (recovery) of a transaction log should be performed by SQL Server's Enterprise Manager and Transact-SQL, etc. The databases which can be backed up with Softek AdvancedCopy Manager are only user databases, and so system databases (master, msdb, model and distribution) cannot be backed up with Softek AdvancedCopy Manager. The backup operation of the system databases should be performed with SQL Server System Databases (master, msdb, model, distribution) User Databases O:Provided, X:Not provided SQL Server 2000 O Database backup O O Log backup O X Softek AdvancedCopy Manager X In this appendix, the "database restore" refers to changing back a database to the status at the time of database backup. In contrast, the "database recovery" refers to applying logs to a database on which the database restore has been performed to restore the database to a specific point or the latest point after the database backup Restore Function The SQL Server restore execution command recreates a database using the database files restored from a database backup. A series of processing of (1)restoring database files, (2)recreating a database and (3)applying transaction logs can be completed in a short time by using OPC(One Point Copy) of the advanced copy function. 95

99 [Figure 8.3 Restore Function Overview] In the example of operation of Figure 8.2, the following figure shows how to perform restore up to the latest point when a failure occurs before the log backup on Friday: [Figure 8.4 Example of restore] 8.2 Operation Design Work out the following backup operation designs before you perform the backup operation of SQL Server Backup Operation Design of SQL Server Database Design the backup operation of a database. For more information, see "Designing a Backup and Restore Strategy" in 96

100 the "SQL Server Books Online". Additionally, observe the following limitations on placing database files Database in raw partitions Softek AdvancedCopy Manager does not support a database constructed in raw partitions. Construct a database on file systems Placement of files Softek AdvancedCopy Manager performs copy in units of volume (i.e., in units of partitions). Thus, do not place any file other than target database files on the volumes on which the database files are placed. If a file irrelevant to the database files to be backed up is placed on a volume to be backed up, not only the data of the file but also the entire file system might be corrupted. In particular, do not place any database file on the system drive or on the volume that stores the executable files and management files of SQL Server 2000 and Softek AdvancedCopy Manager. Both mixing files of N(>2) databases on one volume and mixing files of N(>2) databases on M(>2) volumes are possible, however, these N databases must be databases under the control of the same instance. [Figure 8.5 N databases on one volume] [Figure 8.6 N databases on M volumes] If you perform the backup for the database of such a configuration, specify all the databases which exist on the 97

101 volumes. After SQL Server 2000 secures the data consistency by freezing all the specified databases, Softek AdvancedCopy Manager executes the copy processing to all the volumes where the files are placed. If the backup is performed without specifying all the databases, the database backup cannot be normally obtained (the file systems of the backup volumes might be damaged). The above-mentioned database configuration is seen in the system with insufficient drive letters or the system where many small-scale databases exist, and has the following problems in respect of backup operation: When two or more databases are backed up at the same time, all the specified databases are frozen by SQL Server 2000 until processing is completed. If the frozen time of the data base becomes long, there is a possibility that the backup cannot be normally completed. Design databases so that the number of the databases to be backed up may decrease as much as possible. If you will restore a specific database, you cannot use the advanced copy for file restore processing. In this case, only the database files to be restored must be restored by the means of the COPY command and the FTP, etc. The advanced copy can be used only for file restore in the case where all the databases are restored. As shown in Figure 8.7, you can place database files distributed over multiple volumes. Softek AdvancedCopy Manager performs processing on all the volumes on which database files are placed. [Figure 8.7 Distributed placement of database files] Determining the servers to perform backup Determine the servers to perform backup operation. The following servers are used to perform backup: +Storage management server Multiple storage servers are unified and operated centrally. The manager function of Softek AdvancedCopy Manager should be installed. A storage management server can also be used as a storage server. +Storage server (Business server) SQL Server 2000 is operated on this server. The agent function of Softek AdvancedCopy Manager should be installed. Backup and restore of databases are performed on this server. +Storage server (Backup server: Only if replication management function is u sed) This server serves as a backup server. The agent function of Softek AdvancedCopy Manager should be installed. The volumes (i.e., backup volumes) which become backup destination of database volumes are connected to this server. The operation using a backup server can be executed only if the replication management function is employed and so cannot be executed if the backup management function is employed. 98

102 Determining a backup target Determine the databases to be backed up and the volumes (database volumes) where their database files are placed. All the database volumes must be placed on disk array unit GR series Determining a backup method Determine the backup method. The following two can be selected as a backup method. +Snapshot type backup It is a backup method using OPC/ROPC function of disk array unit GR series. The backup is obtained by starting OPC/ROPC. +Synchronous type backup It is a backup method using EC/REC function of disk array unit GR series. The backup is obtained by stopping (in case of employing backup management function) or suspending (in case of employing replication management function) EC/REC in the equivalency holding state Preparing a backup volume Prepare backup volumes. The volumes which become backup destination of database volumes are called backup volumes. All the backup volumes must be placed on disk array unit GR series. 8.3 Operation by backup management function Preparations Carry out the following preparations before the backup operation of SQL Server 2000 is started. Setting the environment for SQL Server Carrying out a general preparation Changing the backup preprocessing script Preparing a device map file (Only if the backup destination is specified) Recording the output path of a metadata file Preparing the automated operation of backup The following example is used for explanation in the following sub sections. 99

103 [Server configuration] Server type Storage management server Storage server <Database configuration> Server name MGR-SVR DB-SVR comment Business server operating on MSCS(AdvancedCopy Manager's logical node name=nodeagt, SQL Server virtual server name=vserver) Database name Database file name Database file type DB01 DB02 DB03 <Database volume configuration> Drive letter D: g1d1p1 D: SQLSVR DB01.mdf E: SQLSVR DB01.ndf F: SQLSVR DB01.ldf D: SQLSVR DB02.mdf E: SQLSVR DB02.ndf F: SQLSVR DB02.ldf D: SQLSVR DB03.mdf E: SQLSVR DB03.ndf F: SQLSVR DB03.ldf AdvancedCopy Manager device name Primary data file Secondary data file Transaction log file Primary data file Secondary data file Transaction log file Primary data file Secondary data file Transaction log file 100

104 E: g1d2p1 F: g1d3p Setting the environment for SQL Server Set up SQL Server based on the result of database backup operation design. If, in particular, you apply logs at the time of recovering a database, set the "recovery model" of a database to "Full" or "Bulk-Logged". For more information, see "Designing a Backup and Restore Strategy" in the "SQL Server Books Online" Carrying out a general preparation Do the work described in Capter 4.4 "Preparation", noting the following points. When you register transaction volumes, register all the volumes on which database files are placed. Also, set the same backup policies for all the volumes on which database files are placed. The management of backup history information becomes easy by making the backup policies the same though the backup can be executed even if the backup policies are not made the same. <Execution example> Register all the target database volumes in AdvancedCopy Manager as transaction volumes, and set the backup policies. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -t g1d1p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -t g1d2p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -t g1d3p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstbkpolset -s 1 -i 7 g1d1p1 g1d1p1 swstbkpolset completed C: >C: Win32App AdvancedCopyManager bin swstbkpolset -s 1 -i 7 g1d2p1 g1d2p1 swstbkpolset completed C: >C: Win32App AdvancedCopyManager bin swstbkpolset -s 1 -i 7 g1d3p1 g1d3p1 swstbkpolset completed C: > Register the backup volumes in AdvancedCopy Manager. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -b g1d11p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -b g1d12p1 swstdevinfoset completed C: >C: Win32App AdvancedCopyManager bin swstdevinfoset -b g1d13p1 swstdevinfoset completed Changing a backup preprocessing script Softek AdvancedCopy Manager releases and reassigns a drive letter of a transaction volume in the preprocessing and postprocessing of backup and restore, respectively. This processing enables copy while maintaining the consistency of a file system. However, if you backup an SQL Server 2000 database, the drive letter release processing in the backup preprocessing fails because the database files are opened by SQL Sever However, you need not release drive letters because SQL Server 2000 guarantees the consistency of files making up the database. Therefore, change the backup preprocessing script (OpcBackupPre.js) like Figure 8.8 to disable the drive letter 101

105 release processing for the transaction volumes on which database files are placed, as follows: [Figure 8.8 Example of modifying a backup preprocessing script] Change the script carefully. If you change the script incorrectly, the backup command returns an error. Place only database files on the transaction volumes on which database files are placed because no drive letter release processing is performed Preparing a device map file (Only if the backup destination is specifie d) If you specify the backup volumes which become copy destinations, create a device map file referring to Recording the output path of a metadata file At the time of backup execution, the "metadata" which includes information, such as path name, size and file type, etc. of the database files of the database for backup is outputted from SQL Server Softek AdvancedCopy Manager saves a metadata file in a backup volume. A metadata file is restored to a database volume at the time of restore of database files. Since it becomes indispensable when executing SQL Server restore execution command (swstrestore_sqlsvr), it needs to record the absolute path of a metadata file in advance. The metadata file is saved by the name of ""DB name".swst-dmp" at the folder where the database file with file identification number (FILE_ID) 1 exists. For example, supposing that the absolute path of the database file with file identification number 1 of a database DB01 is "D: SQLSVR DB01_data.mdf", the absolute path of a metadata file will serve as "D: SQLSVR DB01.swst-dmp." Usually, although the database file with file identification number 1 is a primary data file, check it in the following procedure by way of precaution. 1. Perform Transact-SQL "USE database name EXEC SP_HELPFILE". 2. Look for the record with which the column "file id" is 1 from an execution result. The content of the column "filename" of the record is the absolute path of the database file with file identification number

106 Although it is strictly required to secure the capacity for saving a metadata file in operating volume, since the size of a metadata file is small, there is almost no necessity for consideration. (The size of a metadata file depends on the number of files of a database. For example, it is about 20KB in the database of 10 files composition) Preparing the automated operation of backup You can automate the backup operation of Softek AdvancedCopy Manager using the job creation wizard of SQL Server or SystemWalker/OperationMGR. Automate the backup operation using commands provided by Softek AdvancedCopy Manager Performing backup and restore It explains how to perform backup and restore of the SQL Server database Performing backup The backup of the SQL Server database is composed of the following procedures. Starting synchronous processing (Only if synchronous type backup is employed) Backing up a database Backing up a transaction log +Starting synchronous processing (Only if synchronous type backup is emplo yed) In the case of synchronous type backup, synchronous processing (EC/REC) should start beforehand. Synchronous processing starts by backup synchronous processing starting command (swststartsync). If the database is composed of two or more volumes, synchronous processing for all the database volumes should be executed. <Execution example> Start synchronous processing for all the database volumes. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swststartsync g1d1p1 g1d1p1 swststartsync completed C: >C: Win32App AdvancedCopyManager bin swststartsync g1d2p1 g1d2p1 swststartsync completed C: >C: Win32App AdvancedCopyManager bin swststartsync g1d3p1 g1d3p1 swststartsync completed C: > +Backing up a database Backup of an SQL Server database is performed by the SQL Server backup execution command (swstbackup_sqlsvr). The transaction log is not truncated by snapshot backup. Therefore, execute the log backup for the truncation of the transaction log regularly even when you compose the backup operation only of the database backup. For details, refer to the clause of "Truncating the Transaction Log" of "SQL Server Books Online." If an error occurs while SQL Server backup execution command (swstbackup_sqlsvr) is processing the database of two or more volumes composition with the backup execution command (swstbackup), processing is interrupted at that time and the backup history information on Softek AdvancedCopy Manager may become inconsistent. In order to cancel such an inconsistent state, delete unnecessary history information using a history information deletion command (swsthistdel). Also, for the volumes for which the replication processing has already been completed, after you deal with the error cause, restart synchronous processing by using the backup synchronous processing start command (swststartsync). 103

107 <Execution example> Perform backup of databases DB01, DB02 and DB03. If you employ synchronous type backup, by the backup synchronous processing progress display command (swststartsync), confirm synchronous processing for all database volumes is in equivalency holding state (namely, the Execute column is "100%"). Execute the command from the business server (DB-SVR), where it is assumed that the device map file name is G: SQLADM devmap.txt. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstbackup_sqlsvr -Xserver VSERVER -Xdevmap G: SQLADM devmap.txt DB01 DB02 DB03 DB01 DB02 DB03 swstbackup_sqlsvr completed C: > +Backing up a transaction log Backup the transaction log with Enterprise Manager or Transact-SQL of SQL Server Performing restore The restore of SQL Server database is composed of the following procedures. Backing up a transaction log (Only if the restore to the latest point should performed) Restoring a database Recovering a database (Only if the restore to the latest point or a specific point should be performed) +Backing up a transaction log (Only if the recovery to the latest point shoul d performed) Backup the transaction log if the restore to the latest point should be performed. You cannot perform the restore to the latest point if transaction log has not been backed up or a failure has occurred disabling the log backup. In such cases, use the latest log backup before a failure occurs to perform database recovery. +Restoring a database Restore a database by performing the following two procedures: Restoring files Recreating a database When the default database of the user (login) who does restoration work is set as the database for restoration, before doing the above-mentioned work, it is necessary to change a default database into a master database. The restoration procedure in this case is as follows. : 1. A default database is changed into master from the database for restoration. 2. "Restoring file" work is done. 3. "Recreating a database" work is done. 104

108 4. A default database is changed into the database for restoration from master. A default database can be changed by Enterprise Manager. : 1. Expand a server group, and then expand a server. 2. Expand Security, and then click Logins. 3. In the details pane, right-click the login to modify, and then click Properties. 4. In the Database list, on the General tab, click the new default database to which the login is connected after logging into an instance of SQL Server(The above-mentioned modifying method is indicated by "To change the default database of a login" of "Administering SQL Server"->"Managing Security"->"Managing Security Accounts"->"Modifying Logins" in SQL Server Books Online. +Restoring files Restore all the database files (data and log files). You cannot restore only log files. Restore all the database files as follows: Step Step name Description 1 2 Deleting a database Executing the restore execution command Delete a database using Enterprise Manager. When you apply logs, be careful not to delete the "history of database backup and restore". If you do, you will no longer be able to apply logs from Enterprise Manager. In this case, apply logs by Transact-SQL. Execute the restore execution command (swstrestore) for transaction volumes on which all the database files are placed. A meta data file as well as database files will be restored (to the same folder as the data file with file identification number 1). If you use the operation of further saving the data on a backup volume of Softek AdvancedCopy Manager to a tape unit, you can also directly restore files from the tape unit to the database volumes without using the restore execution command. <Execution example> Restore files by using the restore execution command (swstrestore) after deleting the databases. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstrestore g1d1p1 g1d1p1 swstrestore completed C: >C: Win32App AdvancedCopyManager bin swstrestore g1d2p1 g1d2p1 swstrestore completed C: >C: Win32App AdvancedCopyManager bin swstrestore g1d3p1 g1d3p1 swstrestore completed C: > ++Recreating a database Recreate a database using the SQL Server restore execution command (swstrestore_sqlsvr). You can select one of the following restore methods: Restore to the latest point or a specific point Restore to the backup point <Execution example> Recreate the databases after performing file restore. Because the meta data files are restored to D: SQLSVR DB01.swst-dmp etc., execute the commands specifying these files. C: >C: Win32App AdvancedCopyManager bin swstrestore_sqlsvr -Xserver VSERVER -Xmeta 105

109 D: SQLSVR DB01.swst-dmp DB01 DB01 swstrestore_sqlsvr completed C: >C: Win32App AdvancedCopyManager bin swstrestore_sqlsvr -Xserver VSERVER -Xmeta D: SQLSVR DB02.swst-dmp DB02 DB02 swstrestore_sqlsvr completed C: >C: Win32App AdvancedCopyManager bin swstrestore_sqlsvr -Xserver VSERVER -Xmeta D: SQLSVR DB03.swst-dmp DB03 DB03 swstrestore_sqlsvr completed C: > +Recovering a database (Only if the restore to the latest point or a specific point should be performed) To restore a database to the latest point or a specific point, apply logs using Enterprise Manager. For information on the operation method, see "How to apply a transaction log backup (Enterprise Manager)" of the "SQL Server Books Online". If you cannot apply logs using Enterprise Manager because, for example, the backup history of msdb is lost, apply logs using Transact-SQL. For information on the operation method, see "How to apply a transaction log backup (Transact-SQL)" of the "SQL Server Books Online" Confirming operation status Confirm the copy status by the backup synchronous processing progress display command (swstsyncstat), the backup execution status display command (swstbackstat), and the restore execution status display command (swstreststat). The database backup history information is stored in msdb of SQL Server. You can refer to the latest backup time by selecting "Property" after right-clicking in the target database on the tree screen of Enterprise Manager Stopping operation When the copy processing under execution is stopped, use the backup synchronous processing cancel command (swstcancelsync), the history information deletion command (swsthistdel), and restore cancellation command (swstcancelrest). <Execution example> Stop backup synchronous processing under execution. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstcancelsync g1d1p1 g1d1p1 swstcancelsync completed C: >C: Win32App AdvancedCopyManager bin swstcancelsync g1d2p1 g1d2p1 swsrpcancel completed C: >C: Win32App AdvancedCopyManager bin swstcancelsync g1d3p1 g1d3p1 swstcancelsync completed C: > Operation by MSCS Softek AdvancedCopy Manager supports Microsoft Clustering Service (MSCS). For more information, see the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." About note of Backup operation for SQL Server database, see Chapter 7.3, "Backup Operation", in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." 8.4 Operation by replication management function Preparations Carry out the following preparations before the backup operation of SQL Server 2000 is started. 106

110 Setting the environment for SQL Server Carrying out a general preparation Preparing a device map file Recording the output path of a metadata file Preparing the automated operation of backup The following example is used for explanation in the following sub sections. <Server configuration> Server type Storage management server Storage server Server name MGR-SVR DB-SVR Comment Business server operating on MSCS(AdvancedCopy Manager's logical node name=nodeagt, SQL Server virtual server name=vserver) Storage server BKUP-SVR Backup server <Database configuration> Database name Database file name Database file type DB01 DB02 D: SQLSVR DB01.mdf E: SQLSVR DB01.ndf F: SQLSVR DB01.ldf D: SQLSVR DB02.mdf E: SQLSVR DB02.ndf F: SQLSVR DB02.ldf Primary data file Secondary data file Transaction log file Primary data file Secondary data file Transaction log file DB03 D: SQLSVR DB03.mdf Primary data file 107

111 E: SQLSVR DB03.ndf F: SQLSVR DB03.ldf Secondary data file Transaction log file <Database volume configuration> Drive letter AdvancedCopy Manager device name D: E: F: Setting the environment for SQL Server Set up SQL Server based on the result of database backup operation design. If, in particular, you apply logs at the time of recovering a database, set the "recovery model" of a database to "Full" or "Bulk-Logged". For more information, see "Designing a Backup and Restore Strategy" in the "SQL Server Books Online" Carrying out a general preparation Do the work described in Capter 6.4 "Preparation", noting the following points. Register all the database volumes and register the backup volumes which become copy destinations. Set a database volume and a backup volume to be an original volume and a replica volume, respectively (Do not reverse an original volume and a replica volume). Set the server (original server) which operates the database to be an operation server when you employ the backup server. (Specify "ORG" for the argument of o option in the replication volume information setting command.) Specify u option if you do not use the advanced copy to perform the file restore. The direction of the copy which can be executed can be limited to one direction from the original volume (database volume) to the replica volume (backup volume). <Execution example> Set the replication volume information for all the target database volumes in AdvancedCopy Manager. Execute the command from the business server (DB-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpsetvol -o ORG g1d1p1 g1d11p1@bkup-svr swsrpsetvol completed C: >C: Win32App AdvancedCopyManager bin swsrpsetvol -o ORG g1d2p1 g1d12p1@bkup-svr swsrpsetvol completed C: >C: Win32App AdvancedCopyManager bin swsrpsetvol -o ORG g1d3p1 g1d13p1@bkup-svr swsrpsetvol completed C: > Preparing a device map file Create a file (device map file) which describes the relation between database volumes and backup volumes, which is used by the SQL Server backup execution command. The SQL Server backup execution command copies data onto the backup volumes specified for a device map file. Place a device map file on an arbitrary place of the server which operates the database (original server). The backup destination of the database volume is decided by specifying this file when backup is performed. +Describing a device map file The following shows a description example of a device map file. Description example of a device map file 108

112 The following lists rules for creating a device map file. Describe a database volume and a corresponding target backup volume in one line. Separate a database volume and a backup volume with one or more "half-size blank or tab characters". One or more "half-size blank or tab characters" may be included between the beginning of a line and a database volume name or between the end of a backup volume name and the end of a line (newline character). Specify the backup volume of a backup server in the form of "volume name@server name". Only the form of "volume name" can be used about the database volume. Also, it should be noted that the form of "volume name@database server name" cannot be used. A blank line ("half-size blank or tab characters") may be included in a file. The portion from the symbol "#" to the end of a line is assumed as a comment. You cannot specify more than one target backup volumes for one database volume in one device map file. In such a case, the information in the line first found will be valid. While a device map file is read, the system will not detect such a redundant line. Prepare two or more device map files if you perform the plural generation backup. A device map file may include descriptions of database volumes other than the processing target database. (See the description example provided in the beginning of this chapter.) Describe all the database volumes for the database of the multivolume composition in one device map file. (The description shall not be extending over plural files.) Make the character-code system when the device map file is preserved SJIS Recording the output path of a metadata file At the time of backup execution, the "metadata" which includes information, such as path name, size and file type, etc. of the database files of the database for backup is outputted from SQL Server Softek AdvancedCopy Manager saves a metadata file in a backup volume. A metadata file is restored to a database volume at the time of restore of database files. Since it becomes indispensable when executing SQL Server restore execution command (swsrprestore_sql), it needs to record the absolute path of a metadata file in advance. The metadata file is saved by the name of ""DB name".swsrp-dmp" at the folder where the database file with file identification number (FILE_ID) 1 exists. For example, supposing that the absolute path of the database file with file identification number 1 of a database DB01 is "D: SQLSVR DB01_data.mdf", the absolute path of a metadata file will serve as "D: SQLSVR DB01.swsrp-dmp." Usually, although the database file with file identification number 1 is a primary data file, check it in the following procedure by way of precaution. 1. Perform Transact-SQL "USE database name EXEC SP_HELPFILE". 2. Look for the record with which the column "file id" is 1 from an execution result. The content of the column "filename" of the record is the absolute path of the database file with file identification number 1. Although it is strictly required to secure the capacity for saving a metadata file in operating volume, since the size of a metadata file is small, there is almost no necessity for consideration. (The size of a metadata file depends on the number of files of a database. For example, it is about 20KB in the database of 10 files composition.) Preparing the automated operation of backup You can automate the backup operation of Softek AdvancedCopy Manager using the job creation wizard of SQL Server or SystemWalker/OperationMGR. Automate the backup operation using commands provided by Softek AdvancedCopy Manager. 109

113 8.4.2 Performing backup and restore It explains how to perform backup and restore of the SQL Server database Performing backup The backup of the SQL Server database is composed of the following procedures. Starting or resuming synchronous processing (Only if synchronous type backup is employed) Backing up a database Backing up transaction log +Starting or resuming synchronous processing (Only if synchronous type bac kup is employed) In the case of synchronous type backup, synchronous processing (EC/REC) should start or resume beforehand. Synchronous processing starts by backup synchronous processing starting command (swsrpstartsync). If the database is composed of two or more volumes, synchronous processing for all the database volumes should be executed. <Execution example> Start or resume synchronous processing for all the database volumes. Execute the command from the business server (DB-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpstartsync g1d1p1 g1d11p1@bkup-svr FROM=g1d1p1@DB-SVR,TO=g1d11p1@BKUP-SVR swsrpstartsync completed C: >C: Win32App AdvancedCopyManager bin swsrpstartsync g1d2p1 g1d12p1@bkup-svr FROM=g1d2p1@DB-SVR,TO=g1d12p1@BKUP-SVR swsrpstartsync completed C: >C: Win32App AdvancedCopyManager bin swsrpstartsync g1d3p1 g1d13p1@bkup-svr FROM=g1d3p1@DB-SVR,TO=g1d13p1@BKUP-SVR swsrpstartsync completed C: > +Backing up a database Backup of an SQL Server database is performed by the SQL Server backup execution command (swsrpbackup_sql). The transaction log is not truncated by snapshot backup. Therefore, execute the log backup for the truncation of the transaction log regularly even when you compose the backup operation only of the data base backup. For details, refer to the clause of "Truncating the Transaction Log" of "SQL Server Books Online." If an error occurs while SQL Server backup execution command (swsrpbackup_sql) is processing the database of two or more volumes composition with the replication creation command (swsrpmake), processing is interrupted at that time. For the volumes for which the replication processing has already been completed, after you deal with the error cause, restart synchronous processing by using the synchronous processing start command (swsrpstartsync). <Execution example> Perform backup of databases DB01, DB02 and DB03. If you employ synchronous type backup, by the operation status display command (swsrpstat), confirm synchronous processing for all database volumes is in equivalency holding state (namely, the Execute column is "100%"). Execute the command from the business server (DB-SVR), where it is assumed that the device map file name is G: SQLADM devmap.txt. C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpbackup_sql -Xserver VSERVER -Xdevmap G: SQLADM devmap.txt DB01 DB02 DB03 DB01 DB02 DB03 swsrpbackup_sql completed C: > 110

114 +Backing up transaction log Backup the transaction log with Enterprise Manager or Transact-SQL of SQL Server Performing restore The restore of the SQL Server database is composed of the following procedures. Backing up transaction log (Only if the restore to the latest point should performed) Restoring a database Recovering a database (Only if the restore to the latest point or a specific point should be performed) +Backing up a transaction log (Only if the recovery to the latest point shoul d performed) Backup the transaction log if the restore to the latest point should be performed. You cannot perform the restore to the latest point if transaction log has not been backed up or a failure has occurred disabling the log backup. In such cases, use the latest log backup before a failure occurs to perform database recovery. +Restoring a database Restore a database by performing the following two procedures: Restoring files Recreating a database When the default database of the user (login) who does restoration work is set as the database for restoration, before doing the above-mentioned work, it is necessary to change a default database into a master database. The restoration procedure in this case is as follows. : 1. A default database is changed into master from the database for restoration. 2. "Restoring file" work is done. 3. "Recreating a database" work is done. 4. A default database is changed into the database for restoration from master. A default database can be changed by Enterprise Manager. : 1. Expand a server group, and then expand a server. 2. Expand Security, and then click Logins. 3. In the details pane, right-click the login to modify, and then click Properties. 4. In the Database list, on the General tab, click the new default database to which the login is connected after logging into an instance of SQL Server(The above-mentioned modifying method is indicated by "To change the default database of a login" of "Administering SQL Server"->"Managing Security"->"Managing Security Accounts"->"Modifying Logins" in SQL Server Books Online. +Restoring files Restore all the database files (data and log files). You cannot restore only log files. Restore all the database files as follows: Step Step name Description 1 2 Deleting a database Executing the replication creation command Delete a database using Enterprise Manager. When you apply logs, be careful not to delete the "history of database backup and restore". If you do, you will no longer be able to apply logs from Enterprise Manager. In this case, apply logs by Transact-SQL. Executing the replication creation command (swsrpmake), copy all the database files from the backup volumes to the database volumes. 111

115 A meta data file as well as database files will be restored (to the same folder as the data file with file identification number 1). If you use the operation of further saving the data on a backup volume of Softek AdvancedCopy Manager to a tape unit, you can also directly restore files from the tape unit to the database volumes without using the replication creation command. <Execution example> Restore files by using the snapshot type replication (OPC) after deleting the databases. Execute the command from the business server (DB-SVR). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpmake g1d11p1@bkup-svr g1d1p1 FROM=g1d11p1@BKUP-SVR,TO=g1d1p1@DB-SVR swsrpmake completed C: >C: Win32App AdvancedCopyManager bin swsrpmake g1d12p1@bkup-svr g1d2p1 FROM=g1d12p1@BKUP-SVR,TO=g1d2p1@DB-SVR swsrpmake completed C: >C: Win32App AdvancedCopyManager bin swsrpmake g1d13p1@bkup-svr g1d3p1 FROM=g1d13p1@BKUP-SVR,TO=g1d3p1@DB-SVR swsrpmake completed C: > ++Recreating a database Recreate a database using the SQL Server restore execution command (swsrprestore_sql). You can select one of the following restore methods: Restore to the latest point or a specific point Restore to the backup point <Execution example> Recreate the databases after performing file restore. Because the meta data files are restored to D: SQLSVR DB01.swsrp-dmp etc., execute the commands specifying these files from the business server (DB-SVR). C: >C: Win32App AdvancedCopyManager bin swsrprestore_sql -Xserver VSERVER -Xmeta D: SQLSVR DB01.swsrp-dmp DB01 DB01 swsrprestore_sql completed C: >C: Win32App AdvancedCopyManager bin swsrprestore_sql -Xserver VSERVER -Xmeta D: SQLSVR DB02.swsrp-dmp DB02 DB02 swsrprestore_sql completed C: >C: Win32App AdvancedCopyManager bin swsrprestore_sql -Xserver VSERVER -Xmeta D: SQLSVR DB03.swsrp-dmp DB03 DB03 swsrprestore_sql completed C: > +Recovering a database (Only if the restore to the latest point or a specific point should be performed) To restore a database to the latest point or a specific point, apply logs using Enterprise Manager. For information on the operation method, see "How to apply a transaction log backup (Enterprise Manager)" of the "SQL Server Books Online". If you cannot apply logs using Enterprise Manager because, for example, the backup history of msdb is lost, apply logs using Transact-SQL. For information on the operation method, see "How to apply a transaction log backup (Transact-SQL)" of the "SQL Server Books Online" Confirming operation status Confirm the copy status by the operation status display command (swsrpstat). The database backup history information is stored in msdb of SQL Server. You can refer to the latest backup time by selecting "Property" after right-clicking in the target database on the tree screen of Enterprise Manager. 112

116 Stopping operation When the copy processing under execution is stopped, use the replication cancellation command (swsrpcancel). <Execution example> Stop backup synchronous processing under execution. Execute the command from the business server(db-svr). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpcancel g1d1p1 swsrpcancel completed C: >C: Win32App AdvancedCopyManager bin swsrpcancel g1d2p1 swsrpcancel completed C: >C: Win32App AdvancedCopyManager bin swsrpcancel g1d3p1 swsrpcancel completed C: > Operation by MSCS Softek AdvancedCopy Manager supports Microsoft Clustering Service (MSCS). For more information, see the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." About note of Replication operation for SQL Server database, see Chapter 7.4, "Replication Operation", in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment MSCS." 113

117 114

118 Chapter 9 Operation Maintenance This chapter describes maintaining a database, performing troubleshooting, and changing the operation information. 9.1 Maintaining a Database Softek AdvancedCopy Manager holds various repositories and management information as employment information. They are named generically and it is called a database in this chapter. A database is important information. You are recommended to periodically back up a periodical database, when the capacity of repositories becomes insufficient by long-time running and employment changed from the first time plan, in preparation for the unexpected accident. (It differs from the database used for the transaction of the database of ORACLE etc.) The following table lists instances when the acquisition timing is needed. Server type Type Acquisition timing and method Storage server Storage server Storage management server Storage management server Storage management sever/storage server Backup management list Replication management list Database Authentication management list Registry After backup is completed Backing up a backup management list and a recovery control file After replication is completed Backing up a replication management list When configuration information is changed due to, for example, addition of a storage server or fetching of device information, or when operation information for backup management or replication management is changed Saving a database After authentication is set Shell script for outputting definition information When a storage server is added or the server information (server name, IP address, or port number) on the storage management server is changed Backing up a registry Maintaining a backup a management list This chapter describes maintenance of a backup management list. A backup management list is maintained on the server that performs the backup operation Backing up a backup management list and a recovery control file A backup management list is backed up. For details, please refer to chapter , "Resource backup command (swstresback)." Restoring a backup management list and recovery control file A backup management list is restored. For details, please refer to chapter , "Resource restore command (swstresrst)." Saving of device information used by backup management To perform the backup operation by using the synchronous high-speed backup, it is necessary to save device information used by the backup management. Save device information as follows: 1. Confirm the backup synchronous processing is not begun. Use "Transaction volume list view" or chapter "Backup synchronous processing progress display command (swststartsync)" to confirm the state of the backup synchronous processing. 2. Confirm the replication synchronous processing is not begun when the replication management is performed. Use chapter "Execution status display command (swsrpstat)" to confirm the state of the replication 115

119 synchronous processing. 3. To make device information, do "Fetching device information on a storage server". 4. Save the device information used by the backup management. Execute the following command to save the device information. C: >program-directory bin swstcmdmbak.exe When the AdvancedCopy Manager server work is in the cluster environment, save device information as follows: Do this operation without setting environment variable SWSTGNODE. 1. Confirm the backup synchronous processing is not begun. Use "Transaction volume list view" or chapter "Backup synchronous processing progress display command (swststartsync)" to confirm the state of the backup synchronous processing. 2. Confirm the replication synchronous processing is not begun when the replication management is performed. Use chapter "Execution status display command (swsrpstat)" to confirm the state of the replication synchronous processing. 3. Save the device information used by the backup management. Execute the following command to save the device information. C: >program-directory bin clset_repdevice.exe Logical-Node-Name Recovering of device information used by backup management If the system was rebooted or the AdvancedCopy Manager service was restarted while synchronous processing, device information used with the backup management might become abnormal. In this case, recover device information as follows: When the AdvancedCopy Manager server work is in the cluster environment, do this operation after environment variable SWSTGNODE is set. 1. Recover the device information used by backup management. Execute the following command to recover the device information. C: >program-directory bin swstcmdmrst.exe 2. Confirm the backup synchronous processing status. Use "Transaction volume list view" or chapter "Backup synchronous processing progress display command (swststartsync)" to confirm the state of the backup synchronous processing. 3. Confirm the replication synchronous processing status when the replication management is performed. Use chapter "Execution status display command (swsrpstat)" to confirm the state of the replication synchronous processing Maintaining a replication management list This chapter describes maintenance of a replication management list Backing up a replication management list To back up a replication management list, back up the repository of the storage management server. For information about backing up a repository, see chapter , "Saving a database." Operation information for replication management is saved in a repository. It is recommended that a replication management list be backed up when operation information for replication management is changed with the replication volume information setting command (swsrpsetvol) or the replication volume information deletion command (swsrpdelvol) Restoring a replication management list Take the following steps to restore a replication management list. 1. Restore the repository on the storage management server. For information about restoring a repository, see chapter , "Recovering a database." 2. On the storage server, execute the resource adjustment command (swsrprecoverres) with the r option specified. For details of the resource adjustment command, see chapter ,"Resource adjustment command." When step 1 above is performed, operation information for replication management of a repository is copied to 116

120 a storage server, where it is available for use. When the operation information for replication management in the repository does not need to be changed and only the operation information for replication management on the storage server is incorrect for some reason, perform only step Saving of device information used by replication management To perform the replication operation by using the synchronous replication, it is necessary to save device information used by the replication management. Save device information as follows: 1. Confirm the replication synchronous processing is not begun. Use chapter "Execution status display command (swsrpstat)" to confirm the state of the replication synchronous processing. 2. Confirm the backup synchronous processing is not begun when the backup management is performed. Use "Transaction volume list view" or chapter "Backup synchronous processing progress display command (swststartsync)" to confirm the state of the backup synchronous processing. 3. To make device information, do "Fetching device information on a storage server". 4. Save the device information used by the replication management. Execute the following command to save the device information. C: >program-directory bin swsrpcmdmbak.exe When the AdvancedCopy Manager server work is in the cluster environment, save device information as follows: Do this operation without setting environment variable SWSTGNODE. 1. Confirm the replication synchronous processing is not begun. Use chapter "Execution status display command (swsrpstat)" to confirm the state of the replication synchronous processing. 2. Confirm the backup synchronous processing is not begun when the backup management is performed. Use "Transaction volume list view" or chapter "Backup synchronous processing progress display command (swststartsync)" to confirm the state of the backup synchronous processing. 3. Save the device information used by the replication management. Execute the following command to save the device information. C: >program-directory bin clset_repdevice.exe Logical-Node-Name Recovering of device information used by replication management If the system was rebooted or the AdvancedCopy Manager service was restarted while synchronous processing, device information used with the replication management might become abnormal. In this case, recover device information as follows: When the AdvancedCopy Manager server work is in the cluster environment, do this operation after environment variable SWSTGNODE is set. 1. Recover the device information used by replication management. Execute the following command to recover the device information. C: >program-directory bin swsrpcmdmrst.exe 2. Confirm the replication synchronous processing status. Use chapter "Execution status display command (swsrpstat)" to confirm the state of the replication synchronous processing. 3. Confirm the backup synchronous processing status when the backup management is performed. Use "Transaction volume list view" or chapter "Backup synchronous processing progress display command (swststartsync)" to confirm the state of the backup synchronous processing Maintaining a database This chapter describes maintaining a database used by a storage management server Saving a database Save a database as follows: 1. Click the Start button and select [Programs]/[ Softek AdvancedCopy Manager]/[DB Setup]. 2. The following window will be output. Click the [DB maintenance] button. 117

121 3. The following DB maintenance window will be output. Click the [DB save] button. 4. The save directory specification window will be displayed. To specify a save directory, enter the directory name and click the [OK] button. To overwrite an already saved directory, mark the [Overwrite if there is any previous save data in the save directory] checkbox. 5. The DB save processing confirmation window will be output. Check that the entered information is correct and click the [Start] button. 6. When the DB save is completed, the following completion window will be output. Click the [Close] button. 118

122 Use this save method only when configuration information is changed due to an addition of a storage server or fetching of device information. You are recommended to periodically save a database, for example, once a day. To prepare for an input-output error in an external file while save data is being acquired, you are recommended to keep at least two generations of save data Finding an error in a database You need to recover a database if an input-output error occurs in the database space. To recover a database depends on where in the database the error occurred. Finding where an error in a database occurred follow the steps below: 1. Click the Start button and select [Programs]/[Administrator Tool (Common)]/[Event Viewer]. 2. Display the event viewer window and select [Log]/[Application]. 3. The application log window will be displayed. Out of the records whose source name is displayed as "SymfoWARE", double-click the record that encountered the error. This will display the detailed window. 4. On the detailed window, find a qdgxxxxx error message. Table 9.1 shows the "recovery modes" corresponding to error messages. A "recovery mode" is information required to recover a database. For more information, see chapter , "Recovering a database". [Table 9.1 Relationship between qdg messages and recovery modes] qdg message Error description Check Recovery mode qdg13039u Input-output error, destruction detected qdg03400u qdg03401u Rollback disabled Repository data space DSI (FW mode) qdg12079e File deleted qdg03121u Input-output error qdg03420u qdg12078u Input-output error, destruction detected, etc. File deleted DB dictionary file RDB dictionary (FW mode) qdg12150u qdg12151u File open error qdg12251e qdg12443u qdg12434u Input-output error File error DB dictionary file Log management file qdg02290u File deleted qdg12111u Input-output error DB log file Temporary log file qdg12440u 119

123 qdg12441u qdg12442u qdg02299u File deleted qdg03815u qdg12275w qdg12250u System call error Destruction detected DB log file Archive log file qdg12483u File read error If multiple errors occur at the same time, recovery may not be made using one of the recovery modes shown above. In such a case, re-create a database and then use the recovery mode "RDB dictionary, DSI (LOAD mode)". This way, you can make recovery up to the point when data has been saved. (Data reflected after saving cannot be restored). At this point, execute the resource matcha command (see chapter , "Resource match command") with option -x on all the storage servers on which the backup operation is performed. Moreover, execute the resource adjustment command (see chapter , "Resource adjustment command") with option -r on all the storage servers on which the replication operation is performed Recovering a database If an input-output error or any other error occurs in the database space, make recovery as follows: 1. Click the Start button and select [Programs]/[ Softek AdvancedCopy Manager]/[DB Setup]. 2. The following window will be output. Click the [DB maintenance] button. 3. The following DB maintenance window will be output. Click the [DB recovery] button. 4. The recover mode selection window will be output. Select a recovery mode and click the [OK] button. For information on deciding a recovery method, see chapter , "Finding an error in a database". 120

124 5. The window for entering a save data storage directory will be output. Specify a directory in which save data has been stored and click the [OK] button. 6. The DB recovery processing confirmation window will be output. Check that the entered information is correct and click the [Start] button. 7. When the DB recovery process is completed, the following completion window will be output. Click the [Close] button. 121

125 8. When the DB recovery process is completed, save the database. You are recommended to save the database at a different location than the previous time. For information on the save methods, see chapter , "Saving a database". 9. Restart all the services of Softek AdvancedCopy Manager on the storage management server. For information on stopping and starting a service, see chapter 2, "Starting and Stopping a Service" Maintaining authentication management list This chapter describes maintenance of the authentication feature. Execute the command on the server (storage server) where the authentication feature is implemented Backing up an authentication management list In a Storage management server, a program directory bin smmkbat command is executed and attestation management information is extracted. It is necessary to perform this command by the Administrators authority user. 1. It moves to program directory bin. 2. The smmkbat command is executed. smmkbat -f Definition information output batch file Example: smmkbat-f acldata.bat A definition information output batch file is extracted as a batch file which described the command sequence reflecting definition information Restoring an authentication management list A definition information output batch file is performed. In this case, it is necessary to carry out by the Administrators authority user. 1. It moves to program directory bin. 2. A definition information output batch file is performed Maintaining a registry This chapter describes maintaining a registry. Perform this procedure on a storage management server or a storage server Backing up a registry On the DOS prompt window, back up the following files using the copy command, etc. a. File names In the case of a non-cluster environment-settings-directory etc swnode.ini environment-settings-directory etc device.ini In the case of a cluster The drive letter of the shared disk for AdvancedCopy Manager share data: etc opt swstorage etc swnode.ini The drive letter of the shared disk for AdvancedCopy Manager share data: etc opt swstorage etc device.ini b. Example Back up the registry to the backup directory on drive D. This example assumes that AdvancedCopy Manager has been installed at C: Win32app. C: >copy C: Win32app AdvancedCopyManager etc swnode.ini D: backup 122

126 C: >copy C: Win32app AdvancedCopyManager etc device.ini D: backup Restoring a registry On the DOS prompt window, use the copy command or other method to restore the following files. a. File names In the case of a non-cluster environment-settings-directory etc swnode.ini environment-settings-directory etc device.ini ExampleIn the case of a cluster The drive letter of the shared disk for AdvancedCopy Manager share data: etc opt swstorage etc swnode.ini The drive letter of the shared disk for AdvancedCopy Manager share data: etc opt swstorage etc device.ini b. Example Restore files saved to the /backup directory of D drive. C: >copy D: backup swnode.ini C: Win32app AdvancedCopyManager etc C: >copy D: backup device.ini C: Win32app AdvancedCopyManager etc 9.2 Troubleshooting Troubleshooting for insufficient free space in a repository This chapter describes what to do if there is insufficient free space in a repository used by a storage management server. Perform this procedure on a storage management server. You can use this troubleshooting method when there is insufficient free space in a repository and if the operation status is significantly different from the initial installation time to prevent the occurrence of insufficient free space in the repository. Extend the repository space as follows: 1. Backup of the registry of a Storage management server (See chapter , "backing up a registry") 2. Stored data save processing (see chapter , "Database backup") 3. Database unsetup (see chapter , "Database unsetup") 4. Re-estimating the database size (see chapter 2.1.4, "Estimating the database space" in the "Softek AdvancedCopy Manager User's Guide") 5. Database setup (see chapter , "Database setup") 6. Service Starting of "SymfoWARE RDA RDBSWSTF" of Service Display Name, and "SymfoWARE RDB RDBSWSTF" (See Chapter 2 "Starting and Stop of Service) 7. Save data restore processing (see chapter , "Database restoration") 8. Restoration of the registry of a Storage management server (See chapter , "Restoring a registry") Database backup This chapter describes backing up a database. You can save data stored in a database to the specified directory collectively. This method is mainly used for converting data. To save normal operation data, use the method described in chapter , "Saving a database." A directory in which data will be saved must be created in advance. Back up a database as follows: 1. Click the Start button and select [Programs]/[ Softek AdvancedCopy Manager]/[DB setup]. 2. The following DB setup initial window will be displayed. Click the [DB maintenance] button. 123

127 3. The following DB maintenance window will be output. Click the [DB backup] button. 4. The following window for entering a backup directory will be output. Enter a data storage directory and click the [OK] button. 5. The following window will be output. Check that the displayed information is correct and click the [Start] button. 6. When the backup is completed, the following window will be output. Click [Close]. 124

128 Database restoration This chapter describes restoring a database. You can restore data that has been saved as described in chapter , "Database backup" to a database collectively as shown below. Data currently stored in a database will be lost in this processing because it will be overwritten by save data. When the database restoration is normally completed, the database is saved. For more information see chapter , "Saving a database". Restore a database as follows: 1. Click the Start button and select [Programs]/[ Softek AdvancedCopy Manager]/[DB Setup]. 2. The following DB setup initial window will be displayed. Click the [DB maintenance] button. 3. The following DB maintenance window will be output. Click the [DB restore] button. 4. The following window for specifying a backup data storage directory will be output. Specify a directory in which backup data has been stored and click the [OK] button. 125

129 5. The following window will be output. Check that the displayed information is correct and click the [Start] button. 6. When the restoration is completed, the following completion window will be output. Click [Close] Database setup This chapter describes setting up a database. 1. Click the Start button and select [Programs]/[ Softek AdvancedCopy Manager]/[DB Setup]. 2. The following window will be output. Click the [DB setup] button. 3. The following window will be output. Enter necessary items and click the [Continue] button. 126

130 4. The following window will be output. Enter necessary items and click the [Setting] button. 5. The following window will be displayed. Check the displayed information and click the [Start] button. 127

131 6. When the database setup is completed, the following window will be output. Click the [Close] button Database unsetup Remove the setup of a database as follows: 1. Click the Start button and select [Programs]/[ Softek AdvancedCopy Manager]/[DB setup]. 2. The following DB setup initial window will be displayed. Click the [DB unsetup] button. 3. The following confirmation window will be displayed. Click the [Start] button. 128

132 4. When the unsetup is completed, the following completion window will be output. Click [Close] Collecting maintenance information Collecting information using a Web window Collect information as follows: 1. Start the Java Plug-in control panel. Start the Java Plug-in control panel as follows: Select [Settings] - [Control Panel] - [Java Plug-in]. 2. Make the startup settings of the Java console. On the Java control panel, access the [Basics] tag, mark the [Display Java Console] check box, click the [Apply] button, and exit the Java Plug-in control panel. 3. Start the Web window of Softek AdvancedCopy Manager. 4. The Java console will be started and a message will be output. Copy and paste the message on a NotePad window, save it to a file, and attach the file to your report Collecting error survey information Log into the storage management server and the storage server. Collect the following information. 1. When an error occurs during backup management Type Storage management server Storage server Event log Must be collected. Must be collected. Trace log Backup management list Acquire the files under the following directory: work-directory var Need not be collected. Acquire the files under the following directory: work-directory var trc Acquire the files of the following directory: <environment setting directory> etc backup data When cluster operation is performed, collect the files of the following directory: 2. When an error occurs during replication management Type Storage management server <Shared disk>: etc opt swstorage etc backup data Storage server 129

133 Event log Must be acquired. Must be acquired. Trace log Replication management list Get the files under the following directory: work-directory var trc Replication management list Get the files under the following directory: work-directory var trc Acquire the files of the following directory: <environment setting directory> etc repl data When cluster operation is performed, collect the files of the following directory: <Shared disk>: etc opt swstorage etc repl data Troubleshooting for a failure in access to a repository database This chapter describes finding a cause for a failure in access to a repository database and what to do in such a case. Perform this procedure on the storage management server. 1. Check that the following repository access services are running. - SymfoWARE RDA RDBSWSTF - SymfoWARE RDB RDBSWSTF [Check method] Select [Control Panel] and then [Services] to display the service window. On the service window, check that the above two services are in the "Started" status. [Required action] If any of the repository access services are stopped, select the service on the service window and click the [Start] button. For more information, see Chapter 2, "Starting and Stopping a Service". 2. Check that there is sufficient free space as required to update a repository database. [Check method] Execute the following command to check the usage ratio of space required to update a repository. C: >program-directory bin stgdbloginf.exe [Required action] If the usage ratio is 100%, save the database space according to "Saving a database". (Consequently, there will be sufficient free space required to update a repository.) After saving a database, restart (stop and then start) the repository access services. For information on stopping and starting a service, see Chapter 2, "Starting and Stopping a Service". Then, perform this step again. 3. Check whether the Saving a database processing is in progress. [Check method] Log into the storage management server and check whether the database save window is up. If it is, check whether the database save processing is in progress. [Required action] If the database save processing is in progress, wait until it is completed. Then, perform this step again. 4. It checks whether the capacity of ripository is insufficient. [Check method] 1. [Program] -> [management tool (common)] -> [an event viewer] is chosen from a start button. 2. Since an event viewer screen is displayed, [log] -> [application] is chosen. 3. Since an application log screen is displayed, the record which serves as an error among the records currently displayed on the sauce name as "SymfoWARE" is double-clicked, and a detailed screen is displayed. 4. The error message of qdgxxxxx is found on a detailed screen. It checks whether "JYP5019E" or "JYP5045E" exists in an error message. [Required action] When you exist, please extend ripository capacity with reference to chapter 9.2.1"Troubleshooting for insufficient free space in a repository" of this manual. Then, please re-perform processing. 5. Check whether an input-output error or any other error has occurred in the database space. [Check method] Check whether an error exists according to chapter , "Finding an error in a database". [Required action] Recover a database according to chapter , "Recovering a database". After making recovery, perform this step again. 6. Collect survey information according to chapter 9.2.2, "Collecting maintenance information". Then, contact your Fujitsu system engineer (SE). 130

134 9.3 Troubleshooting for a hardware error, etc. occurring d uring backup This chapter describes what to do for a hardware error, etc. occurring during a backup using Softek AdvancedCopy Manager Overview If a hardware error occurs during backup operation, the following symptoms are generated: The backup execution status display command (swstbackstat) displays "failed" in the Status column. The synchronous backup operation status display command (swstsyncstat) displays "failed" in the Status column. The restoration execution status display command (swstreststat) displays "failed" in the Status column. The history information display command (swsthistdisp) displays "failed" in the Status column. Code swst0634, swst0719, or swst0902 is displayed during command execution. If the execution status display command and history information display command display "failed" in the Status column, a hardware error has occurred during physical copying, and the copy processing has failed. If swst0634, swst0719, or swst0902 is output during command execution and the same error occurs even if the command is re-executed, a hardware error has occurred, causing AdvancedCopy to fail. If a hardware error occurs during remote copying, the following symptoms may be generated: The backup execution status display command (swstbackstat) displays "halt" in the Status column. The synchronous backup operation status display command (swstsyncstat) displays "halt" in the Status column. The restoration execution status display command (swstreststat) displays "halt" in the Status column. The history information display command (swsthistdisp) displays "halt" in the Status column. If the execution status display command and history information display command display "halt" in the Status column, a hardware error has occurred during physical copying, and the remote copy processing has failed. If these symptoms are generated, a hardware error may have occurred in the transaction volume or backup volume. Check the hardware status, and if a hardware error is found, remove the cause of the error, and re-execute the processing Troubleshooting Troubleshooting for a hardware error, etc. on a transaction volume When a hardware obstacle occurs in operating volume, please perform the repair work of an obstacle according to the following procedures. 1. If an error occurred during physical copying, cancel the the processing in which the error occurred. - If an error occurred during backup (OPC) physical copy: swsthistdel command - If an error occurred during synchronous processing (EC): swstcancelsync command - If an error occurred during restore (OPC) physical copy: swstcancelrest command 2. Execute the execution status display commands (swstbackstat,swstsyncstat,swstreststat), and history information display command (swsthistdisp) to verify that no other errors are found. 3. Remove the hardware error of the transaction volume. 4. Execute the restoration execution command (swstrestore) to restore the transaction volume Troubleshooting for a hardware error, etc. on a backup volume When a hardware obstacle occurs in backup volume, please perform repair work, such as an obstacle, according to the following procedures. 1. Cancel the processing in which the error occurred. - If an error occurred during backup (OPC) physical copy: swsthistdel command - If an error occurred during synchronous processing (EC): swstcancelsync command - If an error occurred during restoration (OPC) physical copy: swstcancelrest command 2. If the processing cannot be canceled by using the command, use GRmgr to cancel it. 3. Execute resource match command (swstsrsemtch) 4. Cancel the processing in which the error occurred. At this point, the execution status display commands (swstbackstat, swstreststat) and history information display command (swsthistdisp) display "succeeded" in the Status column. However, because the copy processing is suspended, be sure to cancel the commands. If an error occurred in the synchronous processing (EC), the command has already been canceled, so no response is required. - If an error occurred during backup (OPC) physical copy: swsthistdel command 131

135 - If an error occurred during restoration (OPC) physical copy: swstcancelrest command 5. Execute the execution status display commands (swstbackstat,swstsyncstat,swstreststat) and history information display command (swsthistdisp) to verify that no other errors are found. 6. Use the device information setting command (swstdevinfoset) to delete the backup volume in which the error occurred. 7. Use the device information setting command (swstdevinfoset) to register a new backup volume. If the backup volume in which the error occurred is repaired and reused, execute [Collect or reflect the information for a specific device] from the initial window and store the information again in the backup volume. 8. Re-execute the processing in which the error occurred Troubleshooting for an error (halt) on a remote copy processing 1. Remove the hardware error. 2. The suspended copy processing is re-executed. 9.4 Troubleshooting for a Hardware Error or Other Error Occurring during Replication This chapter describes the corrective action for a hardware or other error occurring during Softek AdvancedCopy Manager replication Overview If a hardware error occurs during replication operation, the following symptoms are generated: The operation status display command (swsrpstat) displays "failed" or "?????"in the Status column. Code swsrp2606 is output during command execution. Code swsrp0634k swsrp0719, or swsrp0902 is output during command execution. If the operation status display command displays "failed" in the Status column, and swsrp2606 is output during command execution, a hardware error has occurred during physical copying, and the copy processing has failed. If swsrp0634, swsrp0719, or swsrp0902 is output during command execution, and the same error occurs even if the command is re-executed, a hardware error has occurred, causing AdvancedCopy to fail. If a hardware error occurs during remote copying, the following symptoms may be generated: The operation status display command (swsrpstat) displays "halt" in the Status column. Code swsrp2648 is output during command execution. If the operation status display command displays "halt" in the Status column, and swsrp2648 is output during command execution, a hardware error has occurred during physical copying, and the remote copy processing has failed. If these symptoms are generated, a hardware error may have occurred in the original or replica volume. Check the hardware status, and if a hardware error is found, remove the cause of the error and re-execute the command Troubleshooting Troubleshooting for a hardware error on a replication volume When a hardware obstacle occurs in duplicate volume, please perform the repair work of an obstacle according to the following procedures. 1. Use the operation cancel command (swsrpcancel) to cancel the processing in which the error occurred. If the processing cannot be canceled from the operator server when interserver replication is performed, cancel it from a nonoperator server. 2. If the processing cannot be canceled by using the command, use GRmgr to cancel it. 3. Execute the resource adjustment command (swsrprecoverres) 4. Execute the operation status display command (swsrpstat) to verify that no other errors are found. 5. Use the replication volume information deletion command (swsrpdelvol) to delete the replication volume in which the error occurred. 6. Use the replication volume information setting command (swsrpsetvol) to register a new replication volume. If the replication volume in which the error occurred is repaired and reused, execute [Collect or reflect the information for a specific device] from the initial window and store the information again in the replication volume. 7. Re-execute the processing in which the error occurred Troubleshooting for an error (halt) on a remote copy processing 1. Remove the hardware error. 2. The suspended copy processing is reexecuted. 132

136 9.5 Changing the Operating Environment Changing the IP address of a storage management server Change the IP address of a storage management server as follows: 1. It checks whether the Storage management server for change serves as the Storage server. When serving and you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to Chapter "Deleting an original volume or replica volume" in the Softek AdvancedCopy Manager Operator's Guide. 2. On the storage management server, change the system IP address. 3. On the storage management server, execute the server information change command. For more information on the server information change command, see chapter , "Management server information change command (stgcmmodnode)". 4. On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see chapter , "Management server information change command (stgcmmodnode)". 5. On the storage management server, restart the services of Softek AdvancedCopy Manager. For information on restarting a service, see Chapter 2, "Starting and Stopping a Service". About change by cluster operation, see "Changing the IP address of a storage management server transaction," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Changing the IP address of a storage server Change the IP address of a storage server as follows: For more information on the Web window, see Chapter , "Changing the IP address of a storage server" of the "Softek AdvancedCopy Manager User's Guide". 1. When you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to Chapter "Deleting an original volume or replica volume" in the Softek AdvancedCopy Manager Operator's Guide. 2. On a target storage server, stop services of Softek AdvancedCopy Manager. For more information on stopping a service, see Chapter 2, "Starting and Stopping a Service". 3. On the storage server, change the system IP address. 4. On the storage server, start services of Softek AdvancedCopy Manager. For more information on starting a service, see Chapter 2, "Starting and Stopping a Service". Later, follow steps 5 and 6 if the address is changed by using the Web screen, and follow step 7 if the address is changed by using a command. 5. On the server list view on the initial window of Softek AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window. 6. On the [Change of server] window, change the IP address and click the [OK] button. 7. Change the IP address by using the server information change command on the Web server. Refer to Chapter " Server information change command(stgxfwcmmodsrv)" About change by cluster operation, see "Changing the IP address of a storage server transaction," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Changing the port number of a storage management server Change the port number of a storage management server as follows: 1. It checks whether the Storage management server for change serves as the Storage server. When serving and you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to Chapter "Deleting an original volume or replica volume" in the Softek AdvancedCopy Manager Operator's Guide. 2. On the storage management server, change the port number of the communications service (stgxfws) of Softek AdvancedCopy Manager. 133

137 Change the port number of the communications service (stgxfws) described at windows-install-directory system32 drivers etc services. When the storage management server is being operated on the cluster, change the port number of the communication daemon (stgxfws_logic node name) of Storage management server transaction. 3. On the storage management server, execute the server information change command. For more information on the server information change command, see chapter , "Management server information change command (stgcmmodnode)". 4. On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see chapter , "Management server information change command (stgcmmodnode)". 5. On the storage management server, restart the services of Softek AdvancedCopy Manager. For information on restarting a service, see Chapter 2, "Starting and Stopping a Service". About change by cluster operation, see "Changing the port number of a storage management server transaction," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Changing the port number of a storage server Change the port number of a storage server as follows: For more information on the Web window, see chapter , "Changing the port number of a storage server" of the "Softek AdvancedCopy Manager User's Guide". 1. When you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to Chapter "Deleting an original volume or replica volume" in the Softek AdvancedCopy Manager Operator's Guide. 2. On a target storage server, stop services of Softek AdvancedCopy Manager. For more information on stopping a service, see Chapter 2, "Starting and Stopping a Service". 3. On the storage server, change the port number of the communications service (stgxfws) of Softek AdvancedCopy Manager. Change the port number of the communications service (stgxfws) described at windows-install-directory system32 drivers etc services. When the storage server is being operated on the cluster, change the port number of the communication daemon (stgxfws_logic node name) of Storage server transaction. 4. On the storage server, start services of Softek AdvancedCopy Manager. For more information on starting a service, see Chapter 2, "Starting and Stopping a Service". Later, follow steps 5 and 6 if the address is changed by using the Web screen, and follow step 7 if the address is changed by using a command. 5. On the server list view on the initial window of Softek AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window. 6. On the [Change of server] window, change the port number and click the [OK] button. 7. Change the IP address by using the server information change command on the Web server. Refer to Chapter " Server information change command(stgxfwcmmodsrv)" About change by cluster operation, see "Changing the port number of a storage server transaction," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Changing the server name of a storage management server Change the server name of a storage management server as follows: For more information on the Web window, see Chapter , "Changing the server name of a storage management server" of the "Softek AdvancedCopy Manager User's Guide". 1. Check whether the target storage management server serves also as a storage server. If it does, do as described in Chapter 9.5.6, "Changing the server name of a storage server". Then, please perform Procedure 5. Later, follow steps 2 and 3 if the address is changed by using the Web screen, and follow step 4 if the address is changed by using the command. 2. On the server list view on the initial window of Softek AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window. 134

138 3. On the [Change of server] window, change the server name and click the [OK] button. 4. Change the server name by using the server information change command on the Storage server. Refer to Chapter , "Server information change command," for details on the server information change command. Later, follow step On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see chapter , "Server information change command (stgcmmodnode)". About change by cluster operation, see "Changing the server name of a storage management server transaction," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Changing the server name of a storage server Change the server name of a storage server as follows: For more information on the Web window, see chapter , "Changing the server name of a storage server" of the "Softek AdvancedCopy Manager User's Guide". 1. In the Storage server used as the candidate for change, when the backup management function is being used, please delete operating volume and backup volume with reference to Chapter "Deleting a device" in the Softek AdvancedCopy Manager Operator's Guide. Moreover, when the definition is given as a original or replica volume using a replication management function, please delete a setup of a original/ replica volume with reference to Chapter "Deleting an original volume or replica volume" in the Softek AdvancedCopy Manager Operator's Guide. 2. Delete a storage server environment. For information on the deletion method, see chapter 4.6.4, "Deleting a storage server ". Later, follow steps 3 and 4 if the address is changed by using the Web screen, and follow step 5 if the address is changed by using the command. 3. On the server list view on the initial window of Softek AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window. 4. On the [Change of server] window, change the server name and click the [OK] button. 5. Change the server name by using the server information change command on the Storage server. Refer to Chapter , "Server information change command(stgxfwcmmodsrv)," for details on the server information change command. About change by cluster operation, see "Changing the server name of a storage server transaction," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Changing the device configuration Changing the device configuration refers to any of the following: Deleting a logical drive in the primary or extended partition Adding a primary or extended partition or a logical drive Changing the partition type (primary or extended partition) Changing the capacity of logical drive in the primary or extended partition When backup synchronized processing or synchronized replication processing is being performed, device composition after change may be unable to be acquired correctly. Therefore, when reflecting in the management list of Softek AdvancedCopy Manager the device composition after change, all synchronous processings are canceled and carry out Backup management Change the device configuration in the following procedure. This processing is executed for all volumes on the disk where the volume whose device configuration is to be changed is located. 1. Check whether there is a transaction volume on the target disk that needs to be backed up. If it does, delete the transaction volume. For information on deleting a transaction volume, see Chapter , "Deleting a 135

139 transaction volume". 2. Check whether a backup volume exists in the target disk. If it does, delete the backup volume. For information on deleting a backup volume, see Chapter , "Deleting a backup volume". 3. Using Disk Administrator, change the device configuration If a logical drive in the primary partition or an extended partition is deleted, restart the system. 4. Because the postchange device configuration needs to be reflected in the Softek AdvancedCopy Manager data set, execute device information change processing for Softek AdvancedCopy Manager. Refer to Section 4.4.5, "Fetching device information on a storage server," for details on changing the device information. 5. Set a deleted transaction volume or backup volume again in the backup operation. Refer to Section 4.4.8, "Setting the operation type for a device," for details on adding the transaction volume or backup volume Replication management Change the device configuration as shown below. When executed, this processing applies to all the volumes on a disk on which a volume whose device configuration to be changed is stored. 1. Check whether there are any replication volumes on the target disk. If there are, delete them. For information about deleting a replication volume, see chapter 6.6.2, "Deleting an original volume or replica volume." 2. Use Disk Administrator to change the device configuration. If a logical drive in the primary partition or an extended partition is deleted, restart the system. 3. Because the postchange device configuration needs to be reflected in the Softek AdvancedCopy Manager data set, execute device information change processing for Softek AdvancedCopy Manager. Refer to Section 6.4.4, "Fetching device information from a storage server," for details on changing the device information. 4. Set a deleted replica volume again in the replication operation. Refer to Section 6.4.5, "Setting the original volume and replica volume," for details on adding the replica volume Changing the IP address for GUI connection of a storage management server The Storage management server is equipped with two or more network cards, and in order to divide and apply to the IP address specified in case the IP address (IP address specified when it was the database creation at the time of Storage management server introduction) and Web screen with a Storage server which communicate are used, the IP address for GUI connection is changed using a GUI connection information setting command. Please refer to GUI connection information setting command and chapter "GUI connection information setting command (stgguiipset)." Change of deletion/password of the user who specified it as the reposit ory access user When a user is deleted on OS about the "repository access user" who specified by environmental setup at the time of manager introduction of Softek AdvancedCopy Manager, or when the password to the specified user name is changed on OS, the information of a "repository access user" is re-set up using a repository access user change command. Please refer to " Repository access user change command (stguserset)" about a repository access user change command. About change by cluster operation, see "Changing of deletion/password of the user who specified it as the repository access user," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system About change of the employment environment in cluster employment Please refer to each item of the "Operator's Guide for cluster environment" corresponding to the cluster system about change of the following environment on cluster operation. Changing the IP address of a storage management server transaction Changing the IP address of a storage server transaction Changing the port number of a storage management server transaction Changing the port number of a storage server transaction Changing the server name of a storage management server transaction Changing the server name of a storage server transaction Change of deletion/password of the user who specified it as the repository access user Changing the logic node name Changing the server name Changing the shared disk for AdvancedCopy Manager share data 136

140 Changing the shared disk for AdvancedCopy Manager repository 137

141 138

142 Chapter 10 Commands You can operate Softek AdvancedCopy Manager using the Web window. However, all commands provided by Softek AdvancedCopy Manager can be performed as unattended operations in combination with a shell. All the commands provided in this chapter should be installed in the Win32app AdvancedCopyManager directory of the C drive. In cluster operation, some commands need an environment variable (SWSTGNODE) and the node that can execute a command is also decided. About executing a command on cluster operation, see "Commands," in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to the cluster system Backup Management Commands Backup management commands are <INSERT BRIEF EXPLANATION TO THE COMMAND'S PURPOSE>. This commands can only be executed by users belonging to the Administrators group Environment definition commands The following commands are used to define a backup environment: Function Storage server configuration information setting command Storage server configuration information display command Device information setting command Device usage status display command Command name swstsvrset swstsvrdisp swstdevinfoset swstdevdisp Description Sets the configuration information of a storage server. Displays the configuration information of a storage server. Sets the use of a device. Displays the information of a device. Backup policy setting command swstbkpolset Sets a backup policy. Backup policy display command Backup policy deletion command swstbkpoldisp swstbkpoldel Displays a backup policy that has been set. Deletes a backup policy that has been set Storage server configuration information setting command (swstsvrse t) This command sets configuration information of a storage server for the backup operation. a. Specification method [To be executed on a storage server] program-directory bin swstsvrset [To be executed on a storage management server] program-directory bin swstsvrset [-h Server] b. Description of options Option -h Description c. End status = 0: Normal end Specifies the name of a storage server to be subject to the backup operation. This option is valid only on a storage management server. If this option is omitted, the storage server on which the command is entered will be subject to the processing. 139

143 > 0: Abnormal end d. Execution example Set configuration information of a storage server. C: >C: Win32app AdvancedCopyManager bin swstsvrset swstsvrset completed C: > Set configuration information of a storage server (Work2) from a storage management server. C: >C: Win32app AdvancedCopyManager bin swstsvrset -h Work2 swstsvrset completed C: > This command can be executed only while none of the following commands are running. Storage server configuration information setting command(swstsvrset) Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Device information setting command (swstdevinfoset) History information deletion command (swsthistdel) Resource backup command (swstresback) Resource restore command (swstresrst) Resource match command (swstsrsemtch) SQL Server backup execution command (swstbackup_sqlsvr) Exchange database information registration command (swstdbinfo_exchange) Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deleting command (swstbkpoldel_exchange) Exchange synchronous command (swststartsync_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) Exchange backup execution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore execution command (swstrestore_exchange) Storage server configuration information display command (swstsvrdi sp) This command displays configuration information of a storage server, which has been set using the storage server configuration information setting command. a. Specification method [To be executed on a storage server] program-directory bin swstsvrdisp [To be executed on a storage management server] program-directory bin swstsvrdisp [-h Storage-Server] b. Description of options Option -h Description c. End status = 0: Normal end > 0: Abnormal end Specifies a storage server name. This option is valid only on a storage management server. 140

144 d. Execution example Display configuration information of a storage server (Work1). C: >C: Win32app AdvancedCopyManager bin swstsvrdisp Storage-Server = Work1 C: > The following information will be displayed. Title Description Storage-Server Displays a storage server name Device information setting command (swstdevinfoset) Set a volume that has been allocated to the disk array unit GR series, as a transaction or backup volume. A transaction volume refers to a volume that stores transaction data to be backed up. A backup volume refers to a volume used to store a backup of this transaction data. The following devices can be registered on Windows as transaction and backup volumes. SCSI driver resource (OS standard) MPHD driver resource (Multipath disk control for WindowsNT) MPLB driver resource Only regular drives can be registered. No mirror set, stripe set, parity-protected stripe set, and volume set that can be recognized as FT (Fault Tolerant) drives can be registered. Additionally, the following file systems can be used (HPFS is not supported). On Windows NT NTFS and FAT On Windows 2000 NTFS, FAT, and FAT32 You may want to change information (partition size, drive letter, and disk array unit cabinet information) on a device registered as a work or backup volume using an OS management tool such as Disk Administrator or a function such as GRmgr provided by the disk array unit. If you do, you need to deselect the target device from the work or backup volume and register it again. If you add or delete a device (including disk array units and other general devices) on a storage server on Windows, use the "getting and reflecting information of all devices" option on the initial window to update the correspondence table between AdvancedCopy Manager device names and OS information. If you want to perform the backup operation on a regular transaction volume, see Chapter 4.2.2, "Deciding a backup target" for information on a transaction volume and Chapter 4.2.4, "Preparing a backup volume" for information on a backup volume. a. Specification method [To be executed on a storage server] program-directory bin swstdevinfoset -t [-f] -b -o Device-Name [To be executed on a storage management server] program-directory bin swstdevinfoset [-h Storage-Server] -t [-f] -b -o Device-Name b. Description of options Option Description -h -t -f Specifies a storage server name. This option is valid only on a storage management server. Register the specified device as a transaction volume. Cannot be specified at the same time as the -b and -o options. The specified device is registered as operating volume which performs SP series employment. It is simultaneously specified as the -t option. Cannot be specified at the same time as the -b and -o options. -b Register the specified device as a backup volume. Cannot be specified at the same time as the -t and -o options. 141

145 -o c. Description of operand Operand Device-Name Deregister the specified device if it has been registered as a transaction or backup volume. Cannot be specified at the same time as the -t and -b options. Description Specifies an AdvancedCopy Manager device name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Register a device (g1d1p2) as a transaction volume. C: >C: Win32app AdvancedCopyManager bin swstdevinfoset -t g1d1p2 swstdevinfoset completed C: > Register a device (g1d2p1) as a backup volume. C: >C: Win32app AdvancedCopyManager bin swstdevinfoset -b g1d2p1 swstdevinfoset completed C: > Deregister a device (g1d1p2) that has been registered as a transaction volume. C: >C: Win32app AdvancedCopyManager bin swstdevinfoset -o g1d1p2 swstdevinfoset completed C: > When backup/restore is operated in cooperation with the SP series, it is necessary to do the registration setting as a transaction volume by which the SP series is operated. A device cannot be registered as a transaction volume if: Another device with the same logical volume information has already been registered as a transaction volume. The space of the device to be registered overlaps the space of an already registered work or backup volume. The device is a FT drive. The device is a dynamic volume of Windows2000. A device cannot be registered as a backup volume if: Another device with the same logical volume information has already been registered as a backup volume. The space of the device to be registered overlaps the space of an already registered work or backup volume. A drive letter has been allocated to the device to be registered. The device is a FT drive, a dynamic volume of Windows2000, or an SDX object. When the device that is going to be set up is registered as a replication destination volume of replication management. When the device that is going to be set up is registered as replication source volume of the duplicate volume information in which the bidirectional copy of replication management is possible. You must delete related backup history information before: Changing a backup volume to a transaction volume Canceling the setting of a backup volume 142

146 You must delete a backup policy specified on a transaction volume before: Changing a transaction volume to a backup volume Canceling the setting of a transaction volume Changing the transaction volume to a transaction volume subject to the SP operation This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) History information deletion command (swsthistdel) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) SQL Server backup execution command (swstbackup_sqlsvr) Exchange database information registration command (swstdbinfo_exchange) Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deleting command (swstbkpoldel_exchange) Exchange synchronous command (swststartsync_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) Exchange backup execution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore execution command (swstrestore_exchange) Device usage status display command (swstdevdisp) This command displays information of a transaction or backup volume or any other definable device, which has been set using the device information setting command (swstdevinfoset). a. Specification method [To be executed on a storage server] program-directory bin swstdevdisp [-t] [-b] [-o] [Device-Name] [To be executed on a storage management server] program-directory bin swstdevdisp [-h Storage-Server] [-t] [-b] [-o] [Device-Name] 143

147 b. Description of options Option Description -h -t -b Specifies a storage server name. This option can be specified only on a storage management server. Displays information on a device that has been set as a transaction volume. Displays device information on all the transaction volumes if the device name in an operand is omitted. Displays a device that has been set as a backup volume. Displays device information on all the backup volumes if the device name in an operand is omitted. -o Displays all the devices other than those set as a transaction or backup volume. Displays all the devices other than those set as a transaction or backup volume if the device name in an operand is omitted. Information on a device that has been set as a transaction volume will be displayed if all of the t, b, and o options are omitted. c. Description of operand Operand Device-Name Description Specifies a AdvancedCopy Manager device name. Displays device information on all the transaction volumes if this operand as well as the options are omitted. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Display the usage statuses of the registered devices. C: >C: Win32app AdvancedCopyManager bin swstdevdisp -tb Server Device Size Device-Mode Mount-Point (Method) Backup-Engine Work2 g1d1p2 1.0 Gbyte Transaction D: (NTFS) AdvancedCopy Work2 g1d2p1 1.0 Gbyte Transaction E: (FAT) SP Work2 g1d2p1 1.0 Gbyte Backup (used) ---- (----) Work2 g1d2p2 1.0 Gbyte Backup (free) ---- (----) Work2 g1d2p3 2.0 Gbyte Backup (used) ---- (----) Work2 g1d2p4 2.0 Gbyte Backup (free) ---- (----) AdvancedCopy AdvancedCopy AdvancedCopy AdvancedCopy : C: > The following information will be displayed. Title Description Server Device Size Device-Mode Displays a storage server name. Displays a AdvancedCopy Manager device name. Displays the size of a partition allocated to a device. Displays a character string by which a device can be identified. "Transaction": Represents a transaction volume. "Backup": Represents a backup volume. "Other": Represents a device that can be registered as a work or backup volume. A backup volume is indicated as "Backup (used)" if it is being used or "Backup (free)" if it is not used. 144

148 Mount-Point (Method) Displays the drive letter of a device. The file system type of the device is displayed inside the parentheses. Backup-Engine Displays the operation type. "AdvancedCopy": Backup operation using Softek AdvancedCopy Manager "SP" : Backup operation using SP serise Backup policy setting command (swstbkpolset) This command sets a backup policy (numbers of preservation generations and interval days). The number of preservation generations means how many generations of backup data should be kept. The number of interval days means the number of days after execution of backup in which the next backup should be performed. a. Specification method [To be executed on a storage server] program-directory bin swstbkpolset [-i Interval-Days] [-s Save-Number] [Device-Name] [To be executed on a storage management server] program-directory bin swstbkpolset [-h Storage-Server] [-i Interval-Days] [-s Save-Number] [Device-Name] b. Description of options Option Description -h -i Specifies a storage server name. This option can be specified only on a storage management server. Specifies the number of interval days. You can specify a value between 1 and 366. If this option is omitted during initial registration, 30 will be set. If this option is omitted during update, the existing value will be inherited. -s c. Description of operand Operand Device-Name Specifies the number of preservation generations. You can specify a value between 1 and 31. If this option is omitted during initial registration, 2 will be set. If this option is omitted during update, the existing value will be inherited. Description Specifies a AdvancedCopy Manager device name. If the device name is omitted, the backup policy will be set for all the transaction volumes. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Set a backup policy assuming 10 days as the number of interval days and three generations as the number of preservation generations for a transaction volume (g1d1p2). C: >C: Win32app AdvancedCopyManager bin swstbkpolset -i 10 -s 3 g1d1p2 g1d1p2 swstbkpolset completed C: > The backup policy cannot be set for the transaction volume by which the SP series is operated. 145

149 Even if the number of interval days is specified, Softek AdvancedCopy Manager does not automatically collect backup. When you specify a backup policy, there must be as many backup volumes required operating according to the specified backup policy. To view information on the number of backup volumes required to perform the backup operation of a regular transaction volume, see Chapter 4.2.4, "Preparing a backup volume". You can change the number of preservation generations as long as the "history information count at the time" is equal to or less than the "number of preservation generations to be specified". No backup policy can be set if: a. There are not as many backup volumes as the specified number of preservation generations. b. An option for more than the maximum number of preservation generations is specified. c. An option for more than the maximum interval days is specified. This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) Backup policy display command (swstbkpoldisp) This command displays a backup policy that has been set for a transaction volume. a. Specification method [To be executed on a storage server] program-directory bin swstbkpoldisp [Device-Name] [To be executed on a storage management server] program-directory bin swstbkpoldisp [-h Storage-Server] [Device-Name] b. Description of options Option -h Description c. Description of operand Operand Device-Name Specifies a storage server name. This option can be specified only on a storage management server. Description Specifies a AdvancedCopy Manager device name. If the device name is omitted, a backup policy for a transaction volume with a registered backup policy will be displayed. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Display a backup policy of a transaction volume (g1d1p2). C: >C: Win32app AdvancedCopyManager bin swstbkpoldisp g1d1p2 Server Device Interval-Days Save-Number Mount-Point (Method) Work2 g1d1p D: (NTFS) C: > The following information will be displayed. Title Description Server Device Interval-Days Save-Number Displays a storage server name. Displays a AdvancedCopy Manager device name Displays a number of interval days. Displays a number of preservation generations. 146

150 Mount-Point (Method) Displays the drive letter of a device. The file system type of the device will be displayed inside the parentheses. This command cannot be used for the transaction volume by which the SP series is operated Backup policy deletion command (swstbkpoldel) A set backup policy is deleted by using this command. Delete the backup history information of the transaction volume prior to execution. a. Specification method [To be executed on a storage server] program-directory bin swstbkpoldel Device-Name [To be executed on a storage management server] program-directory bin swstbkpoldel [-h Storage-Server] Device-Name b. Description of options Option -h Description c. Description of operand Operand Device-Name Specifies a storage server name. This option can be specified only on a storage management server. Description Specifies a AdvancedCopy Manager device name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Delete a backup policy that has been set on a transaction volume (g1d1p2). C: >C: Win32app AdvancedCopyManager bin swstbkpoldel g1d1p2 g1d1p2 swstbkpoldel completed C: > This command cannot be used for the transaction volume by which the SP series is operated. A backup policy cannot be deleted if the transaction volume has backup history information. This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) 147

151 Operation commands This chapter describes operation commands for backup management. Function Backup execution command Backup execution status display command Command name swstbackup swstbackstat Description Performs the synchronous high-speed backup or snapshot fast backup. Displays the backup progress status. Restore execution command swstrestore Performs restoration. Restore cancellation command swstcancelrest Cancels the execution of restoration. Restore execution status display command History information display command History information deletion command backup synchronous processing start command backup synchronous processing cancel command backup synchronous processing progress display command Execution status display command swstreststat swsthistdisp swsthistdel Swststartsync Swstcancelsync Swstsyncstat swstexecstat Displays the execution status of restoration. Displays the history information that has been backed up. Deletes the history information that has been backed up. Starts backup synchronous processing. Aborts backup synchronous processing. Displays the progress of the backup synchronous processing. Displays the execution status of a command executed on a transaction volume. Drive letter allocation command swstdrvset Allocates a drive letter to a device. Drive letter deallocation command swstdrvunset Deallocates a drive letter that has been allocated to a drive Backup execution command (swstbackup) As for this command, operation changes with states of the advanced copy under execution. When synchronous processing (EC) is not performed Snapshot processing (OPC) is performed and the performance information, such as the date and backup volume of a copy place, is registered into backup history information. When synchronous processing (EC) is performed The state of synchronous processing is checked and, in the case of an equivalent nature maintenance state, backup synchronous processing is suspended. Information, such as time and backup volume of a copy place, is simultaneously registered into backup history information. Backup of such a form is called synchronous high-speed backup. (It becomes an error end when an equivalent nature maintenance state is not reached) In both cases, it is established as backup and access of backup volume is attained from immediately after this command execution. Softek AdvancedCopy Manager executes a backup preprocessing and post pocessing scripts before and after executing. For information oncustomizing these scripts, see Appendix A, "Preprocessing and Postprocessing for Backup and Restoration". AdvancedCopy Manager deletes the oldest backup history information automatically at the time of backup execution, when it has reached the maximum number of preservation generations (*1). (*1) Set up by the backup policy setting command. a. Specification method [To be executed on a storage server] program-directory bin swstbackup Device-Name [-Xdevmap Device-Map-File] [To be executed on a storage management server] 148

152 program-directory bin swstbackup [-h Storage-Server] Device-Name [-Xdevmap Device-Map-File] b. Description of options Option Description -h Specifies a storage server name. This option can be specified only on a storage management server. -Xdevmap c. Description of operand Operand Device-Name Specifies a target backup volume to perform the snapshot fast backup. In the operand, specify a device map file in which a combination of a transaction volume and a target backup volume is described. If this option is not specified, the target backup volume will be automatically selected. To execute this command on a remote basis using the -h option, specify a device map file (of a storage server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character. Description Specifies a AdvancedCopy Manager device name. For more information on a device map file, see Chapter , "Describing a device map file". d. End status = 0: Normal end > 0: Abnormal end e. Execution example Back up a transaction volume (g1d1p2). C: >C: Win32app AdvancedCopyManager bin swstbackup -h Work2 g1d1p2 g1d1p2 swstbackup completed C: > Specify a target backup volume and back up a transaction volume (g1d1p2) in the snapshot fast backup. C: >C: Win32app AdvancedCopyManager bin swstbackup g1d1p2 -Xdevmap C: advancedcopynanager devmap1 g1d1p2 swstbackup completed C: > To guarantee data, this command performs backup after inhibiting access to transaction and backup volumes from other processes. Thus, the drive letters of devices are not assigned. This command terminates with an error if a drive letter of a transaction volume is assigned or if: The volume has a file in use. If the transaction volume is used by another server, the manager of backup must inhibit the access to the transaction volume by canceling the setting of sharing the transaction volume. If, for some reason, you do not want to cancel the setting of sharing the transaction volume, do as described below. For more information see Appendix A, "Preprocessing and Postprocessing of Backup and Restoration". In the backup preprocessing, execute a command (*) with a function equivalent to sync on UNIX to synchronize a transaction volume and a file system. In the backup postprocessing, execute the chkdsk command (allocate a drive letter to a backup volume using the drive letter allocation command (swstdrvset)) to check the file system of a backup volume. (*): For example, use the "clearmem.exe" command provided with "Microsoft Windows NT 4.0 Workstation Resource Kit (ISBN )" to realize a function equivalent to the sync command. (This command is not supported by this product. Use this command on your own responsibility.) Note that backup may not be completely performed using the above procedure. On any server other than the one on which this command is entered, you are recommended to perform backup in an environment in which a transaction volume is not used. 149

153 Backup cannot be executed in the following cases: No backup policy has been specified for the specified transaction volume. Backup executed one generation earlier was unsuccessful. A transaction volume on which OPC is in progress has been specified. The drive letter specified when the transaction volume was registered has been changed. Restoration is being executed using backup history information that will cause a generation overflow. (When restoration is performed using the backup volume of the oldest history) No unused backup volume to be used as the copying destination could be acquired. Any of the cabinet information (cabinet identifier, OLU number, EXTENT start position, and EXTENT size) of a transaction volume has been changed. A drive letter has been allocated to a backup volume to be used as the copying destination. When the state of SDX object is not in the following states. - Mirror volume is ACTIVE or STOP. - A SDX disk is enabling. - A mirror slice is ACTIVE or STOP. When the automatic mount function of a SDX object is effective When operating volume has two or more mount points When other volumes are mounted by operating volume You cannot specify a target backup volume and perform backup if: A backup volume specified in a device map file cannot be used as the backup volume for a corresponding transaction volume. In other words, not all the following conditions are met. - The specified backup volume is unused. - The transaction volume and the backup volume are not the same partition size. The description on a target transaction volume of the device map file has an error (see Chapter , "Describing a device map file"). A device map file name includes a national character. This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) Backup execution status display command (swstbackstat) This command displays the completion status of backup that is being performed using the backup execution command. a. Specification method [To be executed on a storage server] program-directory bin swstbackstat [Device-Name] [To be executed on a storage management server] program-directory bin swstbackstat [-h Storage-Server] [Device-Name] 150

154 b. Description of options Option -h Description c. Description of operand Operand Device-Name Specifies a storage server name. This option can be specified only on a storage management server. Description Specifies a AdvancedCopy Manager device name corresponding to a transaction volume. If this operand is omitted, the backup execution statuses of all the transaction volumes will be displayed. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Display the actual copying execution status. C: >C: Win32app AdvancedCopyManager bin swstbackstat Server Transaction-Disk Backup-Disk Status Execute Work1 g1d1p2 g1d2p1 succeeded ---- Work1 g1d1p3 g1d2p2 executing 70% Work1 g1d1p4 g1d2p3 executing 30% : C: > The following information will be displayed. Keyword Description Server Transaction-Disk Backup-Disk Status Execute Displays a storage server name. Displays the AdvancedCopy Manager device name of a transaction volume. Displays a backup volume name. If no backup has been collected, "----" will be displayed. Displays a backup completion status using one of the following character strings. "----": No backup has been collected (no history exists). "succeeded": Backup has been completed. "executing": Copying using OPC is in progress. "failed": Copying using OPC has been interrupted due to an error. "halt": Copying using OPC has been halt status. Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed. In the case of the operating volume which is carrying out SP series employment, the information on an execution situation is not displayed. Do not use the OPC stop function of GRmgr while the snapshot fast backup is in progress. If you use the OPC stop function of GRmgr, it will display "succeeded" whether or not the backup has actually been successful. If "failed" or "halt" is displayed in the "Status" field, a hardware error may have occurred. After removing the cause of 151

155 the hardware error, delete the backup history information using the history deletion command Restore execution command (swstrestore) The data that exists in backup history information is restored using OPC. When the restore execution command is executed, Softek AdvancedCopy Manager performs the restore preprocessing and postprocessing scripts before and after copying data using OPC. For more information on customizing these scripts, see the chapter on the preprocessing and postprocessing for backup and restoration. a. Specification method [To be executed on a storage server] program-directory bin swstrestore [-g Generation-No -v Version-No] [-r Restore-Device-Name] Device-Name [To be executed on a storage management server] program-directory bin swstrestore [-h Storage-Server [-g Generation-No -v Version-No][-r Restore-Device-Name] Device-Name b. Description of options Option Description -h -g -v Specifies a storage server name. This option can be specified only on a storage management server. Specifies the relative generation number of data to be restored. Check the relative generation number using the history information display command (swsthistdisp). Specifies the absolute generation number of data to be restored. Check the absolute generation number using the history information display command (swsthistdisp). -r Specifies a restore destination device name to restore data to any other device than a transaction volume. Note: If neither the -g or -v option is specified, the latest information out of information under history management will be restored. c. Description of operand Operand Device-Name Description Specifies a AdvancedCopy Manager device name corresponding to a transaction volume. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Restore data with relative generation number 2 (For information on the relative generation number, see data displayed using the history information display command). C: >C: Win32app AdvancedCopyManager bin swstrestore -g 2 g1d1p2 g1d1p2 swstrestore completed C: > Restoration of each individual file cannot be performed because copying between devices will be performed. You can restore data to any device other than a transaction volume. When you do so, the device must not be registered as a transaction volume and the device must have the same space size as the specified transaction volume. 152

156 On a transaction volume on which a file system has been constructed, restore a specific file as follows: 1. Allocate a drive letter to a backup volume using the drive letter allocation command (swstdrvset). Check the backup volume using the backup history list view or history information display command. 2. Copy a file to be restored using the copy command (Windows NT/2000). 3. To unassign the drive letter of a backup volume use the command (swstdrvunset). If the transaction volume is used by another server, the manager of backup must execute this command after inhibiting the access to the transaction volume. For example, canceling the setting of sharing the transaction volume (Windows NT/2000). Restoration or recovery cannot be executed in the following cases: Both a relative and absolute generation numbers have been specified. A device registered as a transaction volume has been specified in a parameter in the -r option. When a device registered as a backup volume has been specified in a parameter in the -r option, the device has been registered in the backup registration information of a certain transaction volume. If you restore data to a backup volume without registered backup data, and the backup volume is used to back up a certain transaction volume, then data will be overwritten. You are recommended not to specify a backup volume as a restore destination device. You perform restoration immediately after performing backup (the actual copying using OPC is in progress). In this case, perform restoration after the actual copying using OPC is completed. Alternatively, on a transaction volume on which a file system has been constructed, perform restoration according to the method described in Points. Any of the cabinet information (cabinet identifier, OLU number, EXTENT start position, and EXTENT size) of a transaction volume to be restored has been changed. A drive letter that has been allocated during transaction volume registration has been changed. An SDX object has been specified in a parameter in the -r option. When operating volume has two or more mount points When other volumes are mounted by operating volume This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) If the transaction volume is an SDX object, you cannot perform restoration using this command. If so, perform recovery as follows: 1. Assign a drive letter to a backup volume using the drive letter allocation command (swstdrvset). Check the backup volume using the backup history list view or history information display command. 2. Copy a file to be restored using the copy command. 3. Unassign the drive letter of a backup volume using the drive letter deallocation command (swstdrvunset) Restore cancellation command (swstcancelrest) This command cancels OPC-based restoration. A hardware error will be detected when the restore execution command is executed while data is being copied using OPC. Remove the cause of the hardware error and repeat restoration using the restore execution command 153

157 (swstrestore). Check whether an abnormality occurred using the restore execution status display command (swstreststat). a. Specification method [To be executed on a storage server] program-directory bin swstcancelrest [-g Generation-No -v Version-No] [-r Restore-Device-Name] Device-Name [To be executed on a storage management server] program-directory bin swstcancelrest [-h Storage-Server][-g Generation-No -v Version-No][-r Restore-Device-Name] Device-Name b. Description of options Option Description -h Specifies a storage server name. This option can be specified only on a storage management server. Specifies the relative generation number of data being restored. -g This option cannot be specified at the same time as the -v option. Check the relative generation number using the restore execution status display command (swstreststat). Specifies the absolute generation number of data being restored. -v This option cannot be specified at the same time as the -g option. Check the absolute generation number using the restore execution status display command (swstreststat). -r Specifies the device name if data is restored to any other device than a transaction volume. Check the device name using the restore execution status display command (swstreststat). Note: The restoration of the latest history information will be canceled if neither the -g or -v option is specified. c. Description of operand Operand Device-Name Description Specifies a AdvancedCopy Manager device name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Cancel restoration of the transaction volume (g1d1p2). C: >C: Win32app AdvancedCopyManager bin swstcancelrest -g 1 g1d1p2 g1d1p2 swstcancelrest completed C: > If you cancel OPC-based restoration using this command, the transaction volume will be in an incomplete status and can no longer be used because part of the data has already been copied. Perform restoration again using the restore execution command (swstrestore). The restoration cannot be canceled by using this command for the transaction volume to operate the SP series. 154

158 You cannot cancel restoration if: The history specified in the -g or -v option does not exist. Restoration is not performed on the device specified in the -r option. Restoration is not performed from the specified history. In this case, processing is terminated with an information message "swst0303 Restoration for specified restoration device is not performed". (The end status is a normal end.) This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) Restore execution status display command (swstreststat) This command displays the execution status of restoration. a. Specification method [To be executed on a storage server] program-directory bin swstreststat [-g Generation-No -v Version-No] [Device-Name] [To be executed on a storage management server] program-directory bin swstreststat [-h Storage-Server [-g Generation-No -v Version-No] [Device-Name] b. Description of options Option Description -h -g Specifies a storage server name. This option can be specified only on a storage management server. Specifies the relative generation number of data whose restore execution status should be displayed. -v Specifies the absolute generation number of data whose restore execution status should be displayed. Note: The restore execution statuses of all the historys will be displayed if both the -g and -v options are omitted. c. Description of operand Operand Device-Name d. End status = 0: Normal end > 0: Abnormal end Description Specifies a AdvancedCopy Manager device name. If this operand is omitted, the restore execution statuses of all the transaction volumes will be displayed. 155

159 e. Execution example Display the restore execution statuses of transaction volumes. C: >C: Win32app AdvancedCopyManager bin swstreststat Server Transaction-Disk Generation Version Backup-Disk Restore-Disk Status Execute Work1 g1d1p g1d2p1 g1d3p2 executing 75% Work1 g1d1p Work1 g1d1p g1d2p succeeded --- Work1 g1d1p g1d2p4 g1d3p5 executing 75% : C: > The following information will be displayed. Title Server Transaction-Disk Generation Version Backup-Disk Restore-Disk Status Execute Description Displays a storage server name. Displays the AdvancedCopy Manager device name of a transaction volume. Displays the relative generation number of restored backup data. "----" will be displayed if no generation number is specified in the -g or -v option and no history being restored exists. Displays the absolute generation number of restored backup data. "----" will be displayed if no generation number is specified in the -g or -v option and no history being restored exists. Displays the name of a backup volume from which data should be copied and restored. "----" will be displayed if restoration is not in progress. Displays a restore target device name unless data is copied and restored to a transaction volume. "----" will be displayed if restoration is not in progress or data is restored to a transaction volume. Displays an execution status. "----": No copying using OPC is in progress. "executing": Copying using OPC is in progress. "succeeded": Copying using OPC has been completed. "failed": Copying using OPC has been interrupted due to an error. "halt": Copying using OPC has been halt status. Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed. Information on the execution situation is not displayed for the transaction volume to operate the SP series. Do not use the OPC stop function of GRmgr while the snapshot fast backup is in progress. If you use the OPC stop function of GRmgr, this command displays "succeeded" whether or not the restoration has actually been successful. 156

160 If "failed" is displayed in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, use the restore cancellation command (swstcancelrest) to cancel restoration. If no generation number has been specified in the -v or -g option, the restore execution statuses of all the historys will be displayed. If, at this time, restoration is not in progress from any of the historys, "----" will be displayed in all the information fields other than "Server" and "Transaction-Disk" History information display command (swsthistdisp) This command displays history information that has been backed up. a. Specification method [To be executed on a storage server] program-directory bin swsthistdisp [Device-Name] [To be executed on a storage management server] program-directory bin swsthistdisp [-h Storage-Server] [Device-Name] b. Description of options Option -h Description c. Description of operand Operand Device-Name Specifies a storage server name. This option can be specified only on a storage management server. Description Specifies a AdvancedCopy Manager device name. If this operand is omitted, the backup history information of all the transaction volumes will be displayed. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Display the backup history information of all the transaction volumes. C: >C: Win32app AdvancedCopyManager bin swsthistdisp Server=Work1 Device=g1d1p2 Mount-Point=D: (NTFS) Generation Version Backup-Date Backup-Device Status Execute /11/12 22:00 g1d2p1 succeeded /11/11 22:00 g1d2p2 succeeded ---- Server=Work1 Device=g1d1p3 Mount-Point= E: (FAT) Generation Version Backup-Date Backup-Device Status Execute /11/12 23:00 g1d3p1 succeeded /11/11 23:00 g1d3p2 succeeded ---- : C: > The following information will be displayed. Keyword Description Server Device Mount-Point Displays a storage server name. Displays a AdvancedCopy Manager device name. Displays the drive letter of a device. The file system type of the 157

161 device will be displayed inside the parentheses. Generation Version Backup-Date Backup-Device Status Execute Displays a relative generation number. This item will not be displayed if no backup history information exists. Displays an absolute generation number. This item will not be displayed if no backup history information exists. Displays a date at which backup has been completed. This item will not be displayed if no backup history information exists. Displays the name of a backup volume to which data has been backed up. This item will not be displayed if no backup history information exists. Displays an actual copying execution status using one of the following character strings. "succeeded": Copying using OPC has been completed. "executing": Copying using OPC is in progress. "failed": Copying using OPC has been interrupted due to an error. "halt": Copying using OPC has been halt status. This item will not be displayed if no backup history information exists. Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed. This item will not be displayed if no backup history information exists. Backup history information is not displayed for the transaction volume to operate the SP series. If "failed" or "halt" is displayed in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, delete the backup history information using the history deletion command History information deletion command (swsthistdel) The backup volume of the deleted history is released and turns into empty backup volume. a. Specification method [To be executed on a storage server] program-directory bin swsthistdel -g Generation-No -v Version-No -z Device-Name [To be executed on a storage management server] program-directory bin swsthistdel [-h Storage-Server] -g Generation-No -v Version-No -z Device-Name b. Description of options Option Description -h Specifies a storage server name. This option can be specified only on a storage management server. Specifies the relative generation number of backup history information to be deleted. -g This option cannot be specified at the same time as the -v or -z. Check the relative generation number using the history information display command (swsthistdisp). 158

162 Specifies the absolute generation number of backup history information to be deleted. -v This option cannot be specified at the same time as the -g or -z. -z c. Description of operand Operand Device-Name Check the absolute generation number using the history information display command (swsthistdisp). Specifies to delete all the backup history information. This option cannot be specified at the same time as the -g or -v. Description Specifies a AdvancedCopy Manager device name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Delete a history with absolute generation number 10 of a transaction volume (g1d1p2). C: >C: Win32app AdvancedCopyManager bin swsthistdel -v 10 g1d1p2 g1d1p2 swsthistdel completed C: > If the history information display command displays "failed" in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, use history information deletion command to delete backup history information. You cannot delete backup history information if: The backup history information specified in the -g or -v option does not exist. The specified backup history information is used in restoration. This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) Backup synchronous processing start command (swststartsync) This command starts backup synchronous processing (starts disk-to-disk copy using EC). a. Specification method [To be executed on a storage server] program-directory bin swststartsync Device-Name [-Xdevmap Device-Map-File] [To be executed on a storage management server] program-directory bin swststartsync [-h Storage-Server] Device-Name [-Xdevmap Device-Map-File] b. Description of options Option Description -h Specify the name of a Storage server. 159

163 -Xdevmap c. Description of operand Operand Device-Name This option can be specified only on the Storage management server. Specifies a target backup volume to perform the backup synchronous processing. In the operand, specify a device map file in which a combination of a transaction volume and a target backup volume is described. If this option is not specified, the target backup volume will be automatically selected. To execute this command on a remote basis using the -h option, specify a device map file (of a storage server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character. Description Specifies a AdvancedCopy Manager device name. For more information on a device map file, see Chapter , "Describing a device map file". d. End status = 0: Normally end > 0: Abnormally end e. Execution example To start the backup synchronous processing for a transaction volume (g1d0p0): C: >C: Win32app AdvancedCopyManager bin swststartsync -h Work2 g1d0p0 g1d0p0 swststartsync completed. C: > Synchronous processing of transaction volume (g1d1p2) begins specifying the backup volume at the output destination. C: >C: Win32app AdvancedCopyManager bin swststartsync g1d1p2 -Xdevmap C: AdvancedCopyManager devmap1 g1d1p2 swststartsync completed C: > When you execute the backup synchronous processing start command for a transaction volume or log group to which the backup synchronous processing is being executed, the message, "swst0301 Backup synchronous processing is being executed." (For a log group, the message ID is swst0302) is output and then the command is terminated normally. You cannot start backup synchronous processing in the following cases. In any of the cases below, take an action according to the "System administrator response" message. When specifying a device that does not support the EC function. When the backup volumes required to start backup synchronous processing cannot be obtained. When specifying a device that is being restored by OPC. When mounting the backup volume to which data is copied. When any of the following commands is running, this command cannot be executed: Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) 160

164 Backup synchronous processing cancel command (swstcancelsync) If the system detects an error while backup synchronous processing is being executed, the copying being performed at that time terminates abnormally. In such a case, use this command to cancel the backup synchronous processing. Use the backup synchronous processing progress display command (swstsyncstat) to check for the error. a. Specification method [To be executed on a storage server] program-directory bin swstcancelsync Device-Name [To be executed on a storage management server] program-directory bin swstcancelsync [-h Storage-Server] Device-Name b. Description of options Option -h Description c. Description of operand Operand Device-Name Specify the name of a Storage server. This option can be specified only with a Storage management server. Description Specifies a AdvancedCopy Manager device name. For more information on a device map file, see Chapter , "Describing a device map file". d. End status = 0: Normally end > 0: Abnormally end e. Execution example To cancel backup synchronous processing to a transaction volume (g1d0p0): C: >C: Win32app AdvancedCopyManager bin swstcancelsync g1dt0p0 g1d0p0 swstcancelsync completed. C: > This command cannot be executed when any of the following commands is running: Storage server configuration information setting command (swstsvrset) Device information setting command(swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange database information registration command (swstdbinfo_exchange) Backup synchronous processing progress display command (swstsy ncstat) This command displays the status of the backup synchronous processing. a. Specification method [To be executed on a storage server] program-directory bin swstsyncstat [Device-Name] [To be executed on a storage management server] program-directory bin swstsyncstat [-h Storage-Server] [Device-Name] b. Description of options Option -h Description c. Description of operand Operand Specify the name of a Storage server. This option can be specified only with the Storage management server. Description 161

165 Device-Name Specifies a AdvancedCopy Manager device name. For more information on a device map file, see chapter , "Describing a device map file". d. End status = 0: Normally end > 0: Abnormally end e. Execution example To display the status of backup synchronous processing to a transaction volume (g1d1p2): C: >C: Win32app AdvancedCopyManager bin swstsyncstat g1d0p0 Server Transaction-Disk Backup-Disk Status Execute Transaction1 g1d1p2 g1d2p2 executing 75% C: > To display the status of backup synchronous processing for all of the transaction volumes: C: >C: Win32app AdvancedCopyManager bin swstsyncstat Server Transaction-Disk Backup-Disk Status Execute Transaction1 g1d1p2 g1d2p2 executing 75% Transaction1 g1d1p3 g1d2p3 equivalent 100% Transaction1 g1d1p4 g1d2p4 failed ---- Transaction1 g1d1p C: > The table below lists the meaning of each title. Title Description Server Transaction-Disk Backup-Disk Status Execute Indicates the name of the Storage server. Indicates the name of the transaction volume. Indicates the name of the backup volume. When backup synchronous processing is not being executed, the system displays "----". Indicates the status of backup synchronous processing: "----": Backup synchronous processing is not being executed. "executing": Backup synchronous processing is being executed but equivalency maintain status has not been established. "equivalent": Equivalency maintain status is established. "failed": Backup synchronous processing was abnormally terminated. "nosession": No session exists (inconsistent resource information). "halt": Backup synchronous processing is being halt status. Indicates the progress of the backup synchronous processing as a percentage (0 to 100%). When backup synchronous processing is not being executed, the system displays "----". In the case of the operating volume which is carrying out SP series employment, the information on an execution situation is not displayed. If "failed" or "halt" is indicated as the status of the backup synchronous processing (in the Status field), a hardware 162

166 failure is considered. First eliminate the hardware failure, then execute the backup synchronous processing cancel command (swstcancelsync) to cancel the backup synchronous processing executed. If "nosession" is indicated as the status of the backup synchronous processing (in the Status field)," resource information having inconsistency is considered. Use the resource match command (swstsrsemtch) to remove the inconsistency from the resource information Execution status display command (swstexecstat) This command displays the execution status of other commands executed on a transaction volume. The execution status of OPC/EC will be displayed if OPC/EC is being executed. a. Specification method [To be executed on a storage server] program-directory bin swstexecstat [-j] [Device-Name] [To be executed on a storage management server] program-directory bin swstexecstat [-j] [-h Storage-Server] [Device-Name] b. Description of options Option Description -h Specifies a storage server name. This option can be specified only on a storage management server. -j Specifies to display information in another format. c. Description of operand Operand Device-Name Description Specifies a AdvancedCopy Manager device name corresponding to a transaction volume. If this operand is omitted, the execution statuses of all the transaction volumes will be displayed. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Display the execution statuses of transaction volumes. C: >C: Win32app AdvancedCopyManager bin swstexecstat Server Device Last-Backup-Date Interval Status Mount-Point (Method) Execute Work1 g1d1p2 2000/12/11 12:20 OK IDLE D: (NTFS) ---- Work1 g1d1p4 2000/12/09 12:20 DELAY=2 EXEC E: (NTFS) snapshot(45%) : C: > The following information will be displayed. Keyword Description Server Device Last-Backup-Date Interval Displays a storage server name. Displays a AdvancedCopy Manager device name. Displays the last backup date. * Displays the time when the backup execution command was accepted. Displays how many days have passed after the specified number of interval days since the last backup date has been exceeded. This item will be displayed as "DELAY=number-of-days-passing". "OK" will be displayed if the number of interval days has not been 163

167 Status Mount-Point(Method) exceeded. Displays whether any of the following commands is being executed on a transaction volume. If so, "EXEC" will be displayed. Otherwise, "IDLE" will be displayed. Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) History information deletion command (swsthistdel) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Displays the drive letter of a device. The file system type of the device will be displayed inside the parentheses. Displays the name of a command being executed or the copying progress ratio. "----": Neither a command or OPC/EC is being executed. "swststartsync": Backup synchronous processing start command is being executed. "swstcancelsync": Backup synchronous processing cancel command is being executed. "swstbackup": The backup execution command is being processed. "swstrestore": The restore execution command is being processed. "swstcancelrest": The restore cancellation command is being processed. "swstbkpolset": The backup policy setting command is being processed. "swstbkpoldel": The backup policy deletion command is being processed. "swsthistdel": The history information deletion Execute command is being processed. "swstcancelrest": The restore cancellation command is being processed. "sync(xxx%)": How far the EC operation has progressed. "sync(failed)": EC has been abnormally terminated. "sync(halt)": EC has been halt status. "snapshot(xxx%)": Progress ratio of backup using OPC "snapshot(failed)": Backup using OPC has abnormally terminated. "snapshot(halt)": Backup using OPC has been halt status. "restore(xxx%)": Progress ratio of restoration using OPC "restore(failed)": Restoration using OPC has abnormally terminated. "restore(halt)": Restoration using OPC has been halt status. If multiple processes are performed on transaction volumes (for example, when the backup synchronous processing start command is issued while a real copy of the snap shot backup is being handled), the display in the Execute field conforms to the following rule: - The display of a command name takes priority if both copying and command execution are in progress. - When a disk copy of the snap shot backup and a disk copy of the backup synchronous processing are being handled simultaneously, the progress of the disk copy of the backup synchronous processing is displayed. (A disk copy for restoration is not performed during disk copy of the snap shot backup or backup synchronous processing due to a restriction of the GR series.) 164

168 The execution example of using the "-j" option is as follows: C: >C: Win32app AdvancedCopyManager bin swstexecstat -h Work2 -j Server Device Execute-Date Status Mount-Point (Method) Execute Work2 g1d1p IDLE D: (NTFS) ---- Work2 g1d1p3 2000/12/10 12:20 EXEC E: (NTFS) sync Work2 g1d1p4 2000/12/09 12:20 EXEC F: (NTFS) swstbackup : C: > The following information will be displayed. Keyword Server Device Execute-Date Status Mount-Point(Method) Execute Description Displays a storage server name. Specifies a AdvancedCopy Manager device name. Displays the command execution time. Displays whether any of the following commands is being executed on a transaction volume. If so, "EXEC" will be displayed. Otherwise, "IDLE" will be displayed. Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) History information deletion command (swsthistdel) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Displays the drive letter of a device. The file system type of the device will be displayed inside the parentheses. Displays the name of a command being executed or the copying progress ratio. "----": Neither a command or OPC/EC is being executed. "swststartsync": Backup synchronous processing start command is being executed. "swstcancelsync": Backup synchronous processing cancel command is being executed. "swstbackup": The backup execution command is being processed. "swstrestore": The restore execution command is being processed. "swstcancelrest"": The restore cancellation command is being processed. "swstbkpolset": The backup policy setting command is being processed. "swstbkpoldel": The backup policy deletion command is being processed. "swsthistdel": The history information deletion command is being processed. "swstcancelrest": The restore cancellation command is being processed. "sync(xxx%)": How far the EC operation has progressed. "sync(failed)": EC has been abnormally terminated. "sync(halt)": EC has been halt status. "snapshot(xxx%)": Progress ratio of backup using OPC 165

169 "snapshot(failed)": Backup using OPC has abnormally terminated. "snapshot(halt)": Backup using OPC has been halt status."restore(xxx%)": Progress ratio of restoration using OPC "restore(failed)": Restoration using OPC has abnormally terminated. "restore(halt)": Restoration using OPC has been halt status. Information on the execution situation is not displayed for the transaction volume to operate the SP series. If "sync (failed)", "snapshot(failed)", "restore(failed)", "sync (halt)", "snapshot(halt)" or "restore(halt)" is displayed in the "Execute" field, a hardware error may have occurred. After removing the cause of the hardware error, do as follows: For "sync (failed)" Execute the backup synchronous processing cancel command (swstcancelsync) to cancel the backup synchronous processing. If "snapshot(failed)" is displayed Delete backup history information using the history information deletion command (swsthisdel). If "restore(failed)" is displayed Cancel restoration using the restore cancellation command (swstcancelrest) Drive letter allocation command (swstdrvset) Use this command if you need to allocate a drive letter temporarily to a device when, for example, you restore an individual file. a. Specification method program-directory bin swstdrvset Device-Name [Drive-Letter] b. Description of operand Operand Description Device-Name Specifies a AdvancedCopy Manager device name. Drive-Letter Specifies a drive letter to be allocated to a device. Valid drive letters include "C:" to "Z:". (The letters are not case-sensitive.) If this operand is omitted, an unused drive letter will be automatically selected (unused drive letters are searched starting from "Z:"). c. Execution example Allocate a drive letter (E:) to a device (g3d1p2). C: >C: Win32app AdvancedCopyManager bin swstdrvset g3d1p2 E: swst1001 E: has been allocated to g3d1p2. swstdrvset completed C: > Allocate an appropriate used drive letter to a device (g3d1p3). C: >C: Win32app AdvancedCopyManager bin swstdrvset g3d1p3 Swst1001 Z: has been allocated to g3d1p3. swst0307 Z: is allocated to g3d1p3. swstdrvset completed C: > You cannot allocate a drive letter if: 166

170 The specified drive letter has already been allocated to other drive or resource. When this command is executed with no drive letter specified, no unused drive letter exists. The user who executes a command does not have the administrators authority for the local machine. When this command is executed with a drive letter specified, this drive letter has already been allocated (Warning message swst1011 will be displayed). When this command is executed with no drive letter specified, one or more drive letters have already been allocated (Warning message swst1011 will be displayed). This command is executed on a dynamic volume of Windows2000. On Windows2000, the target device is mounted on another device. On Windows2000, the target device mounts another device. On Windows2000, the target device mounts itself. Do not use Disk Administrator when you use this command. A drive letter allocated using this command is valid until the OS is shut down. When the OS is restarted, drive letters revert to the status before this command is executed Drive letter deallocation command (swstdrvunset) The drive character currently assigned to the device is canceled. a. Specification method program-directory bin swstdrvunset (Device-Name Drive-Letter) b. Description of operand Operand Description Device-Name Specifies a AdvancedCopy Manager device name. Drive-Letter Specifies a drive letter. Valid drive letters include "C:" to "Z:". (The letters are not case-sensitive.) c. Execution example Deallocate the drive letter of a device (g3d1p2). C: >C: Win32app AdvancedCopyManager bin swstdrvunset g3d1p2 swst1002 The allocation of the drive letter for g3d1p2 has been released. Drive letter=e: swstdrvunset completed C: > Deallocate the drive letter of a device (Z:). C: >C: Win32app AdvancedCopyManager bin swstdrvunset Z: swst1002 The allocation of the drive letter for g3d1p3 has been released. Drive letter=z: swstdrvunset completed C: > You cannot unassign a drive letter if: No drive letter has been allocated to the specified device. The specified device is in use. The specified drive letter has not been allocated to a device. The specified device is either in use or shared. The specified drive letter has been allocated to a device that does not have a AdvancedCopy Manager device name. The user who executes the command does not have an administrators permission. This command is executed on a dynamic volume of Windows2000. On Windows2000, the target device is mounted on another device. On Windows2000, the target device mounts another device. On Windows2000, the target device mounts itself. 167

171 Do not use Disk Administrator when you use this command. A drive letter allocated using this command is valid until the OS is shut down. When the OS is restarted, drive letters revert to the status before this command is executed Maintenance commands To operate backup management, use the following maintenance commands: Function Resource match command Resource backup command Resource resore command Command name swstsrsemtch swstresback swstresrst Description Recovers the consistency of information in a backup management list. Backs up a backup management list and a recovery control file. Restores a backup management list and a recovery control file Resource match command (swstsrsemtch) This command recovers resource informationif a system failure, etc. has made the resource information inconsistent. a. Specification method [To be executed on a storage server] program-directory bin swstsrsemtch [-x] [To be executed on a storage management server] program-directory bin swstsrsemtch [-x] [-h Storage-Server] b. Description of operands Operand Description -h Specifies a storage server name.this option can be specified only on a storage management server. -x c. Execution example Gets consistency with a repository. Specify this option if the consistency between a backup management list and a repository comes to be inconsistent. C: >C: Win32app AdvancedCopyManager bin swstsrsemtch swstsrsemtch completed C: > This command can be executed only while none of the following commands are running. 168 Storage server configuration information setting command(swstsvrset) Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Device information setting command (swstdevinfoset) History information deletion command (swsthistdel) Resource backup command (swstresback) Resource restore command (swstresrst) Resource match command (swstsrsemtch) SQL Server backup execution command (swstbackup_sqlsvr) Exchange database information registration command (swstdbinfo_exchange)

172 Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deleting command (swstbkpoldel_exchange) Exchange synchronous command (swststartsync_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) Exchange backup execution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore execution command (swstrestore_exchange) Resource backup command (swstresback) A backup management book is backed up to the specified directory. Backup management book Management books, such as Storage server composition information The information backed up by this command can be restored by the resources restoration command. By this command, a replication management book, a database, and an attestation management book are not evacuated. a. Specification method program-directory bin swstresback Backup-Directory b. Description of operand Operand Backup-Directory Description Specifies the name of a directory to which resource control information should be saved. c. Execution example Back up resource control information to C: backup. C: >C: Win32app AdvancedCopyManager bin swstresback C: backup swstresback completed C: > You cannot perform backup if: The specified directory does not exist. Copying of data to the specified directory failed because of insufficient free space, etc. This command can be executed only while none of the following commands are running. Storage server configuration information setting command(swstsvrset) Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Device information setting command (swstdevinfoset) History information deletion command (swsthistdel) Resource backup command (swstresback) Resource restore command (swstresrst) Resource match command (swstsrsemtch) SQL Server backup execution command (swstbackup_sqlsvr) Exchange database information registration command (swstdbinfo_exchange) Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deleting command (swstbkpoldel_exchange) Exchange synchronous command (swststartsync_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) Exchange backup execution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore execution command (swstrestore_exchange) 169

173 Resource restore command (swstresrst) A backup management book is restored from the specified directory. Managed resources information Management books, such as Storage server composition information. a. Specification method program-directory bin swstresrst Backup-Directory b. Description of operand Operand Backup-Directory Description The evacuation place directory name directed by the Backup-Directory resources backup command is specified. c. Execution example Restore resource management information and a recovery control file from C: backup. C: >C: Win32app AdvancedCopyManager bin swstresrst C: backup swstresrst completed C: > You cannot perform restoration if: The specified directory does not exist. No backup management list exists in the specified directory. Copying of data from the specified directory for restoration failed because of insufficient free space, etc. This command can be executed only while none of the following commands are running. Storage server configuration information setting command(swstsvrset) Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup execution command (swstbackup) Restore execution command (swstrestore) Restore cancellation command (swstcancelrest) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Device information setting command (swstdevinfoset) History information deletion command (swsthistdel) Resource backup command (swstresback) Resource restore command (swstresrst) Resource match command (swstsrsemtch) SQL Server backup execution command (swstbackup_sqlsvr) Exchange database information registration command (swstdbinfo_exchange) Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deleting command (swstbkpoldel_exchange) Exchange synchronous command (swststartsync_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) Exchange backup execution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore execution command (swstrestore_exchange) 10.2 Configuration Management Commands This chapter is explains operation the composition management command. This manages the information on a server device which performs backup employment and replication employment, or is a candidate for employment Management server information change command (stgcmmodnode) This command changes the following information on a storage management server. IP address of a storage management server 170

174 PORT number used by a communication service that runs on a storage management server Server name of a storage management server This command has the following two functions: Displays storage management server information specified on the storage server on which this command is currently executed Changes storage management server information. a. Specification method program-directory bin stgcmmodnode [-i IP-address] [-p PORT number] [-n Server name] b. Description of options Option Description None -i -p Displays the server information currently managed. Specifies the IP address of a storage management server to change the IP address of the storage management server. Specifies the port number of a storage management server to change the port number of the storage management server. -n Specifies the server name of a storage management server to change the server name of the storage management server. This option cannot be specified if this command is executed on a storage management server. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Display server information. C: >C: Win32app AdvancedCopyManager bin stgcmmodnode swstf2413 IP Address = swstf2413 PORT Number = 1226 swstf2413 Storage Management Server's Name = fujitsu-storage-management-server C: > Change the IP address of a storage management server to C: >C: Win32app AdvancedCopyManager bin stgcmmodnode -i swstf2401 AdvancedCopy Manager registry updated. C: > The following lists notes on this command. This command can be executed only by an account belonging to the administrators group. As the PORT number of a storage management server, you can specify a value between 1 and In this command, specify the same value as the one specified on a storage management server. A error will occur in the operation if an invalid value is specified. Change the IP address of a storage management server or the PORT number used by the communication service (stgxfws) as follows: 1. On a storage management server, change the server information using this command. 2. On each of the storage servers, change the server information of the storage management server using this command. This command must be executed on all the storage servers managed by the storage management server. 3. Restart services of Softek AdvancedCopy Manager on the storage management server. For information on starting a service, see Chapter 2, "Starting and Stopping a Service". Change the server name of a storage management server as follows: 1. Change the server name on the initial window of the storage management server. 2. On each of the storage servers, change the server name of the storage management server using this command. This command must be executed on all the storage servers managed by the storage management server. 171

175 3. Restart services of Softek AdvancedCopy Manager on the storage management server. For information on starting a service, Chapter 2, "Starting and Stopping a Service" Repository access user change command (stguserset) This command changes the user name and the password of a "repository access user" specified when Manager of Softek AdvancedCopy Manager was installed. This command must be executed on a storage management server. The change in the user-name and the password is executed according to the following procedures. 1. Close Web browser of AdvancedCopy Manager. 2. Execute Repository access user change command (stguserset). 3. Stop service (AdvancedCopy Manager GUI service). 4. Start service (AdvancedCopy Manager GUI service). a. Specification method program-directory bin stguserset user-name password b. Description of options Option Description User name Specifies a user name to be used for repository access. Password Specifies a user password to be used for repository access. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Change the user name and the password to be used for repository access to a1234 and Yfd1fz3, respectively. C: >C: Win32app AdvancedCopyManager bin stguserset a1234 Yfd1fz3 Password for accessing the repository has been registered. C: > This command can be executed only by an account belonging to the administrators group. A user name to be specified in this command must already be registered to the system and have the local logon authority GUI connection information setting command (stgguiipset) The Storage management server is equipped with two or more network cards, and it is used when dividing and employing the IP address specified in case the IP address (IP address specified when it was the database creation at the time of Storage management server introduction) and Web screen with a Storage server which communicate are used. It is necessary to execute this command by the Storage management server. This command has the following functions. Displays the IP address for GUI connection of the Storage management server Changes the IP address for GUI connection of a Storage management server To change the IP address for GUI connection of a Storage management server: 1. The web browser of AdvancedCopy Manager is closed. 2. A GUI connection information setting command (stgguiipset) is carried out. 3. Service (display name: AdvancedCopy Manager GUI Service) is stopped. 4. Service (display name: AdvancedCopy Manager GUI Service) is started. a. Specification method Program directory bin stgguiipset [-i IP address] b. Description of options Option Description None Displays the IP address for GUI connection currently managed. -i The IP address for GUI connection to change is specified. c. End status = 0: Normal end > 0: Abnormal end d. Execution example The IP address for the present GUI connection is displayed. 172

176 C: >C: Win32app AdvancedCopyManager bin stgguiipset IP Address = C: > The IP address for GUI connection of a Storage management server is changed into C: >C: Win32app AdvancedCopyManager bin stgguiipset -i swstf2401 Renewal of the server information on a Storage management server was completed normally. C: > Only the account which belongs to an administrators group can execute this command Server information addition command (stgxfwcmaddsrv) This command adds Storage server information to be managed by AdvancedCopy Manager. This command can only be executed from the Storage management server. a. Specification method Program directory bin stgxfwcmaddsrv [-n Server-Name] -i IP address -p port-number b. Description of options Option Description Specify a Storage server name to be added. (Within 255 bytes) -n If the name is omitted, a host name is set under the noncluster environment, and the logical node name specified during cluster setup is set under the cluster environment. Specify the IP address of the Storage server to be added by IPv4 format. -i Specify a physical IP address if the Storage server is managed as a physical server. Specify a logical IP address if the IP address is made redundant and managed (as a logical server), like under the cluster environment. -p Specify the port number that is set on the Storage server side to communicate with the Storage server to be added. (Value from 1,024 to 65,535) Under the cluster environment, specify the port number that is allocated to the service name stgxfws_? (*1). (*1) Logical node name of AdvancedCopy Manager specified during cluster setup c. End status = 0: Normal end > 0: Abnormal end d. Execution example Add a server by using host name. C: >C: Win32app AdvancedCopyManager bin stgxfwcmaddsrv -i p 1226 stgxfwcmaddsrv completed C: > Add a logical server that cluster setup is performed by specifying a server name. (Logical IP address: ; port number allocated to stgxfws_logical-node-name: 1227) C: >C: Win32app AdvancedCopyManager bin stgxfwcmaddsrv -n Server1 -i p 1227 stgxfwcmaddsrv completed C: > 173

177 Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation. Because a Storage management server and a logical server for a Storage management server transaction are added during database setup and cluster setup, they are not added by this command. This command cannot be executed when the following commands are being executed: Server information change command(stgxfcmmodsrv) Server information deletion command(stgxfwcmdellsrv) Device information collection/reflection command(stgxfwcmsetdev) Device information deletion command(stgxfwcmdeldev) This command cannot be exectued when the following operations are being performed in the initial window by using the Web screen: Addition of server Change of server Deletion of server Acquisition and Reflection of Information on All Devices Acquisition and Reflection of Information on Specific Device Deletion of device information Server information change command (stgxfwcmmodsrv) This command changes the following server information managed by AdvancedCopy Manager. It is necessary to execute this command on the Storage management server. Storage server IP address Storage server port number Server name of Storage management server Server name of Storage server When the target server is an SP series, the GR cabinet information being managed is also changed. Only the management server information change command (stgcmmodnode) can change the following server information: IP address of Storage management server Port number of Storage management server When the server information is changed by using this command, the machine definition information must be changed in advance. Refer to the procedure given in Chapter 9.5, "Changing the operating Environment," to execute the processing. a. Specification method Program directory bin stgxfwcmmodsrv -n Server-Name [-s New-Server-Name] [-i New-IP-Address] [-p New-port-Number] b. Description of options Options Description -n Specify a server name that is currently being managed. -s Specify a new server name. (Within 255 bytes) -i Specify the IP address of the Storage server to be added by IPv4 174

178 -p format. Specify a physical IP address if the Storage server is managed as a physical server. Specify a logical IP address if the IP address is made redundant and managed (as a logical server), like under the cluster environment. Specify a port number required for postchange communication. (Value from 1024 to 65535) Under the cluster environment, specify the port number that is allocated to service name stgxfws_? (*1). (*1) Logical node name of AdvancedCopy Manager specified during cluster setup c. End status = 0: Normal end > 0: Abnormal end d. Execution example The IP address of a Storage server (server name: Server1) is changed to C: >C: Win32app AdvancedCopyManager bin stgxfwcmmodsrv -n Server1 -i stgxfwcmmodsrv completed C: > The server name of a Storage server (server name: Server1) is changed to Agent5. C: >C: Win32app AdvancedCopyManager bin stgxfwcmmodsrv -n Server1 -s Agent5 stgxfwcmmodsrv completed C: > The GR cabinet information managed by a SP series server (server name: SPServer) is changed. (Do not specify the option in which a change is specified.) C: >C: Win32app AdvancedCopyManager bin stgxfwcmmodsrv -n SPServer stgxfwcmmodsrv completed C: > The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation. This command cannot be executed when the following commands are being executed: Server information addition command(stgxfwcmaddsrv) Server information deletion command(stgxfwcmdelsrv) Device information collection/reflection command(stgxfwcmsetdev) Device information deletion command(stgxfwcmdeldev) This command cannot be exectued when the following operations are being performed in the initial window by using the Web screen: Addition of server Change of server Deletion of server Acquisition and Reflection of Information on All Devices Acquisition and Reflection of Information on Specific Device Deletion of device information 175

179 Server information deletion command (stgxfwcmdelsrv) This command deletes the Storage server information that AdvancedCopy Manager is currently managing. It is necessary to execute this command on the Storage management server. a. Specification method Program directory bin stgxfwcmdelsrv -n Server-Name b. Description of options Options Description -n Specify the Storage server name to be deleted. c. End status = 0: Normal end > 0: Abnormal end d. Execution example A Storage server's (server name: Server1) information is deleted. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdelsrv -n Server1 stgxfwcmdelsrv completed C: > The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation. The Storage management server information cannot be deleted. This command cannot be executed when the following commands are being executed: Server information addition command(stgxfwcmaddsrv) Server information change command(stgxfwcmmodsrv) Device information collection/reflection command(stgxfwcmsetdev) Device information deletion command(stgxfwcmdeldev) This command cannot be exectued when the following operations are being performed in the initial window by using the Web screen: Addition of server Change of server Deletion of server Acquisition and Reflection of Information on All Devices Acquisition and Reflection of Information on Specific Device Deletion of device information Device information collection/reflection command (stgxfwcmsetdev) This command collects the latest device information detected by the server and displays the difference with the information managed by AdvancedCopy Manager. Later, it reflects the specified device difference information in the management information for AdvancedCopy Manager. It is necessary to execute this command on the Storage management server. The device information currently being managed and the device information detected are compared, stored, deleted, and updated, and used in the following cases: 176 When operation using AdvancedCopy Manager is started When device information being managed is changed a. Specification method Program directory bin stgxfwcmsetdev -n Server-Name [-d Device-Name] [-f File-Name -y] b. Description of options

180 Options -n -d -f -y Description Specify the server name whose device information is to be collected or reflected. Specify the device name whose information is to be collected or reflected. If this specification is omitted, all devices of the specified server are assumed to be specified. Use the absolute path to specify the file name to which the difference between the device information managed currently and the device information collected is output. The device difference information is only output to the file, and the reflection processing for the subsequent management information is not executed. This option cannot be specified with the -y option. The difference between the device information managed by AdvancedCopy Manager and the latest device information detected is reflected unconditionally in the management information without an inquiry made about that difference. This option cannot be specified with the -f option. c. End status = 0: Normal end > 0: Abnormal end d. Execution example The information for each device of a server (server name: Server1) is collected or reflected. C: >C: Win32app AdvancedCopyManager bin stgxfwcmsetdev -n Server1 >Device detected 1:g1d38p1 (X:) 2:g1d38p2 3:g1d38p3 >Device not detected 1:g1d39p1 (Y:) 2:g1d39p2 >Specify a device requested to be added. [* or?-? or?,? or q] 1,3 >Specify a device requested to be deleted. [* or?-? or?,? or q] * >Do you want to continue the processing? [y or n] y stgxfwcmsetdev completed C: > The information for a specific device (device name: g1d38p1) managed by the server (server name: Server1) is collected or reflected. C: >C: Win32app AdvancedCopyManager bin stgxfwcmsetdev -n Server1 -d g1d38p1 > The following device information has been changed. This information is updated. 1:g1d38p1 (X:) > Do you want to continue the processing? [y or n] y stgxfwcmsetdev completed C: > 177

181 Use the following methods to request addition or deletion: Enter "*" to specify all. Enter numbers connected with a hyphen to specify a range. (Example: 1-3) Enter numbers separated with a comma to specify an enumeration. (Example: 2, 4) A combination of range and enumeration specifications can be entered. (Example: 1-3, 5) Enter no data to specify nothing. Enter "q" to stop the processing. The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation. Because a device installed in the SP series is not to be managed by AdvancedCopy Manager, its information cannot be collected or reflected. The following message may be displayed when a device requested to be added is specified. In this case, check the following before continuing the processing: whether the device is to be subjected to duplicated registration when two or more logical servers running on the same physical server are managed. (This message is also displayed when the -y option is specified.) > The partitions that comprise the following device are already managed. > Do you want to continue the processing? [y or n] The amount of time required to process this command is proportional to the total number of devices defined on the specified server when the device information is collected. When the number of devices is large, execute the command with low CPU and I/O loads. Note that it takes about 0.5 second for one device (partition) in no load state. When backup synchronous processing or synchronous replication processing is being performed, device information may be unable to be acquired correctly. Therefore, when you take in device information, where all synchronous processing are canceled, please carry out. This command cannot be executed when the following commands are being executed: Server information addition command(stgxfwcmaddsrv) Server information change command(stgxfwcmmodsrv) Server information deletion command(stgxfwcmdelsrv) Device information deletion command(stgxfwcmdeldev) This command cannot be exectued when the following operations are being performed in the initial window by using the Web screen: Addition of server Change of server Deletion of server Acquisition and Reflection of Information on All Devices Acquisition and Reflection of Information on Specific Device Deletion of device information 178

182 Device information deletion command (stgxfwcmdeldev) This command deletes the device information currently being managed by AdvancedCopy Manager. It is necessary to execute this command on the Storage management server. The device information collection/reflection command (stxfwcmsetdev) compares the device information currently being managed and the device information detected before it executes the processing. However, this command deletes the device information irrespective of whether the device information currently being managed is detected. a. Specification method Program directory bin stgxfwcmdeldev -n Server-Name -d Device-Name b. Description of options Options Description -n Specify the server name that is managing the device to be deleted. -d Specify the device name to be deleted. c. End status = 0: Normal end > 0: Abnormal end d. Execution example The device (g1d18p1) information for a Storage server (server name: Server1) is deleted. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdeldev -n Server1 -d g1d18p1 stgxfwcmdeldev completed C: > The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation. This command cannot be executed when the following commands are being executed: Server information addition command(stgxfwcmaddsrv) Server information change command(stgxfwcmmodsrv) Server information deletion command(stgxfwcmdelsrv) Device information collection/reflection command(stgxfwcmsetdev) This command cannot be executed when the following operations are being performed in the initial window by using the Web screen: Addition of server Change of server Deletion of server Acquisition and Reflection of Information on All Devices Acquisition and Reflection of Information on Specific Device Deletion of device information Server information display command (stgxfwcmdispsrv) This command displays the server information managed by AdvancedCopy Manager. It is necessary to execute this command on the Storage management server. a. Specification method Program directory bin stgxfwcmdispsrv [-n Server-Name] b. Description of options Options Description 179

183 -n Specify the server name whose information is to be displayed. If this specification is omitted, the information for all servers managed by AdvancedCopy Manager is displayed. c. End status = 0: Normal end > 0: Abnormal end d. Execution example The information for all servers is displayed. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdispsrv Server Server-Type SP OS-Type OS-Version Version IP-Address Port-Number Manager Management-Server -- Windows V10.0L Server1 Server -- Windows V10.0L C: > The information for a Storage server (server name: Server1) is displayed. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdispsrv -n Server1 Server Server-Type SP OS-Type OS-Version Version IP-Address Port-Number Server1 Server -- Windows V10.0L C: > The contents to be displayed are as follows: Title Description Server Server-Type SP OS-Type OS-Version Version IP-Address Port-Number A server name is displayed. A server type is displayed. "Management-server": Storage management server "Server" : Storage server Whether the server is a SP series is displayed. "--": Other than SP series "Y": SP series An operating system type is displayed. An operating system version is displayed. The version of this product is displayed. The IP address for communication with the server is displayed. The port number for communication with the server is displayed. The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation Device information display command (stgxfwcmdispdev) This command displays the device managed by AdvancedCopy Manager. It is necessary to execute this command on the Storage management server. a. Specification method Program directory bin stgxfwcmdispdev -n Server-Name [-d Device-Name] b. Description of options Options Description -n -d Specify the server name that manages the device whose information is to be displayed. Specify the device name whose information is to be displayed. If this specification is omitted, the information for all devices managed 180

184 by the specified server is displayed. c. End status = 0: Normal end > 0: Abnormal end d. Execution example The information for a device (g1d19p1) of a server (Server1) is displayed. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdispdev -n Server1 -d g1d19p1 Device Block-Device Mount-Point File-System Device-Type Size(MB)RDB-Name Log-Group-Name DB-Space-Name g1d19p1 disk19p1 J: NTFS Normal C: > The information for each device of a server (Server1) is displayed. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdispdev -n Server1 Device Block-Device Mount-Point File-System Device-Type Size(MB) RDB-Name Log-Group-Name DB-Space-Name g1d19p1 disk19p1 J: NTFS Normal g1d19p2 disk19p2 M: NTFS Normal g1d20p1 disk20p1 K: NTFS Normal g1d20p2 disk20p2 N: NTF Normal C: > The following contents are displayed. The following contents are displayed. Note that "SDX" or "SDX object" in the table are SynfinityDISK or PRIMECLUSTER Global Disk Services (GDS) terms. Title Description (For Solaris OE server) A RAW device name is displayed. (Windows server) Device A device name managed internally by AdvancedCopy Manager is displayed. The name is displayed in the g?d?p? format. g?: Disk array number (0 if the device is not installed in the GR series) d?: Disk number (*1) p?: Logical disk number (*2) In the case of the SDX object, the name is displayed in the disk class name or mirror volume name g?d?p? format. Disk class name: Disk class name of SDX object Mirror volume name: Mirror volume name of SDX object (HP-UX server) A RAW device name or a volume group name under LVM is displayed. (Linux server) When a RAW device has been created, its name is displayed; otherwise, a block device name is displayed. (Solaris OE server) A block device name is displayed. (Windows server) The name is displayed in the disk?p? format. Block-Device disk?: Disk number displayed by disk administrator p?: Logical disk number (*2) (HP-UX server) A block device name or a volume group name under LVM is displayed. (Linux server) 181

185 A block device name is displayed. Mount-Point File-System Device-Type Size(MB) (Solaris OE server, HP-UX server, and Linux server) A mount point name is displayed. (Windows server) A drive character is displayed. A file system name is displayed. A device type is displayed. (Normal/SDX/LVM) The capacity (in megabytes) allocated to a device is displayed. (*1) A number given uniquely on the disk array. This number differs from the disk number on the disk administrator. (*2) The sequential number of a logical disk on the disk. The logical disk indicates the following contents of the disk administrator. The number is given by counting up from the left to the right on the disk administrator. In the case of the basic partition, the logical disk is that entire partition. In the case of the extended partition, the logical disk is a logical drive in that partition. The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation Partition information display command (stgxfwcmdisppat) This command displays the information for the partitions that comprise a device managed by AdvancedCopy Manager. It is necessary to execute this command on the Storage management server. a. Specification method Program directory bin stgxfwcmdisppat -n Server-Name -d Device-Name b. Description of options Options Description -n Specify the server name that manages a device whose information is to be displayed. -d Specify a device name whose information is to be displayed. c. End status = 0: Normal end > 0: Abnormal end d. Execution example The partition information for a device (g1d19p1) of a server (Server1) is displayed. C: >C: Win32app AdvancedCopyManager bin stgxfwcmdisppat -n Server1 -d g1d19p1 Partition Identifier Physical-Disk Disk-Type LU-Number g1d19p1 g1d19p1 disk19p1 GR 19 C: > The following contents are displayed. Note that "SDX" or "SDX object" in the table are SynfinityDISK or PRIMECLUSTER Global Disk Services (GDS) terms. Title Description (Solaris OE server) A RAW device name is displayed. In the case of an SDX object, the name is displayed in the RAW device name c?t?d? format. Partition (Windows server) When the device is installed in the GR series, the same contents as Device of the device information display command (stgxfwcmdispdev) are displayed. When the device is not installed in the GR series, the name is displayed in the S?p? format. 182

186 S?: Signature (8-digit hexadecimal number) p?: Logical disk number (*1) (HP-UX server) A RAW device name or a volume group name under LVM is displayed. (Linux server) When a RAW device has been created, its name is displayed; otherwise, a block device name is displayed. In the case of a SDX object, it displays in the form of RAW device name:sd?. (Solaris OE server) A block device name is displayed. In the case of an SDX object, the name is displayed in the block device name c?t?d? format. (Windows server) A device name managed internally by AdvancedCopy Manager is displayed. Identifier The same contents as Device of the device information display command (stgxfwcmdispdev) are displayed. (HP-UX server) A block device name or a volume group name under LVM is displayed. (Linux server) A block device name is displayed. In the case of a SDX object, it displays in the form of block device name:sd?. (Solaris OE server, HP-UX server, and Linux server) "---" is always displayed. Physical-Disk Disk-Type LU-Number (Windows server) A physical device name is displayed. The same contents as Block-Device of the device information display command (stgxfwcmdispdev) are displayed. When the device is installed in the GR series, "GR" is displayed. When the device is not installed in the GR series, "---" is displayed. When the device is installed in the GR series, a logical unit number is displayed. When the device is not installed in the GR series, "---" is displayed. (*1) The sequential number of a logical disk on the disk. The logical disk indicates the following contents of the disk administrator. The number is given by counting up from the left to the right on the disk administrator. In the case of the basic partition, the logical disk is that entire partition. In the case of the extended partition, the logical disk is a logical drive of that partition. The following provides notes on this command: Only the account which belongs to an administrators group can execute this command. Please perform in the locale specified at the time of product installation Replication Management Command This chapter describes operations using Replication Management Commands. It is necessary to execute the command of replication management by the user belonging to the Administrators group. 183

187 Environment definition commands This chapter describes environment definition commands for replication management. To define a replication management environment, use the following commands: Function Replication volume information setting command Replication volume information display command Replication volume information deletion command Command name swsrpsetvol swsrpvolinfo swsrpdelvol Description Sets the information about a replication volume. Displays the information about a replication volume. Deletes replication volume information that has been set Replication volume information setting command (swsrpsetvol) This command sets the replication source and replication destination volumes that will be used in a replication operation. Execute this command to declare that the replication operation will performed using the specified replication volumes. a. Specification method [To be executed on a storage server] For replication on a server program-directory bin swsrpsetvol [-n] [-u] Original-Volume-Name Replica-Volume-Name For replication between servers program-directory bin swsrpsetvol [-n] [-u] -o (ORG REP) Original-Volume-Name Replica-Volume-Name [To be executed on a storage management server] For replication on a server program-directory bin swsrpsetvol -h Server-Name [-n] [-u] Original-Volume-Name Replica-Volume-Name For replication between servers program-directory bin swsrpsetvol -h Server-Name [-n] [-u] -o (ORG REP) Original-Volume-Name Replica-Volume-Name b. Description of options Option Description -h Specifies the name of a storage server subject to the replication operation. This option is valid only on a storage management server. If this option is omitted, the storage server on which the command is entered will be the target to the processing. Specifies the direction of copying. -u If this option is specified, copying from a replication source volume to a replication destination volume is performed only in this direction. Copying from a replication destination volume to a replication source volume is prohibited. If this option is omitted, copying between the replication source and replication destination volumes interactively is bidirectional. Specifies the operation server. Specify one of the following for this operand: -o ORG: Sets the replication source server as the operation server. REP: Sets the replication destination server as the operation server. On the server that is not specified as the operation server, only the following commands can be executed for a replication volume: 184

188 -n Replication volume information display command Operation status display command Replication cancellation command (The forcible stop option is required.) This option is valid only for replication between servers. If this option is omitted, replication volume information cannot be set when the sizes of the replication source volume and replication destination volume are different. When this option is specified, the sizes of the replication source volume and replication destination volume are not checked. Use this option when volume sizes are different (for example, for replication between different OSs). When the volume sizes of the replication source volume and replication destination volume are different, copying is performed as follows: The address at which copying starts is the first sector of the replication destination volume. c. Description of operands Operand The copy data size is the size of the smaller volume. Original-Volume-Name Replica-Volume-Name Description Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Specifies a AdvancedCopy Manager device name for the volume name. Specifies a replication destination volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Specifies a AdvancedCopy Manager device name for the volume name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Set replication volume information by specifying volume g1d1p1 of storage server SRC-SV as the replication source volume and volume g2d1p1 of storage server TARG-SV as the replication destination volume. In addition, specify one-way copying for the copy direction and specify the replication source server (SRC-SV) as the operation server. The example below shows the command executed on SRC-SV. C: >C: Win32app AdvancedCopyManager bin swsrpsetvol -u -o ORG g1d1p1 g2d1p1@targ-sv swsrpsetvol completed C: > When the same settings are made from TARG-SV, the example is as follows (be careful with the volume name): C: >C: Win32app AdvancedCopyManager bin swsrpsetvol -u -o ORG g1d1p1@src-sv g2d1p1 swsrpsetvol completed C: > Replication volume information cannot be set if: Replication volume information has already been set. The specified replication source volume and replication destination volume are set as the replication destination volume and the replication source volume. The n option is not specified when the sizes of the replication source volume and the replication destination 185

189 volume are different. Two volumes that have the same cabinet information (cabinet identifier, OLU number, EXTENT start position, and EXTENT size) as the cabinet information of the specified two volumes have already been set as replication volumes. The replication destination volume has been registered as a backup volume of the backup management function. The replication source volume has been registered as a backup volume of the backup management function and bi-directional copying is specified as a replication volume attribute. The specified replication destination volume and replication source volume are volumes belonging to other servers (at least one volume must be a volume on the local server). If the replication source volume and the replication destination volume are located on another disk array device, the remote copy function of the disk array device is not correctly set. Communication with the storage management server fails. Communication with a destination server fails for replication between servers. When you change physical information on volumes (partition size, drive letter, and cabinet information on a disk array device) using such functions as an OS management tool (for example, Disk Administrator) or GRmgr provided by the disk array device, you need to reset the registered replication volume information associated with the changed volumes, according to the following procedures: 1. Delete the replication volume information by the replication volume information deletion command (swsrpdelvol). 2. In an initial screen, "information acquisition / reflection" of all devices are performed. Or device information acquisition / reflection command (stgxfwcmsetdev) is executed in a Storage management server. 3. Reset the replication volume information by the replication volume informatin setting command (swsrpsetvol). Also, when you add a new device or delete a device (including general devices other than a disk array device) on a Windows NT or Windows 2000 storage server, perform the "acquire and reflect all device information" operation listed on the initial window to update the correspondence table for AdvancedCopy Manager device names and OS information. When you use a replication destination volume by mounting or by allocating a drive letter after creating a replication, the size of the replication destination volume must exactly match the size of the replication destination volume to the byte. If you do not use a replication destination volume (for example, when you need copy data, you restore it to the replication source volume and then use it), the size of the replication destination volume can be larger than the size of the replication source volume. This command cannot be executed while any of the following commands is running: Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Synchronous processing start command (swsrpstartsync) Replication creation command (swsrpmake) Replication cancellation command (swsrpcancel) Resource adjustment command (swsrprecoverres) SQL Server backup execution command (swsrpbackup_sql) Exchange database information registration command (swsrpdbinfo_exchange) Exchange replication start command (swsrpstartsync_exchange) Exchange backup execution command (swsrpbackup_exchange) Exchange data check command (swsrpchkdata_exchange) Exchange restore execution command (swsrprestore_exchange) Exchange cancellation Sync command (swsrpcancel_exchange) Replication volume information display command (swsrpvolinfo) This command displays the replication volume information registered by the replication volume setting command. a. Specification method [To be executed on a storage server] 186

190 program-directory bin swsrpvolinfo [Original-Volumue-Name] [To be executed on a storage management server] program-directory bin swsrpvolinfo -h Server-Name [Original-Volume-Name] b. Description of options Option -h Description c. Description of operands Operand Specifies a storage server name. This option is valid only on a storage management server. Description Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Original-Volume-Name Displays all the replication volume information for the specified replication source volume. If this operand is omitted, all the replication volume information existing on the storage server on which this command is executed is displayed. Specifies a AdvancedCopy Manager device name for the volume name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Direct that all the replication volume information on a storage management server be displayed on storage server SRC-SV. C: >C: Win32app AdvancedCopyManager bin swsrpvolinfo -h SRC-SV Server Original-Volume Size Replica-Volume Size Copy Op-Server SRC-SV g1d1p1@src-sv 4.0Gbyte g2d1p1@targ-sv 4.0Gbyte uni-direction original SRC-SV g1d2p1@src-sv 4.0Gbyte g2d2p1@targ-sv 5.0Gbyte bi-direction original SRC-SV g1d3p1@src-sv 9.1Gbyte g2d3p1@targ-sv 9.1Gbyte bi-direction replica C: > The following information will be displayed. Title Description Server Original-Volume Size Replica-Volume Displays a storage server name. Displays a replication source volume name. Displays the volume size. Displays a replication destination volume name. Displays the copying direction. Copy uni-direction: One-way copying from a replication source volume to a replication destination volume is allowed. bi-direction: Bidirectional copying is allowed. Displays the operation server of a pair of replication volumes. Op-Server original: The replication source server is the operation server. replica: The replication destination server is the operation server. Replication volume information cannot be displayed if: The specified volume is not set as a replication source volume 187

191 This command cannot be executed while the following command is running: Resource adjustment command (swsrprecoverres) Replication volume information deletion command (swsrpdelvol) Delete the replication volume information that has been set. If copy processing is being performed on a replication volume that is to be deleted, execute the command after the copy processing has stopped. a. Specification method [To be executed on a storage server] program-directory bin swsrpdelvol Original-Volume-Name Replica-Volume-Name [To be executed on a storage management server] program-directory bin swsrpdelvol -h Server-Name Original-Volume-Name Replica-Volume-Name b. Description of options Option -h Description c. Description of operand Operand Specifies a storage server name. This option is valid only on a storage management server. Description Original-Volume-Name Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Specifies an AdvancedCopy Manager device name. Replica-Volume-Name Specifies a replication destination volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Specifies an AdvancedCopy Manager device name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Delete replication volume information on storage server SRC-SV. C: >C: Win32app AdvancedCopyManager bin swsrpdelvol g1d1p1 g2d1p1@targ-sv swsrpdelvol completed C: > Replication volume information cannot be deleted if: The specified replication source volume and the replication destination volume are not set as replication volumes. The copy processing (synchronization processing and snapshot processing) is performed between replication volumes. For server-to-server replication, the storage server that executed the command is not the operation server of the replication volume. Communication with a storage management server fails. For server-to-server replication, communication with a destination server fails. 188

192 This command cannot be executed while any of the following commands is running: Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Synchronous processing start command (swsrpstartsync) Replication creation command (swsrpmake) Replication cancellation command (swsrpcancel) Resource adjustment command (swsrprecoverres) SQL Server backup execution command (swsrpbackup_sql) Exchange database information registration command (swsrpdbinfo_exchange) Exchange replication start command (swsrpstartsync_exchange) Exchange backup execution command (swsrpbackup_exchange) Exchange data check command (swsrpchkdata_exchange) Exchange restore execution command (swsrprestore_exchange) Exchange cancellation Sync command (swsrpcancel_exchange) Operation commands This chapter describes operation commands for replication management. To operate replication management, use the following commands: Function Synchronous processing start command Replication creation command Operation status display command Replication cancellation command Command name swsrpstartsync swsrpmake swsrpstat swsrpcancel Description Starts replication while the synchronous type replication function is performed. Creates replication while the snapshot type and the synchronous type replication functions are performed. Displays the status of replication operation Cancels the replication processing while the snapshot type and the synchronous type replication functions are performed Synchronous processing start command (swsrpstartsync) Start the synchronous type replication processing (copying between disks by EC and REC). Copy all the specified replication destination and replication source volumes (start of the synchronization processing), or copy (restart of the synchronization processing) updated data (difference). Use this command at the start of operation or when you want to reflect updated data (difference) from the equivalency holding status. a. Specification method [To be executed on a storage server] program-directory bin swsrpstartsync [-y] [-t] [-m] From-Volume-Name To-Volume-Name [To be executed on a storage management server] program-directory bin swsrpstartsync -h Server-Name [-y] [-t] [-m] From-Volume-Name To-Volume-Name b. Description of options Option Description -h -y This option is valid only on a storage management server. This option can be specified only on a storage management server. Specifies that synchronization processing is started in synchronous write mode (mode in which data is copied to the replication destination volume synchronized with writing to the replication source volume). This option is valid only when total copy for intercabinet replication is started. If this option is omitted, asynchronous write mode (mode in data is copied to the replication destination volume unsynchronized with writing to the replication source volume) is used. The synchronization processing of intracabinet replication is always 189

193 performed in synchronous write mode. -m For server-to-server replication, specifies that communication processing with non-operation servers is not performed. When this option is specified, volume status check processing and the preprocessing for the replication destination volume of a non-operation server are not performed. -t This option is valid only during server-to-server replication. Specifies that preprocessing for the replication destination volume is not performed. c. Description of operands Operand Description From-Volume-Name Specifies a replication source volume name. Specifies the replication source volume or the replication destination volume set with the replication volume information setting command. Specifies a AdvancedCopy Manager device name To-Volume-Name Specifies a replication destination volume name. Specifies the replication source volume or the replication destination volume set with the copy volume information setting command. Specifies a AdvancedCopy Manager device name d. End status = 0: Normal end > 0: Abnormal end e. Execution example Start replication from g1d1p1 of a storage management server to g2d1p1@targ-sv of storage server SRC-SV. C: >C: Win32app AdvancedCopyManager bin swsrpstartsync -h SRC-SV g1d1p1 g2d1p1@targ-sv FROM=g1d1p1@SRC-SV,TO=g2d1p1@TARG-SV swsrpstartsync completed C: > Replication cannot be started if: The specified replication source volume and replication destination volume are not set as replication volumes. A replication source volume is specified as the copy volume and a replication destination volume is specified as the copied material volume, and one-way copy is set as the copy attribute of the replication volume. Volume information (medium identifier, OLU, EXTENT start position, and EXTENT size) is changed after operation starts. In this case, operation cannot continue for the corresponding volume. Stop the replication operation for the corresponding volume, and then delete and set the replication volume information. A replication source volume or a replication destination volume has multiple mount points. For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume. For server-to-server replication, communication with a destination server fails. Replication cannot be started as a result of the preceding advanced copy function. When the replication to perform corresponds to either of the following conditions, please perform drive character release or unmount of copy place volume before executing a command. When a replication is performed between different OS's When the sizes of replication source volume and replication destination volume differ When performing neither drive character release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of duplicate creation serves as an error. 190

194 Now, the replication which makes a SDX object (SynfinityDISK) replication source volume is not supported. Therefore, when one of replication destination volume and the duplicate place volumes is a SDX object, only the replication from a SDX object to a non-sdx object can be used. Use the COPY command in copying data to a SDX object. The processing of this command varies according to the status of the synchronization processing of the specified replication source and replication destination volumes. Status of synchronization processing Unmount status Total or incremental copy status Equivalency maintain status Replication established status (halt status) Processing Start of total copy Abnormal end Abnormal end Start of incremental copy Before starting the replication, run the replication preprocessing script for the replication destination volume. The contents of this script can be customized. For more information, see Appendix C, Replication Scripts. If you do not want to implement the preprocessing script, use the -t option. To protect processing that accesses a replication destination volume, set the replication destination volume before starting replication so that other processes cannot access it. To do so, cancel the drive letter of the replication destination volume or execute unmount. If you cannot cancel the drive letter of the replication destination volume or execute unmount because of the situations described below, this command fails and terminates. There is a directory in which other volumes are mounted under the mount point. A file on the volume is being used. In addition, if the replication destination volume is being used from a server other than the server on which this command is entered, the replication-operation administrator must disable access to the replication destination volume by cancellation of the share setting, unmounting, or some other method. This command cannot be executed while any of the following commands is running: Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) Exchange database information registration command (swsrpdbinfo_exchange) Replication creation command (swsrpmake) When synchronization processing (EC) is not performed, start snapshot processing (OPC) to create a replication volume. When synchronization processing is performed, check whether the status of the processing is equivalency holding status. If the status is equivalency holding status, suspend the synchronization processing and create a replication volume. The status in which synchronization processing is suspended is referred to as the replication established status. After this command is executed, the replication volume (replication destination volume) can be accessed. This command executes the replication preprocessing and postprocessing scripts before a replication is created. For details of these scripts, see Appendix C, "Replication Scripts." a. Specification method [To be executed on a storage server] 191

195 program-directory bin swsrpmake [-f] [-t] [-m] From-Volume-Name To-Volume-Name [To be executed on a storage management server] program-directory bin swsrpmake -h Server-Name [-f] [-t] [-m] From-Volume-Name To-Volume-Name b. Description of options Option Description -h -m Specifies a storage server name. This option can be specified only on a storage management server. For server-to-server replication, specifies that communication processing with the non-operation server is not performed. When this option is specified, volume status check processing and preprocessing and postprocessing are not performed for the non-operation server volume. This option is valid only during server-to-server replication. -f Specifies that the preprocessing and postprocessing for a replication source volume are not performed. -t Specifies that the preprocessing and postprocessing for a replication destination volume are not performed. c. Description of operands Operand Description From-Volume-Name Specifies a replication source volume. Specifies the replication source volume or the replication destination volume that was set with the replication volume information setting command. Specifies a AdvancedCopy Manager device name for the volume name. To-Volume-Name Specifies a replication destination volume. Specifies the replication source volume or the replication destination volume that was set with the replication volume information setting command. Specifies a AdvancedCopy Manager device name for the volume name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example On a storage management server, direct replication of g1d1p1 to g2d1p1@targ-sv for storage server SRC-SV. C: >C: Win32app AdvancedCopyManager bin swsrpmake -h SRC-SV g1d1p1 g2d1p1@targ-sv FROM=g1d1p1@SRC-SV,TO=g2d1p1@TARG-SV swsrpmake completed C: > Replication cannot be created if: The specified replication source and replication destination volumes are not set as replication volumes. The synchronization processing from the specified replication source volume to the replication destination volume is not in the equivalency holding status. After operation starts, physical volume information (medium identifier, OLU, EXTENT start position, and EXTENT size) is changed. In this case, operation for the corresponding volume cannot continue. Stop the replication operation for the volume, and then delete and set the replication volume information. A replication source volume or a replication destination volume has multiple mount points. If a replication source volume is an SDX object (SynfinityDISK), the status of the SDX object does not match the following: 192

196 1. The mirror volume is ACTIVE or STOP. 2. The mirror slice status is ACTIVE or STOP. 3. The SDX disk status is ENABLE. The auto mount function of the SDX object is set to ON, and the replication source volume is an SDX object (SynfinityDISK) in Windows For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume. For server-to-server replication, communication with a destination server fails. When the replication to perform corresponds to either of the following conditions, please perform drive character release or unmount of copy place volume before executing a command. When a replication is performed between different OS's When the sizes of replication source volume and replication destination volume differ When performing neither drive character release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of duplicate creation serves as an error. Now, the replication which makes a SDX object (SynfinityDISK) replication source volume is not supported. Therefore, when one of replication destination volume and the duplicate place volumes is a SDX object, only the replication from a SDX object to a non-sdx object can be used. Use the COPY command in copying data to a SDX object. Before a replication is created, the replication preprocessing and postprocessing scripts for the replication source volume are executed (for synchronized replication, only preprocessing script is executed). After the replication has been created, the replication postprocessing script for the replication source volume and replication destination volume is executed. The contents of the script can be customized. For more information, see Appendix C, "Replication Scripts" If you do not want to implement the preprocessing and postprocessing scripts, use the -f option and the -t option. If this command is executed during execution of snapshot processing, stop the copy processing in progress and start the snapshot processing again. To protect the data, set the replication source volume before creating a replication so that other processes cannot access the volume. To do so, cancel the drive letter of the replication source volume or execute unmount. If you cannot cancel the drive letter of the replication source volume or execute unmount because of the situations described below, this command fails and terminates. There is a directory in which other volumes are mounted under the mount point. A file on the volume is being used. In addition, if the replication source volume is being used from a server other than the server on which this command is entered, the backup-operation administrator must disable access to the replication source volume by cancellation of the share setting, unmounting, or some other method. If for whatever reason you do not want to remove the share setting of the replication source volume or execute unmount or some other method, see Appendix C, "Replication Scripts" and note the following. - When the replication source volume is being used by backup management, unmount may not possible. If so, "swsrp2613 An error occurred on the preprocessing script at replication creation. Error code = 2" is output. - For replication preprocessing, execute a command that operates like the UNIX sync command to synchronize volumes and the file system. For example, use the clearmem.exe command provided in the "Microsoft Windows NT 4.0 Workstation Resource Kit" (ISBN ) to perform processing equivalent to the sync command. (Note, however, that because this command is not supported by Softek AdvancedCopy Manager, you will be using it at your own risk.) 193

197 For replication postprocessing, if you want to check the file system at the replication destination, assign a drive letter to the replication destination volume with the chkdsk drive letter assign command (swstdrvset). However, since a replication may be unable to be completely performed in the above-mentioned procedure, in servers other than the server which supplies this command, we recommend you to perform a replication under the environment where copied material volume is not used. This command cannot be executed while any of the following commands is running: Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) Exchange database information registration command (swsrpdbinfo_exchange) Operation status display command (swsrpstat) This command displays the operation status of the specified volume. If a volume is not specified, the operation status of each replication volumes is displayed. a. Specification method [To be executed on a storage server] program-directory bin swsrpstat [Original-Volume-Name] [To be executed on a storage management server] program-directory bin swsrpstat -h Server-Name [Original-Volume-Name] b. Description of options Option -h Description c. Description of operands Operand Specifies a storage server name. This option can be specified only on a storage management server. Description Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name." Original-Volume-Name Displays all operation statuses for the specified replication source volume. If this operand is omitted, all the operation statuses of the storage server on which this command is executed are displayed. For the volume name, specify a AdvancedCopy Manager device name d. End status = 0: Normal end > 0: Abnormal end e. Execution example Direct that all the replication operation statuses for storage server SRC-SV be displayed on the storage management server. C: >C: Win32app AdvancedCopyManager bin swsrpstat -h SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV g1d1p3@src-sv g2d1p1@targ-sv regular replicated ---- SRC-SV g1d2p1@src-sv g2d2p1@targ-sv SRC-SV g1d3p1@src-sv g2d3p1@targ-sv reverse snap 45% C: > The following information will be displayed. Title Description Server Displays a storage server name. 194

198 Original-Volume Replica-Volume Direction Status Execute Displays a replication source volume name. Displays a replication destination volume name. Displays the copy direction. regular: Copying from the replication source to the replication destination is being performed. reverse: Copying from the replication destination to the replication source is being performed. ----: Copying is not performed. Displays the progress : Copying is not being performed. sync : Total copy or incremental copy is being performed. equivalent : Equivalency maintain status replicated : Replication established status failed : Error suspend status halt : Hard suspend status snap : Snapshot processing is being performed.????? : Copy situation cannot be acquired. Displays the rate of copying progress as a percentage. When copying is not being performed, "----" is displayed. When the execution status (status displayed in the Status field) is one of the following, take appropriate action. Status display Failed Halt????? Corrective action A hardware error may have occurred. Correct the hardware error, and then use the replication cancellation command to stop operation. A hardware error during replication operation between cabinets may occur. Correct the hardware error, and then use the replication cancellation command to stop the copy operation. Copy situation cannot be acquired. A hardware error may have occurred if the result is the same after reexecution. Correct the hardware error, and then reexecute the command. The operation status cannot be displayed if: The volumes are not set as replication volumes. This command cannot be executed while the following command is running: Resource adjustment command (swsrprecoverres) Replication cancellation command (swsrpcancel) This command stops snapshot processing (OPC) and synchronization processing (EC) of the specified replication volume. Use this command when an error is detected during the replication operation and when you want to stop replication processing. a. Specification method [To be executed on a storage server] program-directory bin swsrpcancel [-c] [-f] [-t] [-m] From-Volume-Name To-Volume-Name [To be executed on a storage management server] 195

199 program-directory bin swsrpcancel -h Server-Name [-c] [-f] [-t] [-m] From-Volume-Name To-Volume-Name b. Description of options Option Description -h -c Specifies a storage server name. This option can be specified only on a storage management server. Specifies that the copy processing is forcibly stopped from a non-operation server when the operation server cannot be used because of a system failure. If this option is used, the copy processing is stopped without implementing preprocessing and postprocessing. If this option is used, a contradiction arises in the synchronization processing management information on the operation server. Therefore, after recovery of the operation server, enter the resource adjustment command on the operation server. This option cannot be specified on the operation server. -m For server-to-server replication, specifies that communication processing with non-operation servers is not performed. When this option is specified, volume status check processing and preprocessing and postprocessing for the replication destination volume of a non-operation server are not performed. This option is valid only during server-to-server replication. -f Specifies that preprocessing and postprocessing for the replication source volume are not performed. -t Specifies that preprocessing and postprocessing for the replication destination volume are not performed. c. Description of operands Operand Description From-Volume-Name Specifies a replication source volume name. Specifies the replication source volume or the replication destination volume set with the replication volume information setting command. Specifies a AdvancedCopy Manager device name for the volume name. To-Volume-Name Specifies a replication destination volume name. Specifies the replication source volume or the replication destination volume set with the copy volume information set command. Specifies a AdvancedCopy Manager device name for the volume name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example On the storage management server, direct that copying from g1d1p1 to g2d1p1@targ-sv be stopped for storage server SRC-SV. C: >C: Win32app AdvancedCopyManager bin swsrpcancel -h SRC-SV g1d1p1 g2d1p1@targ-sv FROM=g1d1p1@SRC-SV,TO=g2d1p1@TARG-SV swsrpcancel completed C: > Copy processing cannot be performed if: The specified replication source volume and replication destination volume are not set as replication volumes. The copy processing is not performed for the specified replication source and replication destination volumes. For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume. For server-to-server replication, communication with a destination server fails. 196

200 The volume information for the specified volume is not checked (check for matching of the volume information in the management list and the actual physical information). Operation is canceled unconditionally using the volume information in the management list. The following processing is performed depending on the operation status of the specified replication source volume and replication destination volume. Operation status Reverse copy direction Not operating yet Total or incremental copy is performed Equivalency maintain status Replication established status Snapshot processing is being performed Processing Suspends the processing. Suspends the processing. Suspends synchronization processing. The replication destination volume cannot be used. Suspends synchronization processing. The replication destination volume can be used as a copy Suspends synchronization processing. The replication destination volume can be used as a copy Stops the snapshot processing. The replication destination volume cannot be used. Preprocessing and post processing for a replication source and replication destination volumes are performed only when the status of synchronization processing is equivalency holding state. Synchronization processing cannot be stopped in equivalency holding status if: A replication source volume or a replication destination volume has multiple mount points. When a replication source volume is an SDX object (SynfinityDISK), the status of the SDX object is not one of the following: 1. The mirror volume is ACTIVE or STOP. 2. The mirror slice status is ACTIVE or STOP. 3. The SDX disk status is ENABLE. If a replication source volume is an SDX object (SynfinityDISK) in Windows 2000, the auto mount function of the SDX object is set to ON. This command cannot be executed while any of the following commands is running: Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) Exchange database information registration command (swsrpdbinfo_exchange) Maintenance commands This chapter describes the maintenance commands for replication management. Use the following maintenance commands for replication management. 197

201 Function Resource match command Command name swsrprecoverres Description Restores the consistency of information in a replication management list Resource adjustment command (swsrprecoverres) This command executes recovery to make replication management information consistent if a system failure or other problem has made the replication management information inconsistent. a. Specification method [To be executed on a storage server] program-directory bin swsrprecoverres [-r] [-p] [-s] [To be executed on a storage management server] program-directory bin swsrprecoverres -h Server-Name [-r] [-p] [-s] b. Description of operands Operand Description -h Specifies a storage server name. This option can be used only on a storage management server. Specify this option when an incorrect status exists in the replication management list (for example, the replication volume information setting command or the replication volume information deletion command that update the replication management list terminate suddenly because of a forced stop or a system failure, or the replication management list has been deleted by mistake). -r When this option is specified, the following processing to re-create the replication management list is performed. Replication management information in the storage management server repository is downloaded to the storage server, and the replication volume information is restored. The disk array device is queried, and the execution information for the synchronization processing is restored. (The processing with the -s option specified is performed. This option includes -s option processing.) -p Specifies not to perform any postprocessing that has not been performed. This option can be used when the replication creation command processing terminates suddenly because of a forced stop or system failure. Specify this operand when the replication management list containing synchronization processing information has been deleted by mistake. -s Querying the disk array device enables the execution information for synchronization processing to be restored. In addition, when you use the -r option, you do not need to specify this option since specifying "-r -s" is the same as specifying "-r"). c. End status = 0: Normal end > 0: Abnormal end d. Execution example Perform resource adjustment. C: >C: Win32app AdvancedCopyManager bin swsrprecoverres swsrprecoverres completed C: > The resource adjustment processing cannot be performed if: Communication with a storage management server fails and the -r option is specified. 198

202 The -r option is not specified when this command is executed after processing by the replication volume information setting command and the replication volume information deletion command has been forcibly terminated. The consistency of resource information is restored only for the storage server on which this command is executed. When a resource inconsistency occurs during processing related to replication between servers, this command must be executed both on the storage server on which the processing was performed and on the storage server with which communication is being made. This command cannot be executed while any of the following commands is running: Replication volume information setting command (swsrpsetvol) Replication volume information display command (swsrpvolinfo) Replication volume information deletion command (swsrpdelvol) Synchronous processing start command (swsrpstartsync) Replication creation command (swsrpmake) Operation status display command (swsrpstat) Replication cancellation command (swsrpcancel) Resource adjustment command (swsrprecoverres) SQL Server backup execution command (swsrpbackup_sql) Exchange database information registration command (swsrpdbinfo_exchange) Exchange device display command (swsrpdevdisp_exchange) Exchange replication start command (swsrpstartsync_exchange) Exchange backup execution command (swsrpbackup_exchange) Exchange data check command (swsrpchkdata_exchange) Exchange restore execution command (swsrprestore_exchange) Exchange operation status display command (swsrpstat_exchange) Exchange cancellation Sync command (swsrpcancel_exchange) 10.4 Setup Command This chapter describes operations using a setup command Web server setting and setting cancellation command (alias) This command sets up or cancels the setting of a virtual directory required to use the GUI window of AdvancedCopy Manager on the Web server (IIS). This command must be executed on a storage management server. Use this command if: A failure occurs in the Web server setup automatically executed when you customize Softek AdvancedCopy Manager after installing it. You uninstall Softek AdvancedCopy Manager. When employment of a Web client is started or ended This command sets up and cancels the setting of the following virtual directories: /swstorage /swstorage-cgi /swstorage-d /swstorage-j If any of the virtual directories already exists, change the setting so it can be used on Softek AdvancedCopy Manager. a. Specification method program-directory bin alias [ -u ] b. Description of options Option Description None Sets up the Web server. -u Cancels the setting of the Web server. c. End status = 0: Normal end 199

203 > 0: Abnormal end d. Execution example Set up the Web server. C: >C: Win32app AdvancedCopyManager bin alias Info:AdvancedCopy Manager Web server setup start. Info:AdvancedCopy Manager Web server setup completed. C: > Cancel the setting of the Web server. C: >C: Win32app AdvancedCopyManager bin alias -u Info:AdvancedCopy Manager Web server unsetup start. Info:AdvancedCopy Manager Web server unsetup completed. C: > The following lists notes on this command. This command can be executed only by an account belonging to the administrators group. For information on errors that occur, see Appendix C, "Detailed Error Messages in Setup and Unsetup of Web Server" in the "Softek AdvancedCopy Manager Messages" Exchange Server Commands This chapter explains the command which Softek AdvancedCopy Manager Exchange support software offers. The parameter of a command does not distinguish a capital letter and a small letter. The storage group name containing a space needs to attach double quotation marks ("") (example: swstbackup_exchange-sgname "First Storage Group"). Moreover, it is necessary to execute an Exchange Server cooperation command by the user belonging to the Administrators group and the Domain Admins group. An SDX object is not supported in an Exchange cooperation function. In the Exchange cooperation function for a backup management function, backup employment which cooperated with SP series cannot be performed Backup Management Commands Exchange database information registration command (swstdbinfo_exc hange) This command registers or deletes information on a storage group. The command is used when Exchange Server backup operation begins or after the file configuration of a storage group is changed. Executing the command registers or deletes information on the files that constitute a storage group and information on AdvancedCopy Manager device names. (The files that constitute a storage group include mailbox store and public folder store database files, transaction files, and checkpoint file.) a. Specification method [To register Exchange database information] program-directory bin swstdbinfo_exchange [-evs Virtual-Server-Name] [-sgname Storage-Group-Name] [To delete Exchange database information] program-directory bin swstdbinfo_exchange [-evs Virtual-Server-Name] -clean b. Description of options Option Description -sgname Specifies the storage group name. If this option is omitted, information on all storage groups is registered. 200

204 -clean -evs Specifies that information on the storage group that has been deleted from Exchange Server should be deleted. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Register storage group FirstStorageGroup. C: >C: Win32App AdvancedCopyManager bin swstdbinfo_exchange -sgname FirstStorageGroup swstdbinfo_exchange successfully completed C: > Delete unnecessary storage group information. C: >C: Win32App StorageMGR bin swstdbinfo_exchange -clean swstdbinfo_exchange successfully completed The command cannot register database information if: The specified storage group does not exist. The volume containing the specified storage group is not registered as a transaction volume. Synchronous backup processing is being executed. History information on the specified storage group is inconsistent. This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swstdbinfo_exchange) Exchange backup policy setting command (swstbkpolset_exchange) Exchange backup policy deleting command (swstbkpoldel_exchange) Exchange synchronous command (swststartsync_exchange) Exchange backup exeution command (swstbackup_exchange) Exchange data check command (swstchkdata_exchange) Exchange restore exeution command (swstrestore_exchange) Exchange synchronous processing cancellation command (swstcancelsync_exchange) Storage server configuration information setting command (swstsvrset) Device information setting comand (swstdevinfoset) Backup policy setting command (swstbkpolset) Backup policy deletion command (swstbkpoldel) Backup synchronous processing start command (swststartsync) Backup synchronous processing cancel command (swstcancelsync) Backup execution command (swstbackup) Restore execution command (swstrestore) Restore cancellation command (swstcancelrest) History information deletion command (swsthistdel) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command(swstresrst) Exchange device display command (swstdevdisp_exchange) This command displays the information registered with the Exchange database information registration command (swstdbinfo_exchange). The command displays information on the files that constitute a storage group and information on AdvancedCopy Manager device names. (The files that constitute a storage group include mailbox store 201

205 and public folder store database files, transaction files, and checkpoint file.) a. Specification method [To display information on a specific storage group] program-directory bin swstdevdisp_exchange -sgname Storage-Group-Name [To display information on all storage groups used for Exchange] program-directory bin swstdevdisp_exchange [-evs Virtual-Server-Name] b. Description of options Option Description -sgname Specifies the storage group name. If this option is omitted, information on all storage groups is displayed. -evs Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Display device information on storage group FirstStorageGroup. C: >C: Win32app AdvancedCopyManager bin swstdevdisp_exchange -sgname FirstStorageGroup Exchange Storage Group:FirstStorageGroup MailBoxStore:Mail1 EDB:e: Exchsrvr mdbdata priv1.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr mdbdata priv1.stmadvancedcopy Manager Device:g1d1p1 PublicStore:Pub1 EDB:e: Exchsrvr pdbdata priv1.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr pdbdata priv1.stmadvancedcopy Manager Device:g1d1p1 MailBoxStore:Mail2 EDB:e: Exchsrvr mdbdata priv2.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr mdbdata priv2.stmadvancedcopy Manager Device:g1d1p1 PublicStore:Pub2 EDB:e: Exchsrvr pdbdata priv2.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr pdbdata priv2.stmadvancedcopy Manager Device:g1d1p1 TransactionLog=f: Exchsrvr log E00.logAdvancedCopy Manager Device:g1d2p1 CheckPointFile=e: Exchsrvr chk E00.chkAdvancedCopy Manager Device:g1d1p1 The command cannot display device information if: Device information has not been registered with the database information registration command (swstdbinfo_exchange). Not all storage group information is registered with AdvancedCopy Manager when an attempt is made to display information on all storage groups Exchange backup policy setting command (swstbkpolset_exchange) This command sets the backup policy (the number of generations to be saved and the number of interval days) for all transaction volumes that constitute a storage group. a. Specification method program-directory bin swstbkpolset_exchange [-sgname Storage-Group-Name] 202

206 [-i Interval-Days] [-s Save-Number] b. Description of options Option Description [-evs Virtual-Server-Name] -sgname -i -s Specifies the storage group name. If this option is omitted, a backup policy is set for all storage groups of Exchange Server. Specifies the number of interval days in the range from 1 to 366. If this option is omitted at the first registration, 30 are set. If the option is omitted at the time of updating, the current value is inherited. Specifies the number of generations to be saved in the range from 1 to 31. If this option is omitted at the first registration, 2 are set. If the option is omitted at the time of updating, the current value is inherited. -evs Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Set a backup policy for storage group FirstStorageGroup. C: >C: Win32app AdvancedCopyManager bin swstbkpolset_exchange -sgname FirstStorageGroup -i 7 -s 1 swstbkpolset_exchange successfully completed C: > The command cannot set a backup policy if: Data base information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). The database configuration of the specified group has been changed. Not all storage group information is registered with AdvancedCopy Manager when an attempt is made to set a backup policy for all storage groups. Even if the number of interval days is specified, Softek AdvancedCopy Manager does not automatically collect a backup. To backup a database, use the Exchange backup execution command (swstbackup_exchange). Before this command is entered to set a backup policy, as many backup volumes as necessary for operation in accordance with the specified backup policy must be defined. See Section 4.2.4," Preparing a backup volume"for the number of backup volumes needed for backup operation for normal transaction volumes. The number of generations to be saved can be changed if the current number of history information generations is equal to or less than the specified number of generations to be saved is satisfied. The command cannot set a backup policy if: As many backup volumes as necessary for the specified number of generations to be saved do not exist. The option specified for the number of generations to be saved exceeds the allowable range. The option specified for the number of interval days exceeds the allowable range. This command cannot be executed while one of the following commands is in execution: 203

207 Exchange database information registration command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command (swstsrsemtch) Resource backup command (swstresback) Resource restore command (swstresrst) Exchange backup policy deleting command (swstbkpoldel_exchange) This command deletes the policy of all devices that form the specified Storage group. a. Specification method program-directory bin swstbkpoldel_exchange -sgname Storage-Group-Name b. Description of options Option Description [-evs Virtual-Server-Name] -sgname Specifies the storage group name. -evs When MSCS employment is being performed, the name of an Exchange virtual server (EVS) is specified. When MSCS employment is omitted, there is no necessity for specification. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Delete the backup policy storage group FirstStorageGroup. C: >C: Win32app AdvancedCopyManager bin swstbkpoldel_exchange -sgname FirstStorageGroup swstbkpoldel_exchange successfully completed C: > The command cannot delete a backup policy if: Device information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). The database configuration of the specified storage group has been changed. Backup history information remains for the transaction volume to be deleted. This command cannot be executed while one of the following commands is in execution: Exchange database information setting command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) Exchange synchronous command (swststartsync_exchange) This command starts synchronous backup processing (EC/REC copying between volumes) for a storage group. a. Specification method program-directory bin swststartsync_exchange -sgname Storage-Group-Name [-Xdevmap Device-Map-File] b. Description of options Option Description [-evs Virtual-Server-Name] 204

208 -sgname -Xdevmap -evs Specifies the storage group name. Specifies that synchronous backup processing be started with a target backup volume specified. For the operand, specify the name of the device map file that defines the combinations of transaction volumes and target backup volumes. If this operation is not specified, the target backup volume is selected automatically. If this command is remotely executed with the -h option, specify the absolute path of the device map file on the storage server. The file name specified for Device-Map-File can include no national characters. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Start synchronous backup processing for storage group FirstStorageGroup. C: >C: Win32app AdvancedCopyManager bin swststartsync_exchange -sgname FirstStorageGroup swststartsync_exchange successfully completed C: > If this command is entered while synchronous backup processing is being executed for all transaction volumes in the storage group, the command ends with informational message swst4201 (the end status is normal end). 1. The command cannot start synchronous backup processing if: - Device information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). - The database configuration of the specified storage group has been changed. - History information on the specified storage group is inconsistent. - The specified device does not support the EC function. - A backup volume required for starting synchronous backup processing cannot be reserved. - OPC restoration is being performed for the specified device. - The target backup volume is mounted. 2. The command cannot start synchronous backup processing with a target backup volume specified if: - The backup volume defined as associated with a transaction volume in the device map file is not usable as the backup volume for the transaction volume, that is, neither of the following is satisfied: 1. The specified backup volume is in unused state. 2. The transaction volume and backup volume have the same partition size. - The statement about the applicable transaction volume in the device map file contains an error (see Section ,Statement in a device map file). - The device map file name includes a national character. This command cannot be executed while one of the following commands is in execution: Exchange database information setting command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) Exchange backup execution command (swstbackup_exchange) This command backs up the transaction volume to which the specified storage group is allocated. The command uses 205

209 the advanced copy function to copy the data in the original volume to the backup volume. a. Specification method program-directory bin swstbackup_exchange -sgname Storage-Group-Name [-Xdevmap Device-Map-File] b. Description of options Option Description [-evs Virtual-Server-Name] -sgname -Xdevmap Specifies the storage group name. Specifies that snapshot high-speed backup processing be performed with a target backup volume specified. For the operand, specify the name of the device map file that defines the combinations of transaction volumes and target backup volumes. If this operation is not specified, the target backup volume is selected automatically. If this command is remotely executed with the -h option, specify the absolute path of the device map file on the storage server. The file name specified for Device-Map-File can include no national characters. -evs Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Back up storage group FirstStorageGroup. C: >C: Win32App AdvancedCopyManager bin swstbackup_exchange -sgname FirstStorageGroup swstbackup_exchange successfully completed C: > This command carries out copying while maintaining the consistency of the file system. To do so, it arranges the transaction volume and backup volume so that they cannot be accessed from other processes and then starts backup processing. The command thus releases the device drive letter. If the drive letter of the transaction volume cannot be released or if the volume contains a file being used, the command terminates with an error. There is a file in use in volume. The transaction volume may be in use by a server other than the server through which this command is to be entered. If so, the backup administrator must at his or her own responsibility access-inhibit the transaction volume such as by canceling the setting for volume sharing. If the setting for sharing the transaction volume cannot be canceled for some reason, perform the following while referring to Appendix A,"Preprocessing and Postprocessing for Backup or Restoration". For backup preprocessing, execute a command (*1) that has a function equivalent to UNIX sync to synchronize between the transaction volume and file system. For backup postprocessing, execute the chkdsk command to check the backup volume file system (use the drive letter assignment command [swstdrvset] to assign a drive letter to the backup volume). (*1) For instance, the clearmem.exe command provided by "Microsoft Widows NT 4.0 Workstation Resource Kit (ISBN )" has a function equivalent to the sync command. (The customer should use the command at his or her own responsibility because this product does not support the command.) However, complete backup may not be achieved even with the above procedure. Therefore, Fujitsu recommends performing backup in an environment in which the transaction volume is not used by any other server than the one through which the command is entered. The command cannot achieve backup under the following conditions. If the command is entered under one of these conditions, take corrective action in accordance with [System administrator response] for the output message. 206

210 Database information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). The database configuration of the specified storage group has been changed. No backup policy has been set for the specified transaction volume. The backup operation executed one generation before failed. OPC is being executed for the specified transaction volume. The drive letter defined during registration of the transaction volume has been changed. Backup history information involving a generation overflow was used for restoration. An unused backup volume to be used as the target volume could not be reserved. One of the cabinet information items (cabinet identifier, OLU number, EXTENT start position, and EXTENT size) for the transaction volume has been changed. A drive letter has been assigned to the backup volume to be used as the target volume. Database data is inconsistent. Store dismounting failed. Store mounting failed. The command cannot execute backup processing with a target backup volume specified if: The backup volume defined as associated with a transaction volume in the device map file is not usable as the backup volume for the transaction volume, that is, neither of the following is satisfied: 1. The specified backup volume is in unused state. 2. The transaction volume and backup volume have the same partition size. The statement about the applicable transaction volume in the device map file contains an error (see Section ,"Statement in a device map file". The device map file name includes a national character. If an error occurs while a storage group consisting of multiple volumes is being processed, the command terminates processing immediately. If synchronous backup processing was performed, use the Exchange replication start command (swsrpstartsync_exchange) to resume interrupted synchronous processing. This command cannot be executed while one of the following commands is in execution: Exchange database information setting command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) Exchange data check command (swstchkdata_exchange) This command checks the consistency of the data in the storage group, and on the transaction volume. The command performs the following processing: The command checks data in the backup files existing in the backup volume having the latest backup history. 1. Checking EDB and STM files for signature matching (issuing ESEUTIL /MH to verify that "DB Signature" matches) 2. Checking data for consistency (issuing ESEUTIL /MH to verify that "State" matches "Last Consistent") If the dellog option is specified, the command deletes the log files having generation numbers smaller than the generation number of the log file that contains the last database match log obtained from the latest backup file. The command deletes these log files from the transaction volume. a. Specification method program-directory bin swstchkdata_exchange [-evs Virtual-Server-Name] b. Description of options Option Description [-dellog] -sgname Storage-Group-Name 207

211 -sgname -dellog -evs Specifies the storage group name. Specifies that the log files having generation numbers smaller than the generation number of the log file that contains the last match log obtained from the backup data in the backup volume be deleted. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Check the data in storage group FirstStorageGroup for consistency. C: >C: Program Files AdvancedCopyManager bin swstchkdata_exchange -dellog -sgname FirstStorageGroup swstchkdata_exchange successfully completed C: > This command terminates abnormally if: Database information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). The database configuration of the specified storage group has been changed. Backup history information does not exist. EDB and STM files are not found in the backup volume. The signatures in the EDB and STM files do not match. The EDB and STM files are inconsistent. No CHK file is found in the backup volume when the dellog option is specified. Log files earlier than the last match log cannot be deleted when the dellog option is specified. When the dellog option is specified to delete unnecessary log files, the command deletes log files one by one in descending order of generation number starting with "the generation number of the log file containing the last consistent log - 1". The command stops deletion processing if the log file having a generation number is not found. Thus, if the generation numbers of log files are not consecutive, not all unnecessary log files can be deleted. Execution example Suppose log files having generation numbers 1 to 9 exist and the generation number of the log file containing the last consistent log is 7. In this case, the log files having generation numbers 1 to 6 are normally deleted. However, if the log file having generation number 3 is missing, for example, only the log files having generation numbers 4 to 6 are deleted. E00.log (Generation No. 9) E log (Generation No. 8) E log (Generation No. 7) <--Log file containing the last consistent log E log (Generation No. 6) <--Deleted E log (Generation No. 5) <--Deleted E log (Generation No. 4) <--Deleted (E log) (Generation No. 3) <--Missing E log (Generation No. 2) <--Not deleted E log (Generation No. 1) <--Not deleted 208

212 The time required for consistency checking depends on the size of an Exchange database. The required time increases in proportion to the size of the database. This command cannot be executed while one of the following commands is in execution: Exchange database information setting command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) Exchange restore execution command (swstrestore_exchange) This command restores a storage group, and uses the restore execution command (swstrestore) to restore data from the backup volume and mounts the database. Two restore modes can be selected: +Point-in-time restoration (restoration to the state at the time of backup) The point-in-time restoration restores a database to the state it was in immediately before it was backed up. Thus any data that has been created after backup is not incorporated into the restored database. +Roll-forward restoration (restoration to the latest state) The roll-forward restoration restores a database to the state it was in immediately before it was backed up and then incorporates data that has been created after backup into the database to restore it to the latest state. This restore mode cannot be used if a circular logging is used. a. Specification method program-directory bin swstrestore_exchange -sgname Storage-Group-Name (-point -roll) [-g Generation-Number -v Version-Number] b. Description of options Option Description [-evs Virtual-Server-Name] -sgname -point -roll -g -v Specifies the storage group name. Specifies that restoration be performed in point-in-time mode. Specifies that restoration be performed in roll-forward mode. Specifies the relative generation number of data to be restored. Use the history information display command (swsthistdisp_exchange) to check the relative generation number. Specifies the absolute generation number of data to be restored. Use the history information display command (swsthistdisp_exchange) to check the absolute generation number. -evs Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Restore storage group FirstStorageGroup from the latest backup history in roll-forward mode. C: >C: Win32App AdvancedCopyManager bin swstrestore_exchange -roll -sgname FirstStorageGroup swstrestore_exchange successfully completed 209

213 C: > The command cannot achieve restoration if: Database information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). The database configuration of the specified storage group has been changed. If physical volume information (cabinet identifier, OLU, EXTENT start position, and EXTENT size) has been changed since the start of operation, the operation for the relevant volume cannot be continued. Stop replication operation for the relevant volume and then delete and set replication volume information. The drive letter defined during registration of the transaction volume has been changed. Backup history information is inconsistent. Synchronous backup processing is being executed. Database data is inconsistent. Store dismounting failed. Store mounting failed. The log file exists in the same volume as the database file (EDB/STM file) when the roll option is specified. A drive letter or mount point is assigned to the backup volume when the roll option is specified. Log file numbers are not consecutive when the roll option is specified. When the roll option is specified and the circular logging option is enabled. This command cannot be executed while one of the following commands is in execution: Exchange database information setting command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) Exchange history display command (swsthistdisp_exchange) This command displays history information on a storage group. a. Specification method [To display history information on a specific storage group] program-directory bin swsthistdisp_exchange -sgname Storage-Group-Name [To display history information on all storage groups used for Exchange] program-directory bin swsthistdisp_exchange [-evs Virtual-Server-Name] b. Description of options Option Description -sgname Specifies the storage group name. If this option is omitted, history information on all storage groups is displayed. -evs Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Display backup history information on storage group FirstStorageGroup. C: >C: Win32App AdvancedCopyManager bin swsthistdisp_exchange -sgname FirstStorageGroup Exchange Storage Group:FirstStorageGroup 210

214 Generation Version Backup-Date Transaction-Device /12/01 22:00 g1d1p1 Mount-Point=E: (NTFS) /12/01 22:00 g1d2p1 Mount-Point=F: (NTFS) Server=EXCHG-SVR Device=g1d1p1 Mount-Point=E: (NTFS) Generation Version Backup-Date Backup-Disk Status Execute /12/01 22:00 g1d11p1 succeeded ---- Server=EXCHG-SVR Device=g1d2p1 Mount-Point=F: (NTFS) Generation Version Backup-Date Backup-Disk Status Execute /12/01 22:00 g1d12p1 succeeded ---- C: > The information items that are displayed are explained below: Keyword Server Device Mount-Point Generation Version Backup-Date Backup-Disk Status Execute Description Displays the storage server name. Displays the AdvancedCopy Manager device name Displays the drive letter of a device. The file system type of the device is displayed in parentheses. Displays the relative generation number. Not displayed if backup history information does not exist. Displays the absolute generation number. Not displayed if backup history information does not exist. Displays the time/date of completion of backup. Not displayed if backup history information does not exist. Displays the name of the backed-up volume. Not displayed if backup history information does not exist. Displays one of the following character strings, each indicating the execution status of real copying: "succeeded": OPC copying is complete. "executing": OPC copying is in execution. "failed": OPC copying was interrupted by an error. "halt": OPC copying is in halt state. Not displayed if backup history information does not exist. Displays the progress of copying in percentage when Status is "executing." Displays "----" when Status is something other than "executing." Not displayed if backup history information does not exist. The command cannot display history information if: Database information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). Not all storage group information has been registered with AdvancedCopy Manager when an attempt is made to display all storage group information. A hardware error may have occurred if the status is "failed" or "halt". Remove the hardware error cause and then enter 211

215 the history deletion command (swsthistdel) to delete backup history information Exchange synchronous processing cancellation command (swstcanc elsync_exchange) This command cancels synchronous backup processing for a storage group. If an error is detected during synchronous backup processing, copying does not end normally. In this case, use this command to cancel synchronous backup processing. Use the Backup synchronous processing progress display command(swstsyncstat) to check for errors. a. Specification method program-directory bin swstcancelsync_exchange -sgname Storage-Group-Name b. Description of options Option -sgname Description Specifies the storage group name. If this option is omitted, history information on all storage groups is displayed. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Cancel synchronous backup processing for storage group FirstStorageGroup. C: >C: Win32app AdvancedCopyManager bin swstcancelsync_exchange -sgname FirstStorageGroup swstcancelsync_exchange successfully completed C: > This command cannot be executed while one of the following commands is in execution: Exchange database information setting command (swstdbinfo_exchange) Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) Replication management function commands Exchange database information registration command (swsrpdbinfo_e xchange) This command registers or deletes information on a storage group. The command is used when Exchange Server backup operation begins or after the file configuration of a storage group is changed. Executing the command registers or deletes information on the files that constitute a storage group and information on AdvancedCopy Manager device names. (The files that constitute a storage group include mailbox store and public folder store database files, transaction files, and checkpoint file.) a. Specification method [To register Exchange database information] program-directory bin swsrpdbinfo_exchange [-evs Virtual-Server-Name] [-sgname Storage-Group-Name] [To delete Exchange database information] program-directory bin swsrpdbinfo_exchange [-evs Virtual-Server-Name] -clean b. Description of options Option Description -sgname Specifies the storage group name. 212

216 If this option is omitted, information on all storage groups is registered. -clean Specifies that information on the storage group that has been deleted from Exchange Server be deleted. -evs Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Register storage group FirstStorageGroup. C: >C: Win32App AdvancedCopyManager bin swsrpdbinfo_exchange -sgname FirstStorageGroup swsrpdbinfo_exchange successfully completed C: > Delete unnecessary storage group information. C: >C: Win32App AdvancedCopyManager bin swsrpdbinfo_exchange -clean swsrpdbinfo_exchange successfully completed C: > The command cannot register database information if: The specified storage group does not exist. This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swsrpdbinfo_exchange) Exchange replication start command (swsrpstartsync_exchange) Exchange backup execution command (swsrpbackup_exchange) Exchange data check command(swsrpchkdata_exchange) Exchange restore execution command (swsrpretore_exchange) Exchange cancellation Sync command (swsrpcancel_exchange) Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Synchronous processing start command (swsrpstartsync) Replication creation command (swsrpmake) Replication cancellation command (swsrpcancel) Resource adjustment command (swsrprecoverres) Exchange device display command (swsrpdevdisp_exchange) This command displays the information registered with the Exchange database information registration command (swsrpdbinfo_exchange). The command displays information on the files that constitute a storage group and information on AdvancedCopy Manager device names. (The files that constitute a storage group include mailbox store and public folder store database files, transaction files, and checkpoint file.) a. Specification method [To display information on a specific storage group] program-directory bin swsrpdevdisp_exchange -sgname Storage-Group-Name [To display information on all storage groups used for Exchange] program-directory bin swsrpdevdisp_exchange [-evs Virtual-Server-Name] b. Description of options Option Description -sgname Specifies the storage group name. 213

217 -evs If this option is omitted, information on all storage groups is displayed. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Display device information on storage group FirstStorageGroup. C: >C: Win32app AdvancedCopyManager bin swsrpdevdisp_exchange -sgname FirstStorageGroup Exchange Storage Group:FirstStorageGroup MailBoxStore:Mail1 EDB:e: Exchsrvr mdbdata priv1.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr mdbdata priv1.stmadvancedcopy Manager Device:g1d1p1 PublicStore:Pub1 EDB:e: Exchsrvr pdbdata priv1.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr pdbdata priv1.stmadvancedcopy Manager Device:g1d1p1 MailBoxStore:Mail2 EDB:e: Exchsrvr mdbdata priv2.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr mdbdata priv2.stmadvancedcopy Manager Device:g1d1p1 PublicStore:Pub2 EDB:e: Exchsrvr pdbdata priv2.edbadvancedcopy Manager Device:g1d1p1 STM:e: Exchsrvr pdbdata priv2.stmadvancedcopy Manager Device:g1d1p1 TransactionLog=f: Exchsrvr log E00.logAdvancedCopy Manager Device:g1d2p1 CheckPointFile=e: Exchsrvr chk E00.chkAdvancedCopy Manager Device:g1d1p1 The command cannot display device information if: Device information has not been registered with the database information registration command (swsrpdbinfo_exchange). Not all storage group information is registered with AdvancedCopy Manager when an attempt is made to display information on all storage groups. This command cannot be executed while the following command is in execution: Resource adjustment command(swsrprecoverres) Exchange replication start command (swsrpstartsync_exchange) This command starts synchronous replication processing (EC/REC copying between volumes) for a storage group. The command executes total copying (start of synchronous processing) or update copying (differential copying) (restart of synchronous processing) between the original and replica volumes specified in the device map file. The command is used to reflect data that has been updated since the start of operation or the state of replication establishment (differential data). a. Specification method program-directory bin swsrpstartsync_exchange [-y] [-t] [-m] [-evs Virtual-Server-Name] -Xdevmap Device-Map-File 214

218 b. Description of options Option Description -sgname Storage-Group-Name -sgname -Xdevmap -evs -y -m Specifies the storage group name. Specifies the name of the device map file that defines the combinations of storage group volumes and target backup volumes. Specify the absolute path of the device map file. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. Specifies that synchronous processing be started in synchronous write mode (data is copied to the target volume in synchronization with a write to the master volume). This option is valid only for starting total copying for replication between cabinets. If this option is not specified, synchronous processing is performed in asynchronous write mode (data is copied to the target volume independent of a write to the master volume). Synchronous processing for replication between cabinets is always performed in synchronous write mode. If multiple volumes are subject to synchronous processing, this option applies only to the synchronous processing volumes for replication between cabinets. This option cannot be specified if the volumes subject to synchronous processing are all for replication between cabinets. Specifies that communication with the backup server (non-operating server) not be performed in backup server operation mode (replication between servers). If this option is specified, the command does not perform volume status checking and preprocessing and postprocessing for the backup volume. This option is valid only in backup server operation mode. If multiple volumes are subject to synchronous processing, this option applies only to the synchronous processing volumes for replication between servers. This option cannot be specified if the volumes subject to synchronous processing are all for replication between servers. -t Specifies that preprocessing not be performed for the backup volume (target volume). If multiple volumes are subject to synchronous processing, this option applies to all these volumes. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Start synchronous processing for storage group FirstStorageGroup. Assume that the device map file that defines the associations between transaction volumes (storage group volumes) and backup volumes is K: STG DEV.map. C: >C: Win32App AdvancedCopyManager bin swsrpstartsync_exchange -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpstartsync_exchange successfully completed C: > If this command is entered while synchronous backup processing is being executed for all transaction volumes in the storage group, the command ends with informational message swsrp4201 (the end status is normal end). 215

219 The command cannot start synchronous backup processing if: Device information on the specified storage group has not been registered with the Exchange database information registration command (swsrpdbinfo_exchange). The database configuration of the specified storage group has been changed. The specified device map file does not exist. The statement in the device map file contains an error (see "Preparing a device map file"). A valid combination of the database volume and target backup volume is not found in the device map file. The database volume and backup volume defined in the device map file are not registered respectively as an original volume and replica volume. The y option is specified while all original and replica volumes are located in the same cabinet. The y option is specified while synchronous processing is performed for original and replica volumes located in different cabinets. If physical volume information (cabinet identifier, OLU, EXTENT start position, and EXTENT size) has been changed since the start of operation, the operation for the relevant volume cannot be continued. Stop replication operation for the relevant volume and then delete and set replication volume information. The backup volume has multiple mount points (Windows 2000 only). The m option is specified when all backup volumes are located on the same server as Exchange Server. The storage server on which the command is executed is not an operating server for the replication volume in backup server operation mode (replication between servers). Communication with the remote server fails in backup server operation mode (replication between servers). If the backup operation to be performed meets one of the following conditions, remove the drive letter of the backup volume or unmount the backup volume before command execution. Copying is performed between different operating systems. The database volume and backup volume have different sizes. If the drive letter is not removed or the backup volume is not unmounted in advance, postprocessing for the backup volume results in an error during backup operation. If an error occurs while a storage group consisting of multiple volumes is being processed, the command terminates processing immediately. Synchronous processing that was started before the error occurrence is not terminated. To restart synchronous processing for the storage group, remove the error cause and reexecute this command. This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swsrpdbinfo_exchange) Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) Exchange backup execution command (swsrpbackup_exchange) This command backs up the transaction volume to which the specified storage group is allocated. The command uses the advanced copy function to copy the data in the volume to be backed up to the backup volume. a. Specification method program-directory bin swsrpbackup_exchange [-f] [-t] [-m] [-evs Virtual-Server-Name] -Xdevmap Device-Map-File b. Description of options Option Description -sgname Storage-Group-Name -sgname -Xdevmap Specifies the storage group name. Specifies the name of the device map file that defines the combinations of storage group volumes and target backup volumes. Specify the absolute 216

220 -evs -m -f -t path of the device map file. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. Specifies that communication with the backup server (non-operating server) not be performed in backup server operation mode (replication between servers). If this option is specified, the command does not perform volume status checking and preprocessing and postprocessing for the backup volume. This option is valid only in backup server operation mode. If multiple volumes are subject to synchronous processing, this option applies only to the synchronous processing volumes for replication between servers. This option cannot be specified if the volumes subject to synchronous processing are all for replication between servers. Specifies that preprocessing and postprocessing not be performed for the transaction volume (original volume). If multiple volumes are subject to synchronous processing, this option applies to all these volumes. Specifies that preprocessing not be performed for the backup volume (replica volume). If multiple volumes are subject to synchronous processing, this option applies to all these volumes. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Back up storage group FirstStorageGroup. Assume that the device map file that defines the associations between transaction volumes (storage group volumes) and backup volumes is K: STG DEV.map. C: >C: Win32App AdvancedCopyManager bin swsrpbackup_exchange -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpbackup_exchange successfully completed C: > The command cannot execute backup processing if: Device information on the specified storage group has not been registered with the Exchange database information registration command (swsrpdbinfo_exchange). The database configuration of the specified storage group has been changed. The specified device map file does not exist. The statement in the device map file contains an error (see "Preparing a device map file"). A valid combination of the database volume and target backup volume is not found in the device map file. The database volume and backup volume defined in the device map file are not registered respectively as an original volume and replica volume. Synchronous processing for the database volume and backup volume defined in the device map file is not in the state of equivalency. If physical volume information (cabinet identifier, OLU, EXTENT start position, and EXTENT size) has been changed since the start of operation, the operation for the relevant volume cannot be continued. Stop replication operation for the relevant volume and then delete and set replication volume information. The transaction volume or backup volume has multiple mount points (Windows 2000 only). The m option is specified when all backup volumes are located on the same server as Exchange Server. The storage server on which the command is executed is not an operating server for the replication volume in backup server operation mode (replication between servers). Communication with the remote server fails in backup server operation mode (replication between servers). Database data is inconsistent. Store dismounting failed. Store mounting failed. 217

221 If the backup operation to be performed meets one of the following conditions, remove the drive letter of the backup volume or unmount the backup volume before command execution. Copying is performed between different operating systems. The database volume and backup volume have different sizes. If the drive letter is not removed or the backup volume is not unmounted in advance, postprocessing for the backup volume results in an error during backup operation. Before creating a replica volume, execute replication preprocessing and postprocessing scripts for the original volume (in the case of synchronous replication, execute only the postprocessing script). After creating a replica volume, execute the replication postprocessing script for the original and replica volumes. The scripts can be customized. For more information, refer to Appendix D, "Replication Scripts," in the Operator's Guide. The -f and -t options can be used to prevent preprocessing and postprocessing from being executed. If this command is executed during snapshot copy operation, the command stops the current copy operation and starts another copy operation. If an error occurs while a storage group consisting of multiple volumes is being processed, the command terminates processing immediately. If synchronous backup processing was performed, use the Exchange replication start command (swsrpstartsync_exchange) to resume interrupted synchronous processing. To guarantee data, this command creates a replica while protecting the original volume from being accessed from other processes. To do so, the command removes the drive letter of the original volume or unmounts the volume. If one of the following conditions under which the drive letter of the original volume cannot be removed or the volume cannot be unmounted is met, the command terminates with an error: A directory used to mount another volume exists under the mount point. The volume contains a file in use. The original volume may be in use by a server other than the server through which this command is to be entered. If so, the backup administrator must at his or her own responsibility access-inhibit the original volume such as by canceling the setting for volume sharing or unmounting the volume. If the setting for sharing the transaction volume cannot be canceled or the volume cannot be unmounted for some reason, perform the following while referring to Appendix D, "Replication Scripts." The original volume may not be unmounted when it is used by backup management. In this case, "swsrp2613: An error occurred in the preprocessing script for replica creation. Error code = 2" is output. For replication preprocessing, execute a command that has a function equivalent to UNIX sync to synchronize between the volume and file system. For instance, the clearmem.exe command provided by "Microsoft Widows NT 4.0 Workstation Resource Kit (ISBN )" has a function equivalent to the sync command. (The customer should use the command at his or her own responsibility because this product does not support the command.) For replication postprocessing, execute the chkdsk command to check the target file system (use the drive letter assignment command [swstdrvset] to assign a drive letter to the replica volume). This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swsrpdbinfo_exchange) Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) 218

222 Exchange data check command (swsrpchkdata_exchange) This command checks the consistency of the data in the storage group, and on the transaction volume. The command performs the following processing: The command checks data in the backup files existing in the backup volume specified in the device map file. 1. Checking EDB/STM files for signature matching (issuing ESEUTIL /MH to verify that "DB Signature" matches) 2. Checking data for consistency (issuing ESEUTIL /MH to verify that "State" matches "Last Consistent") If the dellog option is specified, the command deletes the log files having generation numbers smaller than the generation number of the log file that contains the last database match log obtained from the backup file. The command deletes these log files from the transaction volume. a. Specification method program-directory bin swsrpchkdata_exchange [-evs Virtual-Server-Name] b. Description of options Option Description [-dellog] -Xdevmap Device-Map-File -sgname Storage-Group-Name -sgname -Xdevmap -evs Specifies the storage group name. Specifies the name of the device map file that defines the combinations of storage group volumes and target backup volumes. Specify the absolute path of the device map file. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. -dellog Specifies that the log files having generation numbers smaller than the generation number of the log file that contains the last match log obtained from the backup data in the backup volume be deleted. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Check the data in storage group FirstStorageGroup for consistency. Assume that the device map file that defines the associations between transaction volumes (storage group volumes) and backup volumes is K: STG DEV.map. C: >C: Program Files AdvancedCopyManager bin swsrpchkdata_exchange -dellog -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpchkdata_exchange successfully completed C: > The command terminates abnormally if: Database information on the specified storage group has not been registered with the Exchange database information registration command (swstdbinfo_exchange). The database volume and backup volume defined in the device map file are not registered respectively as an original volume and replica volume. The database configuration of the specified storage group has been changed. The signatures in the EDB and STM files do not match. The EDB and STM files are inconsistent. No CHK file is found in the backup volume when the dellog option is specified. Log files earlier than the last match log cannot be deleted when the dellog option is specified. When deletion of the log file before the last adjustment log is not completed (at the time of dellog option specification). The Exchange system management tool is not installed on the backup server in backup server operation mode. 219

223 Communication with the remote server failed in backup server operation mode (replication between servers). When the dellog option is specified to delete unnecessary log files, the command deletes log files one by one in descending order of generation number starting with "the generation number of the log file containing the last consistent log - 1". The command stops deletion processing if the log file corresponding to a generation number is not found. Thus, if the generation numbers of log files are not consecutive, not all unnecessary log files can be deleted. Execution example Suppose log files having generation numbers 1 to 9 exist and the generation number of the log file containing the last consistent log is 7. In this case, the log files having generation numbers 1 to 6 are normally deleted. However, if the log file having generation number 3 is missing, for example, only the log files having generation numbers 4 to 6 are deleted. E00.log (Generation No. 9) E log (Generation No. 8) E log (Generation No. 7) <--Log file containing the last consistent log E log (Generation No. 6) <--Deleted E log (Generation No. 5) <--Deleted E log (Generation No. 4) <--Deleted (E log) (Generation No. 3) <--Missing E log (Generation No. 2) <--Not deleted E log (Generation No. 1) <--Not deleted The time required for consistency checking depends on the size of an Exchange database. The required time increases in proportion to the size of the database. This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swsrpdbinfo_exchange) Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) Exchange restore execution command (swsrprestore_exchange) This command restores the specified storage group, and uses the replication creation command (swsrpmake) to restore data from the backup volume and mounts the database. Two restore modes can be selected: +Point-in-time restoration (restoration to the state at the time of backup) The point-in-time restoration restores a database to the state it was in immediately before it was backed up. Thus, any data that has been created after backup is not incorporated into the restored database. +Roll-forward restoration (restoration to the latest state) The roll-forward restoration restores a database to the state it was in immediately before it was backed up and then incorporates data that has been created after backup into the database to restore it to the latest state. This restore mode cannot be used if a circular logging is used. a. Specification method program-directory bin swsrprestore_exchange [-f] [-t] [-m] [-evs Virtual-Server-Name] 220

224 (-point -roll) -Xdevmap Device-Map-File b. Description of options Option Description -sgname Storage-Group-Name -sgname -Xdevmap -evs -point -roll -m Specifies the storage group name. Specifies the name of the device map file that defines the combinations of storage group volumes and target backup volumes. Specify the absolute path of the device map file. Specifies the name of an Exchange virtual server (EVS) when MSCS operation is used. Need not be specified unless MSCS operation is used. Specifies that restoration be performed in point-in-time mode. Specifies that restoration be performed in roll-forward mode. Specifies that communication with the backup server (non-operating server) not be performed in backup server operation mode (replication between servers). If this option is specified, the command does not perform data consistency checking during roll-forward restoration, volume status checking, and preprocessing and postprocessing for the backup volume. This option is valid only in backup server operation mode. * This option is not open to users. -f Specifies that preprocessing and postprocessing not be performed for the backup volume (original volume). If multiple volumes are subject to synchronous processing, this option applies to all these volumes. -t Specifies that preprocessing not be performed for the transaction volume (replica volume). If multiple volumes are subject to synchronous processing, this option applies to all these volumes. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Restore storage group FirstStorageGroup in roll-forward restore mode. Assume that the device map file that defines the associations between transaction volumes (storage group volumes) and backup volumes is K: STG DEV.map. C: >C: Win32App AdvancedCopyManager bin swsrprestore_exchange -roll -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrprestore_exchange successfully completed C: > This command cannot execute restore processing if: Database information on the specified storage group has not been registered with the Exchange database information registration command (swsrpdbinfo_exchange). The database configuration of the specified storage group has been changed. The specified device map file does not exist. The statement in the device map file contains an error (see "Preparing a device map file"). A valid combination of the database volume and target backup volume is not found in the device map file. The database volume and backup volume defined in the device map file are not registered respectively as an original volume and replica volume. Synchronous processing for the database volume and backup volume defined in the device map file is not in 221

225 the state of equivalency. If physical volume information (cabinet identifier, OLU, EXTENT start position, and EXTENT size) has been changed since the start of operation, the operation for the relevant volume cannot be continued. Stop replication operation for the relevant volume and then delete and set replication volume information. The transaction volume or backup volume has multiple mount points (Windows 2000 only). The m option is specified when all backup volumes are located on the same server as Exchange Server. The storage server on which the command is executed is not an operating server for the replication volume in backup server operation mode (replication between servers). Communication with the remote server fails in backup server operation mode (replication between servers). Database data is inconsistent. Store dismounting failed. Store mounting failed. The log file exists in the same volume as the database file (EDB/STM file) when the roll option is specified. The transaction log required for roll-forward is not found in the log file when the roll option is specified. Log file numbers are not consecutive when the roll option is specified. When the roll option is specified and the circular logging option is enabled. If the backup operation to be performed meets one of the following conditions, remove the drive letter of the backup volume or unmount the backup volume before command execution. Copying is performed between different operating systems. The database volume and backup volume have different sizes. If the drive letter is not removed or the backup volume is not unmounted in advance, postprocessing for the backup volume results in an error during backup operation. If this command is executed during snapshot copy operation, the command stops the current copy operation and starts another copy operation. This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swsrpdbinfo_exchange) Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) Exchange operation status display command (swsrpstat_exchage) This command displays the operation status of the specified storage group. a. Specification method program-directory bin swsrpstat_exchange [-Xdevmap Device-Map-File ] b. Description of options Option Description -sgname Storage-Group-Name -sgname Specifies the storage group name Xdevmap c. End status = 0: Normal end > 0: Abnormal end d. Execution example Specifies the name of the device map file that defines the combinations of storage group volumes and target backup volumes. Specify the absolute path of the device map file. If this option is omitted, the operation status of all replication volumes in the specified storage group is displayed.

226 Display the operation status of storage group FirstStorageGroup. Assume that the device map file that defines the associations between transaction volumes (storage group volumes) and backup volumes is K: STG DEV.map. C: > C: Win32App AdvancedCopyManager bin swsrpstat_exchange -Xdevmap K: STG DEV.map -sgname FirstStorgeGroup Server Original-Volume Replica-Volume Direction Status Execute EXCHG-SVR regular equivalent 100% EXCHG-SVR regular sync 83% C: > See the description about the operation status display command (swsrpstat) for display information and notes. Take corrective action as necessary when the execution status (displayed in the "Status" column) is one of the following: Status failed halt????? Corrective action A hardware error occurred. Remove the hardware error cause and use the replication cancellation command to stop operation. A hardware error occurred during replication between cabinets. Remove the hardware error cause and use the replication cancellation command to stop operation. Copy information could not be obtained. If the same symptom results even after reexecution, a hardware error occurred. Remove the hardware error cause and reexecute the command. The command cannot display the operation status if: The specified original or replica volume is not defined as a replication volume. This command cannot be executed while the following command is in execution: Resource adjustment command (swsrprecoverres) Exchange replication cancellation command (swsrpcancel_exchange) This command stops snapshot processing (OPC) or synchronous processing (EC) for the specified storage group. Use the command to stop replication processing such as when an error is detected during replication. a. Specification method program-directory bin swsrpcancel_exchange [-reverse] -Xdevmap Device-Map-File b. Description of options Option Description -sgname Storage-Group-Name -sgname -Xdevmap Specifies the storage group name. Specifies the name of the device map file that defines the combinations of storage group volumes and target backup volumes. Specify the absolute path of the device map file. 223

227 -reverse Specifies that processing for copying from the backup volume to the transaction volume be stopped. Do not use this option to stop processing for copying from the transaction volume to the backup volume. c. End status = 0: Normal end > 0: Abnormal end d. Execution example Cancel replication of storage group FirstStorageGroup. Assume that the device map file that defines the associations between transaction volumes (storage group volumes) and backup volumes is K: STG DEV.map. C: >C: Win32App AdvancedCopyManager bin swsrpcancel_exchange -Xdevmap K: STG DEV.map -sgname FirstStorageGroup swsrpcancel_exchange successfully completed C: > This command cannot execute restore processing if: Database information on the specified storage group has not been registered with the Exchange database information registration command (swsrpdbinfo_exchange). The specified device map file does not exist. The statement in the device map file contains an error (see "Preparing a device map file"). A valid combination of the database volume and target backup volume is not found in the device map file. The database volume and backup volume defined in the device map file are not registered respectively as an original volume and replica volume. The direction of copy processing for all original and replica volumes is different from the specified direction. The storage server on which the command is executed is not an operating server for the replication volume in replication between servers. Communication with the remote server fails in backup server operation mode (replication between servers). The command does not check the volume information on the specified volume (does not check whether the volume information in the management data set matches actual physical information). The command unconditionally cancels the operation by using the volume information in the management data set. If an error occurs while a database consisting of multiple volumes is being processed, the command terminates processing immediately. If synchronous backup processing was performed, remove the error cause and then use this command or the Exchange replication cancellation command (swsrpcancel) to stop the copy processing that remained unstopped. This command stops copy processing only in the specified direction. The command performs processing depending on the operation statuses of the specified original volume and target volume as shown below: Operation status Copying in reversed direction Not operating Total or differential copying in execution Processing Interrupts processing. Interrupts processing. Stops synchronous processing. The target volume cannot be used. 224

228 State of equivalence Replication established Snapshot processing Stops synchronous processing. The target volume cannot be used. Stops synchronous processing. The target volume can be used as a replica. Stops snapshot processing. The target volume cannot be used. Unlike the replication cancellation command (swsrpcancel), this command does not guarantee database consistency even if the command is executed while the synchronous process is in the state of equivalence. To collect backup data and stop synchronous processing simultaneously, execute this command after executing the Exchange backup execution command. This command cannot be executed while one of the following commands is in execution: Exchange database information registration command (swsrpdbinfo_exchange) Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) 10.6 SQL Server Commands This chapter explains the commands by which the backup and restore of SQL Server databases are performed. It is necessary to execute a SQL Server cooperation command by the user belonging to the Administrators group. The commands used by the backup management function and the replication management function are different. Refer to when you use the backup management function. Refer to when you use the replication management function Backup Management Commands Swstbackup_sqlsvr and swstrestore_sqlsvr are used in the backup operation of SQL Server by the backup management function SQL Server backup execution command (swstbackup_sqlsvr) This command backs up SQL Server 2000 databases. This command, in cooperation with SQL Server 2000, performs copy of data of the target database volumes on to backup volumes by executing the backup execution command (swstbackup). The database backup history information will be stored in msdb of SQL Server The database volume backup history information will be stored in the management files of Softek AdvancedCopy Manager. a. Specification method program-directory bin swstbackup_sqlsvr [-Xserver Server-Name] [-Xinstance Instance-Name] [-Xdevmap Device-Map-File] b. Description of options Option Description DB-Name-1 DB-Name-2 DB-Name-i -Xserver -Xinstance Specifies the virtual server name of connected SQL Server in case of operation by MSCS. In case of operation without MSCS, this option need not be specified. Specifies a connection instance. Specify an instance name in the 225

229 operand. If this option is not specified, connection will be made to the default instance. -Xdevmap Specifies to perform the backup to the specified backup volume. Specify a device map file name that describes combinations of database volumes and destination backup volumes. If this option is not specified, the target backup volume will be automatically selected. Specify a device map file name using an absolute pathname. c. Description of operand Operand DB-Name DB-Name-i (i=1,2,,,,64) Description Specifies database names. Delimit by the half-size blank or the tab character and specify the database names when you specify two or more databases. 65 data base names or more cannot be specified. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Backup the databases DB01, DB02, and DB03 of virtual server VSERVER. (Suppose that the logical node name of AdvancedCopy Manager is nodeagt.) C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstbackup_sqlsvr -Xserver VSERVER DB01 DB02 DB03 DB01 DB02 DB03 swstbackup_sqlsvr completed C: > Backup the databases (DB01, DB02 and DB03) specifying the destination backup volumes by the device map file (G: STGADM devmap.txt). C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swstbackup_sqlsvr -Xserver VSERVER -Xdevmap G: STGADM DEV.map DB01 DB02 DB03 DB01 DB02 DB03 swstbackup_sqlsvr completed C: > This command backs up database volumes on which database files are placed using the backup execution command (swstbackup). The backup execution command release the drive letter of the database volume according to the preprocessing script, performs backup, and then reassigns the drive letter according to the post-processing script. No drive letter can be released from a database volume on which SQL Server database files are placed because they are used for SQL Server. Thus, customize the backup preprocessing script to disable the release of a drive letter from a volume on which an SQL Server database files are placed. For information on customization, see chapter "Changing a backup preprocessing script". You cannot perform backup in the following cases: A specified database does not exist. (This case includes the case where neither the virtual server nor the instance exists.) In the case of specifying two or more databases, all of the specified databases are not databases of the same instance. (In the case where Xinstance option is not used, the processing is done to the default instance. In the case where Xinstance option is used, the processing is done to the specified named instance.) A volume where the specified database is placed is not registered as a transaction volume. Backup policy is not set for a database volume to be backed up. Backup executed one generation earlier was unsuccessful. The drive letter specified when the transaction volume was registered has been changed. Restore is being performed using backup history information that will cause a generation overflow. No unused backup volume to be used as the copy destination could be acquired. 226

230 A drive letter has been assigned to a backup volume to be used as the copy destination. The synchronous processing between the database volumes and the backup volumes is not in equivalency holding state. After operation is begun, any of physical information (box identifier, OLU number, EXTENT start position, and EXTENT size) of a volume has been changed. A database volume has plural mount points. (Only Windows 2000) If a database volume is an SDX object (SynfinityDISK), the state of the SDX object is not in the following states: 1. The mirror volume is ACTIVE or STOP. 2. The mirror slices are ACTIVE or STOP. 3. The state of SDX Disk is ENABLE. If a database volume is an SDX object (SynfinityDISK) on Windows 2000, the auto mounting function of the SDX object is ON. 65 databases or more are specified. You cannot specify a destination backup volume and perform backup if: A backup volume specified in a device map file cannot be used as the destination backup volume for a corresponding database volume. In other words, not all the following conditions are met. 1. The specified backup volume is unused. 2. The database volume and the backup volume have the same partition size. The description on a target database volume of the device map file has an error. If this command is executed during execution of snapshot processing, stop the copy processing in progress and start the snapshot processing again. This command provides the function to back up two or more databases at the same time by specifying the operand. When, like two or more databases exist on one partition, physical files of plural databases exist together on volumes, perform the backup of all the databases which exist on the volumes by using this function. This command makes all the databases specified in operand to be frozen by SQL Server 2000 until backup processing is completed. Thus, if the volumes where database files exist are independent in each database, back up each database two or more times to shorten the frozen time as much as possible. Now, the advanced copy which makes a SDX object (SynfinityDISK) backup volume is not supported. Therefore, only the advanced copy from a database volume which is an SDX object to a backup volume which is a non-sdx object can be used. Use the COPY command, in case you copy data to a SDX object. Because processing of securing data consistency for database volumes when the backup is performed is done by SQL Server 2000, the preprocessing and postprocessing (drive letter release and reassignment) like a usual file system volume are not executed. If an error occurs while SQL Server backup execution command (swsrpbackup_sql) is processing the database of two or more volumes composition with this command, processing is interrupted. When you perform synchronous type backup, restart stopped synchronous processing by using the backup synchronous processing start command (swststartsync). 227

231 If an error occurs while SQL Server backup execution command (swstbackup_sqlsvr) is processing the database of two or more volumes composition with the backup execution command (swstbackup), the backup history information on Softek AdvancedCopy Manager may become inconsistent. In order to cancel such an inconsistent state, delete unnecessary history information using a history information deletion command (swsthistdel). This command can be executed only while none of the following commands are running. Storage server configuration information setting command (swstsvrset) Device information setting command (swstdevinfoset) Resource match command(swstsrsemtch) Resource backup command(swstresback) Resource restore command(swstresrst) SQL Server restore execution command (swstrestore_sqlsvr) This command restores an SQL Server 2000 database. Enter this command after restoring database files using the restore execution command (swstrestore).this command recreates a database from restored database files. To perform recovery, after this command is executed, apply logs using Enterprise Manager or Transact-SQL. a. Specification method program-directory bin swstrestore_sqlsvr [-Xserver Server-Name] [-Xinstance Instance-Name] [-Xnolog] -Xmeta Meta-File-Name b. Description of options Option Description DB-Name 228

232 -Xserver -Xinstance -Xnolog -Xmeta Specifies the virtual server name of connected SQL Server in case of operation by MSCS. In case of operation without MSCS, this option need not be specified. Specifies a connection instance. Specify an instance name in the operand. If this option is not specified, connection will be made to the default instance. Specifies to restore a DB to a backup point, without applying logs. If this option is not specified, the DB will be restored to a backup point but cannot be used until logs are applied to it. Apply logs using Enterprise Manager or Transact-SQL. Specifies a meta data file name, using an absolute pathname. A meta data file will be stored as "db-name.swst-dmp" in the same folder as the primary data file. To confirm file identification numbers of database files, use the Transact-SQL "USE DB-Name EXEC SP_HELPFILE". c. Description of operand Operand Description DB-Name Specifies a database name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Restore a database (DB01) using its backup data. The file restore using swstrestore has been completed and a meta data file exists at D: SQLSVR DB01.swst-dmp. C: >set SWSTGNODE=nodeAGT C: >C: Win32 AdvancedCopyManager bin swstrestore_sqlsvr -Xserver VSERVER -Xmeta D: SQLSVR DB01.swst-dmp DB01 DB01 swstrestore_sqlsvr completed C: > You cannot specify a target backup volume and perform backup if: Neither the virtual server nor the instance exists By choosing to apply logs or not, you can select one of the following two restore methods: Restore to a backup point (only restoring backup data) Restore to the latest point or a specific point (restoring backup data and then applying logs) Replication Management Commands Swsrpbackup_sql and swsrprestore_sql are used in the backup operation of SQL Server by the replication management function SQL Server backup execution command (swsrpbackup_sql) This command backs up SQL Server 2000 databases. This command, in cooperation with SQL Server 2000, performs copy of data of the target database volumes on to backup volumes by executing the replication creation command (swsrpmake). The database backup history information will be stored in msdb of SQL Server a. Specification method 229

233 program-directory bin swsrpbackup_sql [-Xserver Server-Name] [-Xinstance Instance-Name] -Xdevmap Device-Map-File b. Description of options Option Description DB-Name-1 DB-Name-2 DB-Name-i -Xserver -Xinstance -Xdevmap -m Specifies the virtual server name of connected SQL Server in case of operation by MSCS. In case of operation without MSCS, this option need not be specified. Specifies a connection instance. Specify an instance name in the operand. If this option is not specified, connection will be made to the default instance. Specify a device map file name that describes combinations of database volumes and destination backup volumes. Specify a device map file name using an absolute pathname. For backup server type operation (server-to-server replication), specifies that communication processing with the backup server (non-operation server) is not performed. When this option is specified, volume status check processing and preprocessing and postprocessing are not performed for the backup volume. -t c. Description of operand Operand This option is valid only during backup server type operation. Specifies that the preprocessing and postprocessing for a backup volume (copy destination volume) are not performed. DB-Name-1 DB-Name-i (i=1,2,,,,64) Description Specifies database names. Delimit by the half-size blank or the tab character and specify the database names when you specify two or more databases. 65 data base names or more cannot be specified. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Backup the databases DB01, DB02, and DB03 of virtual server VSERVER. (Suppose that the logical node name of AdvancedCopy Manager is nodeagt.) C: >set SWSTGNODE=nodeAGT C: >C: Win32App AdvancedCopyManager bin swsrpbackup_sql -Xserver VSERVER -Xdevmap G: STGADM devmap.txt DB01 DB02 DB03 DB01 DB02 DB03 swsrpbackup_sql completed C: > You cannot perform backup in the following cases: A specified database does not exist. (This case includes the case where neither the virtual server nor the instance exists.) In the case of specifying two or more databases, all of the specified databases are not databases of the same instance. (In the case where Xinstance option is not used, the processing is done to the default instance. In the case where Xinstance option is used, the processing is done to the specified named instance.) The specified device map file does not exist. The description on a target database volume of the device map file has an error. (see ) The database volumes and backup volumes described in the device map file are not registered as original volumes and replica volumes, respectively. The synchronous processing between the database volumes and the backup volumes described in the device map file is not in equivalency holding state. 230

234 After operation is begun, any of physical information (box identifier, OLU number, EXTENT start position, and EXTENT size) of a volume has been changed. A database volume has plural mount points. (Only Windows 2000) If a database volume is an SDX object (SynfinityDISK), the state of the SDX object is not in the following states: 1. The mirror volume is ACTIVE or STOP. 2. The mirror slices are ACTIVE or STOP. 3. The state of SDX Disk is ENABLE. If a database volume is an SDX object (SynfinityDISK) on Windows 2000, the auto mounting function of the SDX object is ON. In the case where all the backup volumes are volumes on the database server, m option is specified. For backup server type operation (server-to-server replication), the storage server on which the command is executed is not the operation server of the corresponding replication volumes. For backup server type operation (server-to-server replication), communication with a destination server fails. 65 databases or more are specified. When the backup to perform corresponds to either of the following conditions, perform drive letter release or unmount of copy destination volume before executing a command. When a replication is performed between different OS's When the sizes of replication source volume and replication destination volume differ When performing neither drive letter release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of backup serves as an error. If this command is executed during execution of snapshot processing, stop the copy processing in progress and start the snapshot processing again. This command provides the function to back up two or more databases at the same time by specifying the operand. When, like two or more databases exist on one partition, physical files of plural databases exist together on volumes, perform the backup of all the databases which exist on the volumes by using this function. This command makes all the databases specified in operand to be frozen by SQL Server 2000 until backup processing is completed. Thus, if the volumes where database files exist are independent in each database, back up each database two or more times to shorten the frozen time as much as possible. Now, the advanced copy which makes a SDX object (SynfinityDISK) backup volume is not supported. Therefore, only the advanced copy from a database volume which is an SDX object to a backup volume which is a non-sdx object can be used. Use the COPY command, in case you copy data to a SDX object. Because processing of securing data consistency for database volumes when the backup is performed is done by SQL Server 2000, the preprocessing and postprocessing (drive letter release and reassignment) like a usual file system volume are not executed. If an error occurs while SQL Server backup execution command (swsrpbackup_sql) is processing the database of two or more volumes composition with this command, processing is interrupted. When you perform synchronous type backup, restart stopped synchronous processing by using the synchronous processing start command (swsrpstartsync). 231

235 This command can be executed only while none of the following commands are running. Replication volume information setting command (swsrpsetvol) Replication volume information deletion command (swsrpdelvol) Resource adjustment command (swsrprecoverres) SQL Server restore execution command (swsrprestore_sql) This command restores an SQL Server 2000 database. Enter this command after restoring database files using the replication creation command (swsrpmake). This command recreates a database from restored database files. To perform recovery, after this command is executed, apply logs using Enterprise Manager or Transact-SQL. a. Specification method program-directory bin swsrprestore_sql [-Xserver Server-Name] [-Xinstance Instance-Name] [-Xnolog] -Xmeta Meta-File-Name b. Description of options Option Description DB-Name -Xserver -Xinstance -Xnolog Specifies the virtual server name of connected SQL Server in case of operation by MSCS. In case of operation without MSCS, this option need not be specified. Specifies a connection instance. Specify an instance name in the operand. If this option is not specified, connection will be made to the default instance. Specifies to restore a DB to a backup point, without applying logs. If this option is not specified, the DB will be restored to a backup point but cannot be used until logs are applied to it. Apply logs using Enterprise Manager or Transact-SQL. -Xmeta c. Description of operand Operand DB-Name Specifies a meta data file name, using an absolute pathname. A meta data file will be stored as "db-name.swsrp-dmp" in the same folder as the primary data file. To confirm file identification numbers of database files, use the Transact-SQL "USE DB-Name EXEC SP_HELPFILE". Description Specifies a database name. d. End status = 0: Normal end > 0: Abnormal end e. Execution example Restore a database (DB01) using its backup data. The file restore using swstrestore has been completed and a meta data file exists at D: SQLSVR DB01.swsrp-dmp. C: >C: Win32App AdvancedCopyManager bin swsrprestore_sql -Xserver VSERVER -Xmeta D: SQLSVR DB01.swsrp-dmp DB01 DB01 swsrprestore_sql completed C: > You cannot specify a target backup volume and perform backup if: Neither the virtual server nor the instance exists 232

236 By choosing to apply logs or not, you can select one of the following two restore methods: Restore to a backup point (only restoring backup data) Restore to the latest point or a specific point (restoring backup data and then applying logs) 233

237 234

238 Chapter 11 Notes on Operations This chapter provides notes on the operations of Softek AdvancedCopy Manager Notes on Backup Operation or Replication operation This chapter provides notes on the backup operation or replication operation. Throughout this chapter, the primary partition on Disk Administrator is called the "basic logical disk" and the logical drive in the extended partition is called the "extended logical disk". Additionally, the basic and extended logical disks are generically called the "logical disks" General notes This chapter provides general notes on the backup operation or replication operation. +Locale of a Storage Server On all the storage servers, the locale of an internal code system to be used by Softek AdvancedCopy Manager (a code system to be specified when Softek AdvancedCopy Manager is installed on a storage management server) must be installed. Between a Storage management server and a Storage server, when language environment (LANG) differs, management is needed. The combination and solution are shown below. Storage management server Windows (SJIS) Windows (SJIS) Windows (SJIS) Storage server Windows (SJIS) Solaris OE (EUC) HP-UX (EUC) Solution Not required Windows (SJIS) Linux (EUC) Not required Solaris OE: Depends on locale setting (standard EUC) Solaris OE: Depends on locale setting (standard EUC) Solaris OE: Depends on locale setting (standard EUC) Solaris OE: Depends on locale setting (standard EUC) Linux (EUC) Linux (EUC) Linux (EUC) Windows (SJIS) Solaris OE (EUC) HP-UX (EUC) Linux (EUC) Windows (SJIS) Solaris OE (EUC) HP-UX (EUC) The SJIS package needs to be installed on the Storage server. The SJIS package needs to be installed on the Storage server. Not required (When the Storage server is EUC, the Storage server responds normally.) Not required (for the same code) When the management server is SJIS, the JIS package needs to be installed on the Storage server. Not required (for the same LANG) When the management server is SJIS, the JIS package needs to be installed on the Storage server. Not required Not required (When the Storage server is EUC, the Storage server responds normally.) Not required Not required Linux (EUC) Linux (EUC) Not required Install SUNWjpck (SJIS package) as required for the response. After the package is installed, perform the operation "Collect or reflect the information for each device" again from the Web client. +Size of a Logical Disk A transaction volume and a backup volume must have the same size. However, not all of a size specified on Disk Administrator will be usable for the following disks because the OS control space is automatically allocated. 235

239 Basic logical disk in the beginning of a disk (the leftmost on Disk Administrator) All the extended logical disks Thus, decide a transaction/backup volume as follows: If a transaction volume is on a basic logical disk at the beginning (the leftmost on Disk Administrator) or any extended logical disk, define a backup volume also on a basic logical disk at the beginning or on an extended logical disk. If a transaction volume is on a basic logical disk not in the beginning, define a backup volume also on a basic logical disk not in the beginning. In sum, combine only a transaction volume and a backup volume in the same color as shown in the above figure. Moreover, please make the capacity of the volume a combination of the same colors as the above figure when you make original volume/ replica volume the same size when you operate the replication. To prevent an operation error, you are recommended to define as extended logical disks all the logical disks on a GR unit to be managed by Softek AdvancedCopy Manager. If you cannot define all the logical disks as extended logical disks, you are recommended to use the same configuration for a partition including a device defined as a transaction volume and a partition including a device defined as a backup volume. This means the relationship between Disks 2 and 4 in the above figure. When performing the replication between servers between different OS's (WindowsNT/Windows2000), even if it performs the same definition by each server, the sizes of the partition created by the difference in OS may differ. In this case, please define it as a duplicate place becoming large. +Types of Logical Disks If basic and extended logical disks are mixed in one LUN, be sure to create an extended logical disk after a basic logical disk (the right side on Disk Administrator). Do not create a basic logical disk after an extended logical disk. If you do, a mismatch will occur between the order of logical disks output on Disk Administrator and the logical disk 236

240 numbers on the device or block device name displayed on the management window of Softek AdvancedCopy Manager. The following shows detailed information. To prevent an operation error, you are recommended to define as extended logical disks all the logical disks on a GR unit to be managed by Softek AdvancedCopy Manager. +Exclusion from Backup Targets or Replication Targets The following devices must not be subject to the backup operation or replication operation. Device on which the system is stored Device on which Softek AdvancedCopy Manager has been installed Device on which the management list of Softek AdvancedCopy Manager exists 237

241 +Fetching of Device Information Before starting the backup operation or replication operation, fetch device information managed by all the storage servers on the Web window of Softek AdvancedCopy Manager. This operation will take time proportional to the total number of devices defined on the selected storage servers. If many devices are involved, perform this operation while the CPU load or I/O load is low. As a guide, about 0.5 seconds are required per device (partition) under a no-load condition. When backup synchronous processing or synchronous replication processing is being performed, device information may be unable to be acquired correctly. Therefore, when you take in device information, where all synchronous processings are canceled, please carry out. +Change in Device Configuration To change the device configuration of a volume defined as a transaction or backup volume or replication volume as shown below, deregister the transaction or backup volume, change the device configuration, and then reregister it as a volume of Softek AdvancedCopy Manager. Deleting a logical drive in the primary or extended partition Adding a primary or extended partition or a logical drive Changing the partition type (primary or extended partition) Changing the capacity of logical drive in the primary or extended partition This processing applies to all the volumes in a disk that stores a volume with a device configuration to be changed. For information on a detailed work procedure, see chapter 9.5.7, "Changing the device configuration". +Running Software All the devices are always in use while any of the following software is running. Before performing backup or restoration or replication, therefore, do as described below. Software which locks a disk (virus software, system surveillance software, etc.) In case you perform backup/restoration business and replication business, please stop the above-mentioned software temporarily. Moreover, please do not introduce the software which cannot be stopped. SystemWalker/CentricMGR Temporarily stop the service of SystemWalker/CentricMGR (a service indicated as SystemWalker MpTrfExA) before performing backup or restoration or replication. SystemWalker/PerfMGR In case you perform backup/restoration business and replication business, please stop service (service display name : SystemWalker/PerfMGR DCM and SystemWalker/PerfMGR FCMAC) of SystemWalker/PerfMGR temporarily. Distributed link tracking client service (Windows 2000 SP2 or before) In before Windows 2000 SP2, in case you perform backup/restoration business and replication business, please stop distributed link tracking client service (service display name : Distributed Link Tracking Client) temporarily. In the case of Windows 2000 SP3, it is not necessary to stop this service. +Upper Limit of Number of Operations Simultaneously Executed An upper limit exists on the number of backup or restoration operations that can be simultaneously executed on one logical unit (LU). Thus, place eight or less logical disks on one LU. If, for the sake of operation, you need to create nine or more logical disks on one LU, design the operation so that only fewer backup or restoration operations than the upper limit will be executed on logical disks (volumes with the same g?d? in the AdvancedCopy Manager disk name) on the same LU. Inquire the Fujitsu customer engineer (CE) about the upper limit of the number of operations simultaneously executed. +About the volume set, stripe set, and fault tolerant disk of WindowsNT A volume set, a stripe set, and a fault tolerant disk cannot be used by backup employment and replication employment. +Dynamic Volume of Windows2000 No dynamic volume of Windows2000 can be used as a transaction volume, a backup volume, a original volume or a replica volume. +About the drive path function of Windows2000 The partition which has mounted other disks using the drive path function of Windows2000 cannot be used by backup 238

242 employment and replication employment. +About failure and the mount point of backup When the backup operation by using the synchronous high-speed backup is performed at Windows2000, information of the mount point might not be able to be acquired correctly by reboot the system, restart the AdvancedCopy Manager service or the fail over of cluster employment. If information of the mount point cannot be correctly acquired, the following messages are output and the transaction volume with mount point cannot be backed up normally. swst0754 The abnormal volume was detected. Volume=[VOLUME], Error=[ERROR] In this case, operate as follows. In case of the transaction volume with mount point Set the option to continue the process even if the mount point cannot be acquired. Make the following files to set the option. At usual (not cluster) operation <environment-settings-directory> etc backup data DEFAULT check.ini At cluster employment <environment-settings-directory for logical node> etc backup data DEFAULT check.ini The description form is as follows. [check] MountPointCheck=Force The alert message is output when the backup is executed and processing is continued. If the transaction volume is not mounted to the volume output to the message, the backup is normally done. If the transaction volume is mounted to the volume output to the message, the preprocessing of backup is not executed. Execute the backup again after repairing the volume where abnormality occurs. In case of the transaction volume without mount point Set the option to execute the process the mount point cannot be acquired. Make the following files to set the option. Set the option to execute the process without acquiring the mount point. Make the following files to set the option. At general operation (non-cluster) <environment-settings-directory> etc backup data DEFAULT check.ini At the cluster operation <logical-node-environment-settings-directory> etc backup data DEFAULT check.ini The description form is as follows. [check] MountPointCheck=Pass Processing is performed without acquiring a mount point, if it backs up. +About the message outputted to an event viewer While performing synchronous processing, it is an event viewer (system). Although the following errors may be displayed, since it is satisfactory, please ignore. [type]:error [source]:disk [Description]: An error was detected on device Device Harddisk0 DR0 during a paging operation. Although an error is expressed to an event viewer (application log) as replication business when there is no entry for [to an execution command] a display, please ignore, when satisfactory. +About the composition of a disk Since it needs to be exclusively accessed from one server, it is necessary to set up a disk so that two or more servers can detect or cannot access the same logic disk. Since this setup cannot be performed by OS (Windows NT/2000), please carry out by setup of hardwares, such as ETERNUS/GR series and a fiber channel switch. 239

243 Notes on the snapshot high-speed backup This chapter provides notes on the snapshot backup. +Number of Required Backup Volumes The snapshot high-speed backup requires as many backup volumes as the number of specified generations. Thus, the snapshot backup is disabled if: All the specified number of generations have been backed up, and No new volume that can be used as a backup volume exists. +Continuous Backup Performing the snapshot high-speed backup continuously with the same transaction volume specified will perform the backup operation in parallel. Performing the snapshot high-speed backup continuously more often than the number of preservation generations will cancel the backup operations starting from the oldest one. In other words, you cannot simultaneously perform the backup operation more often than the specified number of generations. +SDX Object Backup Operation If the transaction volume is an SDX object, the backup operation may not be continued due to a hardware problem. In this case, change the backup operation as follows: 1. Display the initial window. For more information, see chapter 4.4.3, "Starting the initial window". 2. Fetch all the device information from a storage server whose backup operation should be changed. When you fetch device information, the system will detect a device with the same name as an SDX object whose backup operation can no longer be continued. Move the device to the [Additional instruction device] field. For information on fetching device information, see chapter 4.4.5, "Fetching device information on a storage server". At this time, do not delete the original SDX object that is displayed in the [Device not detected] field. 3. Display the backup management window. For information, see chapter 4.4.6, "Displaying the backup management window". 4. Set the added SDX object as a transaction volume. For more information, see chapter 4.4.8, "Setting the operation type for a device". 5. Set a backup policy for the added SDX object. For more information, see chapter , "Setting backup policies". 6. After specifying the added SDX object, perform backup Notes on restoration This chapter provides notes on restoration. +Timing of Restoration If data on a transaction volume has been rewritten since the latest backup data is collected to a backup volume and until restoration is performed, the rewritten data shall not be guaranteed. 240

244 [Figure 9.1 Notes on restoration of Softek AdvancedCopy Manager] Notes of synchronous high-speed backup This chapter describes the notes of synchronous high-speed backup. +About processing of backup Before operating volume and backup volume are in an equivalent state, a backup execution command cannot be executed. +About a setup of a backup policy A backup policy can be set up if a number required for snapshot type high-speed backup employment of backup volumes are registered even if a number required at the time of a backup policy setup of synchronous high-speed backup employment of backup volumes are not registered. In this case, synchronous high-speed type backup may be unable to be performed. +About the loss error of delay write-in data When backup synchronous processing is started, "loss of delay write-in data" error may occur. In the case of the backup volume in which the volume which has generated the error is performing backup synchronous processing, since a problem is not in the adjustment of backup data, please ignore. +About server starting before an equivalent nature maintenance state If a server is started before starting synchronous processing and being in an equivalent nature maintenance state when synchronous high-speed backup / replication employment is being performed, since the disk of a copy place cannot recognize from OS, after waiting for synchronous processing to be in an equivalent nature maintenance state, a server is rebooted, or after canceling synchronous processing, it is necessary to reboot a server. 241

245 In addition, since abnormalities may occur to the device information used by backup management / replication management at this time, with reference to " Recovering of device information used by backup management" or " Recovering of device information used by replication management " of this manual, it is necessary to restore device information Notes on the Web Window Environment This chapter provides notes on the Web window environment. +Settings of Java Plug-in Properties After installing the Java Plug-in, display the Properties window of the Java Plug-in. Select [Settings] - [Control Panel] - [Java Plug-in]. Table 11.1 shows the relationships between the settings on the Java Plug-in Properties window and the operations on the Web window. Depending on the settings made on the Properties window, the Web window may not normally operate. The Web window can operate by the default values that Plug-in has been installed. You need not change the settings in particular. [Table 11.1 Settings of the Java Plug-in and operations on the Web window] Tag name Setting value name Setting Default value Remarks Enabling the Java Plug-in Must be checked Checked Unless this item is checked, a message "Java is disabled" will be displayed on the Java console and the Web window cannot be started. Basics Displaying the Java console Optional Not checked You are recommended to check this item although it is optional. The operating status of the Web window will be displayed on the "Java Console" and can be used as investigation information if any error occurs on the Web window. Caching JAR to memory Recommended to be checked Checked If this item is checked, you can bring up more quickly from the initial window a management window that has been brought up once. Parameter for Java execution Not specified Not specified This item will be meaningless if specified. Details Java Run Time Environment Enabling the Just in Time Compiler Using the Java Plug-in by default Must be checked Using the Java Plug-in by default Checked Specify the Run Time level at which the Web window should run. Do not specify any other level. If this item is not checked, a malfunction may occur. If this item is not checked, a malfunction may occur. Enabling debugging Must not be checked Not checked If this item is checked, a malfunction may occur. Proxy Using the browser settings Must be checked Checked If this item is not checked, a malfunction may occur. +Proxy Settings of Web Browser Before using the Web window, specify an IP address or server name for a storage management server on the Web browser. At this time, do not specify the proxy of the Web browser as the IP address or server name. For Netscape Navigator 4.5 or later 242

246 Select the [Edit] menu and then [Settings] to display the Settings dialog box. From the category (tree), select [Details] and then [Proxy], check [Manually set up the proxy], and click the Display button to display the Manually Set Up Proxy dialog box. In the [Do not use the proxy for a domain starting with:] box, specify the IP address of a storage management server. For Internet Explorer 4.0 Select the [View] menu and then [Internet Options] to display the Internet Options dialog box. From the dialog box, select the [Connection] tag and click the [LAN Connection] button. Then, the [Local Area Network (LAN) Settings] dialog will be displayed. Click the [Details] button to display the [Proxy Settings] dialog. Then, in the [Do not use the proxy for an address starting with:] box in the [Proxy Settings] dialog, specify the IP address of a storage management server. For Internet Explorer 5.0 or later Select the [Tools] menu and then [Internet Options] to display the Internet Options dialog box. From the dialog box, select the [Connection] tag and click the [LAN Connection] button. Then, the [Local Area Network (LAN) Settings] dialog will be displayed. Click the [Details] button to display the [Proxy Settings] dialog. Then, in the [Do not use the proxy for an address starting with:] box in the [Proxy Settings] dialog, specify the IP address of a storage management server. 243

247 244

248 Appendix A Preprocessing and Postprocessing of Backup and Restoration This appendix describes shell scripts used for preprocessing and postprocessing of backup and restoration. Note that a shell script described in this appendix has different linefeed positions due to formatting of this manual. A.1 Overview Shell scripts used for preprocessing and postprocessing of backup or restoration are started before and after backup or restoration when a backup or restore execution command is executed. These shell scripts describe processing required by Softek AdvancedCopy Manager to back up or restore a transaction volume. These scripts are executed on Windows Scripting Host (WSH) (coded in JScript). This chapter describes the setup of preprocessing and postprocessing. A.2 Preprocessing and Postprocessing of Backup Backup on Softek AdvancedCopy Manager must be performed basically while access to a transaction volume from other processes is inhibited. Normally, the preprocessing acquires the mount status of a transaction volume using the transaction volume name and then performs the following processing: Transaction volume status A drive letter has been allocated to the transaction volume. No drive letter has been allocated to the transaction volume. Preprocessing De-allocate the drive letter if it has been allocated to the transaction volume. Perform no processing. What to do in the postprocessing must be determined depending on what has been done in the preprocessing. Preprocessing The drive letter of the transaction volume has been de-allocated. No processing has been performed. Postprocessing Allocate the drive letter to the transaction volume if it has been de-allocated in the preprocessing. To backup volume, the dismount processing is carried out and it changes into the state where the data of backup volume can be referred to. To backup volume, the dismount processing is carried out and it changes into the state where the data of backup volume can be referred to. If special preprocessing or postprocessing is required, you need to add the concerned processing to a shell script. If post-processing was failed, execute the Resource match command because the consistency of resource information may be incomplete. A.2.1 Preprocessing of backup The name of a script file for preprocessing of backup is as follows. In the case of non-cluster employment "environment-settings-directory etc backup scripts OpcBackupPre.js" In the case of cluster employment <Shared disk>: etc opt swstorage etc backup scripts OpcBackupPre.js // Softek AdvancedCopy Manager for Windows 245

249 // All Rights Reserved, Copyright FUJITSU LIMITED, 2002 // // OpcBackupPre.js: Pre-Processing Script for swstbackup // // [Parameters] // 1st argument: device name of transaction volume // 2nd argument: drive letter of transaction volume // 3rd argument: device name of backup volume // // [Return Values] // 0: The script ended normally. // 1: The number of the arguments is incorrect. // 2: The drive letter could not be released. // 3: Disk Administrator is running. // 4: An error othar than the above occurred. try { // create global objects var WshShell = WScript.CreateObject("WScript.Shell"); // create Shell object var WshEnv = WshShell.Environment("PROCESS"); Environment object // create var fsobj = WScript.CreateObject("Scripting.FileSystemObject"); // create FileSystemObject object // create SwstBackupPreProc object var proc = new SwstBackupPreProc(); // check DiskAdministrator status checkdiskadminstatus(); // if a drive letter is assigned to the transaction volume, release it if (proc.drvletter.length!= 0) { // when drive letter is assigned proc.releasedriveletter(); else { // when drive letter is not assigned proc.donothingfordriveletter(); // if a backup volume is specified,.bd file is created. if (proc.bvname.length!= 0) { SwstQuit(0); catch (e) { SwstQuit(4); proc.writepostfile(proc.bdfilename, proc.bvname); function SwstBackupPreProc() { 246

250 // member variables this.tvname = WScript.Arguments.length!=3?SwstQuit(1):WScript.Arguments.Item(0); // device name of transaction volume this.drvletter // drive letter = WScript.Arguments.Item(1); this.postfilename = getdatapathname() + " " + getputfilename(this.tvname) + ".pre"; // name of postprocessing file this.bvname = WScript.Arguments.Item(2); // device name of transaction volume this.bdfilename = getdatapathname() + " " + getputfilename(this.tvname) + ".bd"; // name of postprocessing file // member functions this.releasedriveletter = releasedriveletter; // self-explanatory this.donothingfordriveletter = donothingfordriveletter; // self-explanatory this.writepostfile // self-explanatory function checkdiskadminstatus() { = writepostfile; var command = getbinpathname() + " swstchkdiskadm"; var windowstyle = 0; // means to hide the window and activate another window var waitonreturn = true; // means that the Run method returns any error code returned by the application var returncode = WshShell.Run(command, windowstyle, waitonreturn); if (returncode!= 0) { SwstQuit(3); function releasedriveletter() { var command = getbinpathname() + " swstdrvunset " + " "" + this.drvletter + " ""; var windowstyle = 0; window // means to hide the window and activate another var waitonreturn = true; // means that the Run method returns any error code returned by the application retry."); var i = 0; var retrycnt = 20; // retry number var sleeptime = 1000; // sleep time before retrying (milli seconds) while(true) { var returncode = WshShell.Run(command, windowstyle, waitonreturn); if (returncode!= 0) { if (i < retrycnt) { //WScript.Echo("[backup-pre]swstdrvunset failed and 247

251 + " seconds"); retry limit is over."); else { else { break; //WScript.Echo("[backup-pre]sleep " + sleeptime/1000 WScript.Sleep(sleepTime); i++; continue; //WScript.Echo("[backup-pre]swstdrvunset failed and SwstQuit(2); this.writepostfile(this.postfilename, "drvset"); function donothingfordriveletter() { this.writepostfile(this.postfilename, "none"); function writepostfile(postfile, postdata) { var overwrite = true; // means to overwrite a file if it exists. var postfilestream = fsobj.createtextfile(postfile, overwrite); postfilestream.write(postdata); postfilestream.close(); function SwstQuit(exitStatus) { switch(exitstatus) { case 0: case 1: WScript.Quit(0); WScript.Echo("[Backup Preprocessing] The number of the arguments is incorrect."); case 2: WScript.Quit(1); WScript.Echo("[Backup Preprocessing] The drive letter of the transaction volume could not be released."); case 3: running."); default: WScript.Quit(2); WScript.Echo("[Backup Preprocessing] Disk Administrator is WScript.Quit(3); 248

252 WScript.Echo("[Backup Preprocessing] The script exited abnormally."); WScript.Quit(4); function getdatapathname() { return WshShell.RegRead(getSetupInfoKey() + " etcpathname") + " etc backup data DEFAULT"; function getbinpathname() { return WshShell.RegRead(getSetupInfoKey() + " PathName") + " bin"; function getsetupinfokey() { var nodename = WshEnv.Item("SWSTGNODE"); if( nodename!= "" ){ return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion " + nodename; return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion"; function getputfilename(devicename){ var filename; if( issafediskname(devicename) ){ else{ var re = /( S+) /( S+):( S+)/; filename = devicename.replace(re, "$1_$2_$3"); filename = devicename; return(filename); function getgxdxpx(devicename){ var gxdxpx; if( issafediskname(devicename) ){ else{ var re = /( S+) /( S+):( S+)/; gxdxpx = devicename.replace(re, "$3"); gxdxpx = devicename; return(gxdxpx); 249

253 function issafediskname(devicename){ var key = ":g"; var s = devicename.indexof(key); if ( s < 0 ) { else { return (false); return (true); A.2.2 Postprocessing of backup The name of a script file for postprocessing of backup is as follows. In the case of non-cluster employment "environment-settings-directory etc scripts OpcBackupPost.js" In the case of cluster employment <Shared disk>: etc opt swstorage etc backup scripts OpcBackupPost.js // Softek AdvancedCopy Manager for Windows // All Rights Reserved, Copyright FUJITSU LIMITED, 2002 // // OpcBackupPost.js: Post-Processing Script for swstbackup // // [Parameters] // 1st argument: device name of transaction volume // 2nd argument: drive letter of transaction volume // // [Return Values] // 0: The script ended normally. // 1: The number of the arguments is incorrect. // 2: The drive letter of the transaction volume could not be restored. // 3: The drive letter of the backup volume could not be assigned. // 4: The chkdsk command cannot be run. // 5: The drive letter of the backup volume could not be released. // 7: The drive letter of the backup volume could not be assigned. (in dodrvunsetanddrvset() function) // 8: The drive letter of the backup volume could not be released. (in dodrvunsetanddrvset() function) // 6: An error othar than the above occurred. try { // create global objects var WshShell = WScript.CreateObject("WScript.Shell"); Shell object var WshEnv = WshShell.Environment("PROCESS"); Environment object // create // create var fsobj = WScript.CreateObject("Scripting.FileSystemObject"); // create FileSystemObject object 250

254 // create SwstBackupPostProc object var proc = new SwstBackupPostProc(); // do nothing if postprocessing file exists if (fsobj.fileexists(proc.postfilename) == false) { SwstQuit(0); // get postprocessing type var postproctype = proc.getpostprocdata(proc.postfilename); switch(postproctype) { case "drvset": proc.reassigndriveletter(); break; case "none": proc.donothing(); break; // do nothing if postprocessing file exists if (fsobj.fileexists(proc.bdfilename) == true) { var bvname = proc.getpostprocdata(proc.bdfilename); //dochkdsk(bvname); dodrvunsetanddrvset(bvname); // clear temporary files proc.deletepostfile(proc.postfilename); proc.deletepostfile(proc.bdfilename); SwstQuit(0); catch (e) { SwstQuit(6); function SwstBackupPostProc() { // member variables this.tvname = WScript.Arguments.length!=2?SwstQuit(1):WScript.Arguments.Item(0); // device name of transaction volume this.drvletter // drive letter = WScript.Arguments.Item(1); this.postfilename = getdatapathname() + " " + getputfilename(this.tvname) + ".pre"; // name of postprocessing file this.bdfilename = getdatapathname() + " " + getputfilename(this.tvname) + ".bd"; // name of postprocessing file // member functions this.getpostprocdata = getpostprocdata; // self-explanatory this.reassigndriveletter = reassigndriveletter; // 251

255 self-explanatory this.donothing // self-explanatory this.deletepostfile // self-explanatory function getpostprocdata(postfile) { var iomode = 1; = donothing; = deletepostfile; // means read-only mode var create = false; // means not to create a file var postfilestream = fsobj.opentextfile(postfile, iomode, create); var postdata = postfilestream.readall(); postfilestream.close(); return postdata; function reassigndriveletter() { var command = getbinpathname() + " swstdrvset " + getgxdxpx(this.tvname) + " " + " "" + this.drvletter + " ""; var windowstyle = 0; window // means to hide the window and activate another var waitonreturn = true; // means that the Run method returns any error code returned by the application var returncode = WshShell.Run(command, windowstyle, waitonreturn); if (returncode!= 0) { SwstQuit(2); function donothing() { // do nothing function deletepostfile(postfile) { if (fsobj.fileexists(postfile) == true) { fsobj.deletefile(postfile); function SwstQuit(exitStatus) { switch(exitstatus) { case 0: case 1: WScript.Quit(0); WScript.Echo("[Backup Postprocessing] The number of the arguments 252

256 is incorrect."); case 2: WScript.Quit(1); WScript.Echo("[Backup Postprocessing] The drive letter of the transaction volume could not be restored."); case 3: WScript.Quit(2); WScript.Echo("[Backup Postprocessing] The drive letter of the backup volume could not be assigned."); run."); case 4: case 5: WScript.Quit(3); WScript.Echo("[Backup Postprocessing] The chkdsk command cannot be WScript.Quit(4); WScript.Echo("[Backup Postprocessing] The drive letter of the backup volume could not be released."); case 7: WScript.Quit(5); WScript.Echo("[Backup Postprocessing] The drive letter of the backup volume could not be assigned. (in dodrvunsetanddrvset() function)"); case 8: WScript.Quit(7); WScript.Echo("[Backup Postprocessing] The drive letter of the backup volume could not be released. (in dodrvunsetanddrvset() function)"); default: WScript.Quit(8); WScript.Echo("[Backup Postprocessing] The script exited abnormally."); WScript.Quit(6); function getdatapathname() { return WshShell.RegRead(getSetupInfoKey() + " etcpathname") + " etc backup data DEFAULT"; function getbinpathname() { return WshShell.RegRead(getSetupInfoKey() + " PathName") + " bin"; function getsetupinfokey() { var nodename = WshEnv.Item("SWSTGNODE"); if( nodename!= "" ){ return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu 253

257 Softek AdvancedCopy Manager CurrentVersion " + nodename; return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion"; function getputfilename(devicename){ var filename; if( issafediskname(devicename) ){ else{ var re = /( S+) /( S+):( S+)/; filename = devicename.replace(re, "$1_$2_$3"); filename = devicename; return(filename); function getgxdxpx(devicename){ var gxdxpx; if( issafediskname(devicename) ){ else{ var re = /( S+) /( S+):( S+)/; gxdxpx = devicename.replace(re, "$3"); gxdxpx = devicename; return(gxdxpx); function issafediskname(devicename){ var key = ":g"; var s = devicename.indexof(key); if ( s < 0 ) { else { return (false); return (true); function dochkdsk(bvname) { var chkdrv = "Z:" var command = getbinpathname() + " swstdrvset " + bvname + " " + chkdrv; if ( WshShell.Run(command, 0, true)!= 0 ) { SwstQuit(3); var chkdskflag = true; 254

258 if ( checkversion4() ) command = "chkdsk /f " + chkdrv; else command = "chkdsk /x " + chkdrv; var exitstatus = WshShell.Run(command, 0, true); if ( exitstatus!= 0 && exitstatus!= 1 && exitstatus!= 2 ) { chkdskflag = false; var drvunsetflag = true; command = getbinpathname() + " swstdrvunset " + chkdrv; if ( WshShell.Run(command, 0, true)!= 0 ) { drvunsetflag = false; if ( chkdskflag == false ) { SwstQuit(4); else if ( drvunsetflag == false ) { SwstQuit(5); function checkversion4(){ var version = WshShell.RegRead("HKLM Software Microsoft Windows NT CurrentVersion CurrentVersion"); switch(version) { case "4.0": default: // Windows NT 4.0 return(true); break; // other break; return(false); function dodrvunsetanddrvset(dvname) { var chkdrv = "Z:"; var command = getbinpathname() + " swstdrvset " + dvname + " " + chkdrv; if ( WshShell.Run(command, 0, true)!= 0 ) { SwstQuit(7); command = getbinpathname() + " swstdrvunset " + chkdrv; 255

259 var i = 0; var retrycnt = 20; // retry number var sleeptime = 1000; // sleep time before retrying (milli seconds) while (true) { if ( WshShell.Run(command, 0, true)!= 0 ) { if (i < retrycnt) { //WScript.Echo("[backup-post]swstdrvunset failed and retry."); //WScript.Echo("[backup-post]sleep " + sleeptime/ " seconds"); WScript.Sleep(sleepTime); i++; continue; else { //WScript.Echo("[backup-post]swstdrvunset failed and retry limit is over."); SwstQuit(8); else { break; In order to change into the state where the data of backup volume can be referred to after backup implementation, it is necessary to backup volume to carry out the dismount processing or chkdsk processing (the dismount processing is performed with the script by which standard offer is made.). In order to carry out chkdsk processing, please remove the comment of the 49th line and comment the 50th line. In order to perform these processings to backup volume, the drive character specified by the 239th (it is the 194th line in chkdsk) line is used. With the script by which standard offer is made, although Z drive is used, please Z drive be vacant, and when you are not a drive, be vacant in "Z:" of the 239th (in chkdsk, it is the 194th line) line, and change into a drive. When you execute simultaneously two or more backup execution commands or restoration execution commands, please use properly the drive used for every backup volume, and customize so that the competition state of a drive character does not occur. A.3 Preprocessing and Postprocessing of Restoration Restoration on Softek AdvancedCopy Manager must be performed while access to a transaction volume from other processes is inhibited. Normally, the preprocessing acquires the drive letter setting status of a transaction volume using the transaction volume name and then performs the following processing: Transaction volume status A drive letter has been allocated. No drive letter has been allocated. Preprocessing Deallocate the drive letter of the transaction volume. Perform no processing. What to do in the postprocessing must be determined depending on what has been done in the preprocessing. Preprocessing The drive letter of the transaction volume has been deallocated. Postprocessing Reallocate the drive letter of the transaction volume. 256

260 Chkdsk is performed to transaction volume. No processing has been performed. Chkdsk is performed to transaction volume. If special preprocessing or postprocessing is required, you need to add the concerned processing to a shell script. If postprocessing was failed, execute the Resource match command because the consistency of resource information may be incomplete. A.3.1 Preprocessing of restoration The name of a script file for preprocessing of restoration is as follows. In the case of non-cluster employment "environment-settings-directory etc backup scripts OpcRestorePre.js" In the case of cluster employment <Shared disk>: etc opt swstorage etc backup scripts OpcRestorePre.js // Softek AdvancedCopy Manager for Windows // All Rights Reserved, Copyright FUJITSU LIMITED, 2002 // // OpcRestorePre.js: Pre-Processing Script for swstrestore // // [Parameters] // 1st argument: device name of transaction volume // 2nd argument: drive letter of transaction volume // // [Return Values] // 0: The script ended normally. // 1: The number of the arguments is incorrect. // 2: The drive letter could not be released. // 3: Disk Administrator is running. // 4: An error othar than the above occurred. try { // create global objects var WshShell = WScript.CreateObject("WScript.Shell"); // create Shell object var WshEnv = WshShell.Environment("PROCESS"); // create Environment object var fsobj = WScript.CreateObject("Scripting.FileSystemObject"); // create FileSystemObject object // create SwstRestorePreProc object var proc = new SwstRestorePreProc(); // check DiskAdministrator status checkdiskadminstatus(); // if a drive letter is assigned to the transaction volume, release it if (proc.drvletter.length!= 0) { // when drive letter is assigned proc.releasedriveletter(); 257

261 else { // when drive letter is not assigned SwstQuit(0); catch (e) { SwstQuit(4); proc.donothingfordriveletter(); function SwstRestorePreProc() { // member variables this.tvname = WScript.Arguments.length!=2?SwstQuit(1):WScript.Arguments.Item(0); // device name of transaction volume this.drvletter = WScript.Arguments.Item(1); // drive letter this.postfilename = getdatapathname() + " " + getputfilename(this.tvname) + ".pre"; // name of postprocessing file // member functions this.releasedriveletter = releasedriveletter; // self-explanatory this.donothingfordriveletter = donothingfordriveletter; // self-explanatory this.writepostfile = writepostfile; // self-explanatory function checkdiskadminstatus() { var command = getbinpathname() + " swstchkdiskadm"; var windowstyle = 0; window // means to hide the window and activate another var waitonreturn = true; // means that the Run method returns any error code returned by the application var returncode = WshShell.Run(command, windowstyle, waitonreturn); if (returncode!= 0) { SwstQuit(3); function releasedriveletter() { var command = getbinpathname() + " swstdrvunset " + " "" + this.drvletter + " ""; var windowstyle = 0; // means to hide the window and activate another window var waitonreturn = true; // means that the Run method returns any error code returned by the application var i = 0; var retrycnt = 20; // retry number var sleeptime = 1000; // sleep time before retrying (milli seconds) 258

262 retry."); seconds"); while(true) { limit is over."); var returncode = WshShell.Run(command, windowstyle, waitonreturn); if (returncode!= 0) { if (i < retrycnt) { //WScript.Echo("[restore-pre]swstdrvunset failed and //WScript.Echo("[restore-pre]sleep " + sleeptime/ " WScript.Sleep(sleepTime); i++; continue; else { else { break; //WScript.Echo("[restore-pre]swstdrvunset failed and retry SwstQuit(2); this.writepostfile("drvset"); function donothingfordriveletter() { this.writepostfile("none"); function writepostfile(type) { var overwrite = true; // means to overwrite a file if it exists. var postfilestream = fsobj.createtextfile(this.postfilename, overwrite); postfilestream.write(type); postfilestream.close(); function SwstQuit(exitStatus) { switch(exitstatus) { case 0: WScript.Quit(0); case 1: WScript.Echo("[Restore Preprocessing] The number of the arguments is incorrect."); WScript.Quit(1); case 2: WScript.Echo("[Restore Preprocessing] The drive letter of the transaction volume could not be released."); 259

263 WScript.Quit(2); case 3: WScript.Echo("[Restore Preprocessing] Disk Administrator is running."); WScript.Quit(3); default: WScript.Echo("[Restore Preprocessing] The script exited abnormally."); WScript.Quit(4); function getdatapathname() { return WshShell.RegRead(getSetupInfoKey() + " etcpathname") + " etc backup data DEFAULT"; function getbinpathname() { return WshShell.RegRead(getSetupInfoKey() + " PathName") + " bin"; function getsetupinfokey() { var nodename = WshEnv.Item("SWSTGNODE"); if( nodename!= "" ){ return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion " + nodename; return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion"; function getputfilename(devicename){ var filename; if( issafediskname(devicename) ){ else{ var re = /( S+) /( S+):( S+)/; filename = devicename.replace(re, "$1_$2_$3"); filename = devicename; return(filename); function getgxdxpx(devicename){ var gxdxpx; f( issafediskname(devicename) ){ var re = /( S+) /( S+):( S+)/; gxdxpx = devicename.replace(re, "$3"); else{ 260

264 gxdxpx = devicename; return(gxdxpx); function issafediskname(devicename){ var key = ":g"; var s = devicename.indexof(key); if ( s < 0 ) { else { return (false); return (true); You cannot perform restoration to a transaction volume to which a drive letter has been allocated but cannot be deallocated. Specify a device to which data should be restored. A.3.2 Postprocessing of restoration The name of a script file for postprocessing of restoration is as follows. In the case of non-cluster employment "environment-settings-directory etc backup scripts OpcRestorePost.js" In the case of cluster employment <Shared disk>: etc opt swstorage etc backup scripts OpcRestorePost.js // Softek AdvancedCopy Manager for Windows // All Rights Reserved, Copyright FUJITSU LIMITED, 2002 // // OpcRestorePost.js: Post-Processing Script for swstrestore // // [Parameters] // 1st argument: device name of transaction volume // 2nd argument: drive letter of transaction volume // // [Return Values] // 0: The script ended normally. // 1: The number of the arguments is incorrect. // 2: The drive letter of the transaction volume could not be restored. // 3: The drive letter of the transaction volume could not be assigned. // 4: The chkdsk command cannot be run. // 5: The drive letter of the transaction volume could not be released. // 6: An error othar than the above occurred. try { // create global objects var WshShell = WScript.CreateObject("WScript.Shell"); // create Shell object var WshEnv = WshShell.Environment("PROCESS"); // 261

265 create Environment object var fsobj = WScript.CreateObject("Scripting.FileSystemObject"); // create FileSystemObject object // create SwstRestorePostProc object var proc = new SwstRestorePostProc(); // do nothing if postprocessing file exists if (fsobj.fileexists(proc.postfilename) == false) { proc.donothing(); // get postprocessing type else { var postproctype = proc.getpostproctype(); switch(postproctype) { case "drvset": proc.reassigndriveletter(); break; case "none": proc.donothing(); break; catch (e) { // clear temporary file proc.deletepostfile(); dochkdsk(getgxdxpx(proc.tvname), proc.drvletter); SwstQuit(0); SwstQuit(6); function SwstRestorePostProc() { // member variables this.tvname = WScript.Arguments.length!=2?SwstQuit(1):WScript.Arguments.Item(0); // device name of transaction volume this.drvletter = WScript.Arguments.Item(1); // drive letter this.postfilename = getdatapathname() + " " + getputfilename(this.tvname) + ".pre"; // name of postprocessing file // member functions this.getpostproctype = getpostproctype; // self-explanatory this.reassigndriveletter = reassigndriveletter; // self-explanatory this.donothing = donothing; 262

266 // self-explanatory this.deletepostfile // self-explanatory function getpostproctype() { var iomode = 1; = deletepostfile; // means read-only mode var create = false; // means not to create a file var postfilestream = fsobj.opentextfile(this.postfilename, iomode, create); var postproc = postfilestream.readall(); postfilestream.close(); return postproc; function reassigndriveletter() { var command = getbinpathname() + " swstdrvset " + getgxdxpx(this.tvname) + " " + " "" + this.drvletter + " ""; var windowstyle = 0; another window // means to hide the window and activate var waitonreturn = true; // means that the Run method returns any error code returned by the application var returncode = WshShell.Run(command, windowstyle, waitonreturn); if (returncode!= 0) { function donothing() { // do nothing SwstQuit(2); function deletepostfile() { if (fsobj.fileexists(this.postfilename) == true) { function SwstQuit(exitStatus) { fsobj.deletefile(this.postfilename); switch(exitstatus) { case 0: case 1: WScript.Quit(0); WScript.Echo("[Restore Postprocessing] The number of the arguments is incorrect."); 263

267 case 2: WScript.Quit(1); WScript.Echo("[Restore Postprocessing] The drive letter of the transaction volume could not be restored."); case 3: WScript.Quit(2); WScript.Echo("[Restore Postprocessing] The drive letter of the transaction volume could not be assigned."); be run."); case 4: case 5: WScript.Quit(3); WScript.Echo("[Restore Postprocessing] The chkdsk command cannot WScript.Quit(4); WScript.Echo("[Restore Postprocessing] The drive letter of the transaction volume could not be released."); default: abnormally."); WScript.Quit(5); WScript.Echo("[Restore Postprocessing] The script exited WScript.Quit(6); function getdatapathname() { return WshShell.RegRead(getSetupInfoKey() + " etcpathname") + " etc backup data DEFAULT"; function getbinpathname() { return WshShell.RegRead(getSetupInfoKey() + " PathName") + " bin"; function getsetupinfokey() { var nodename = WshEnv.Item("SWSTGNODE"); if( nodename!= "" ){ return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion " + nodename; return "HKEY_LOCAL_MACHINE SOFTWARE Fujitsu Softek AdvancedCopy Manager CurrentVersion"; function getputfilename(devicename){ var filename; if( issafediskname(devicename) ){ var re = /( S+) /( S+):( S+)/; 264

268 filename = devicename.replace(re, "$1_$2_$3"); else{ filename = devicename; return(filename); function getgxdxpx(devicename){ var gxdxpx; if( issafediskname(devicename) ){ var re = /( S+) /( S+):( S+)/; gxdxpx = devicename.replace(re, "$3"); else{ gxdxpx = devicename; return(gxdxpx); function issafediskname(devicename){ var key = ":g"; var s = devicename.indexof(key); if ( s < 0 ) { return (false); else { return (true); function dochkdsk(tvname, tvdrvletter) { var command; var chkdrv; if ( tvdrvletter.length!= 2 ) { chkdrv = "Z:" else { chkdrv = tvdrvletter; if (tvdrvletter.length!= 2) { command = getbinpathname() + " swstdrvset " + tvname + " " + chkdrv; if ( WshShell.Run(command, 0, true)!= 0 ) { SwstQuit(3); var chkdskflag = true; if ( checkversion4() ) 265

269 else command = "chkdsk /f " + chkdrv; command = "chkdsk /x " + chkdrv; var exitstatus = WshShell.Run(command, 0, true); if ( exitstatus!= 0 && exitstatus!= 1 && exitstatus!= 2 ) { chkdskflag = false; var drvunsetflag = true; if ( tvdrvletter.length!= 2 ) { command = getbinpathname() + " swstdrvunset " + chkdrv; if ( WshShell.Run(command, 0, true)!= 0 ) { drvunsetflag = false; if ( chkdskflag == false ) { SwstQuit(4); else if ( drvunsetflag == false ) { SwstQuit(5); function checkversion4(){ var version = WshShell.RegRead("HKLM Software Microsoft Windows NT CurrentVersion CurrentVersion"); switch(version) { case "4.0": default: // Windows NT 4.0 return(true); break; // other break; return(false); When the drive character is not set as transaction volume, chkdsk to transaction volume uses the drive character specified by the 183rd line. With the script by which standard offer is made, although Z drive is used, please Z drive be vacant, and when you are not a drive, be vacant in "Z:" of the 183rd line, and change into a drive. By the case where the drive character is not set as transaction volume, when you execute simultaneously two or more execution commands or restoration execution commands, please use properly the drive used for every transaction volume, and customize so that the drive for chkdsk does not compete. 266

270 Appendix B Sample Scripts This appendix describes sample scripts for Softek AdvancedCopy Manager. A sample script allows you to back up data on a transaction volume to a tape using Softek AdvancedCopy Manager and backup software in combination. You can hedge against risks by backing up data on a transaction disk not only to a disk but also to a tape. B.1 Overview Use Softek AdvancedCopy Manager and backup software in combination to back up a transaction volume to a tape. Softek AdvancedCopy Manager provides a sample scripts for backup. The manager of backup operation should correct the sample script according to the work and apply it to the actual backup operation. This document and the sample script back up both the two drives on which all the physical data files in the table space in an instance to be backed up. However, you can back up only a drive with a table space to be backed up by correcting the script. Backup on Softek AdvancedCopy Manager is performed in units of drives. If a drive with a data file in the table space to be backed up has data files in other table space, make an Oracle backup declaration for them also. To back up the SYSTEM table space shown in Figure B.1, for example, make Oracle backup declarations in all the five table spaces including other areas in the same volume. A data file in the table space backed up without an Oracle backup declaration cannot be used for recovery because, even during backup, updating of the data file occurs to generate inconsistencies. [Figure B.1 Relationship between an Oracle instance and data files in drive table spaces (in the case of this sample script)] Sample scripts provided for Softek AdvancedCopy Manager are created assuming that the following versions of Oracle and ARCserveIT are used. If you use any other version, correct the sample scripts as required. Oracle8i Release 8.1.x ARCserveIT Version 6.61 B.2 Backup and Restoration of a Transaction volume This chapter describes performing backup and restoration of an Oracle database using Softek AdvancedCopy Manager. B.2.1 Backup procedure The following shows an overview of the backup procedure. 1. Checking the work operation status Check whether work is in operation or not. 267

271 2. Stopping work If work is found to be in operation in Step 1, declare the start of online backup for the database and stop updating data files to make the disk partition that stores work data ready for online backup. 3. Backing up (copying) a disk partition Using the backup function of Softek AdvancedCopy Manager, back up (copy) a disk partition that stores work data. 4. Restarting work If work is found to be in operation in Step 1, declare the end of online backup for the database and restart updating data files. 5. Backing up data to a tape Using backup software, back up a backup (copy) destination disk partition of Softek AdvancedCopy Manager to a tape. Softek AdvancedCopy Manager provides a sample script that automatically performs Steps 2 through 5. For more information, see Chapter B.3.1.2, "Backup". [Figure B.2 Backup] B.2.2 Restoration procedure You can perform restoration in one of the two ways: from a backup disk or from a backup tape. B Performing restoration from a backup disk The following shows an overview of performing restoration from a backup disk. 1. Checking the work stop status Check that work is stopped. If work is in operation, completely stop the work. 2. Performing restoration from a backup disk Using the restoration function of Softek AdvancedCopy Manager, restore data from a backup disk to a transaction volume. [Figure B.3 Performing restoration from a backup disk] 268