10.2
Preface
++ Purpose
++ Intended Readers
This manual is intended for a system administrator who performs storage management using Softek AdvancedCopy Manager.
++ Organization
+ Chapter 1 Overview of Softek AdvancedCopy Manager
This chapter describes the overview of Softek AdvancedCopy Manager.
+ Chapter 2 Starting and Stopping a Daemons
This section describes starting and stopping a daemons 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
+ Chapter 5 Backup Operation (Symfoware)
This chapter describes the backup operation (Symfoware).
+ Chapter 6 Backup Operation in the SP Series
This chapter describes the backup operation in the SP series.
+ Chapter 7 Replication Operation
+ Chapter 8 Operation Maintenance
+ Chapter 9 Commands
This chapter describes notes on the operations.
+ Appendix A Preprocessing and Postprocessing of Backup and Restoration
This appendix describes shell scripts used for preprocessing and postprocessing for backup and restoration.
+ Appendix B Sample Shell Scripts for Backup Operations
This appendix describes sample shell scripts for backup operations for Softek AdvancedCopy Manager.
+ Appendix C Replication Scripts
This appendix describes replication scripts used by Softek AdvancedCopy Manager.
ted 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
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.
i
ii
· 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. · Solaris (TM) Operating Environment is referred to as Solaris OE. · 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 elsewhere.
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.
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.
1.1.1 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 If work uses a database other than Oracle or uses a general file system, the time that work is interrupted is still significantly reduced.
In addition, operations management can be used as a remote copy function for remote sites to create remote copies between Fujitsu disk array units on a SAN-WAN-SAN connection. Remote copying can also provide a disaster recovery solution because disk arrays containing backup data can be stored in an earthquake-resistant location.
1.1.2 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 Shell script for Backup Operations" about the backup method of the database of Oracle.
Moreover it can back up in Softek AdvancedCopy Manager, without cooperating with SynfinityDISK and stopping SynfinityDISK also under mirror volume (SDX object) environment.
1.1.3 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.
1.2 Product Configuration of Softek AdvancedCopy Manag er
1.2.1 Function system
[Table 1.1 Functions]
Function name Description
Manager of Softek AdvancedCopy Manager
Operates on the Storage management server, and two or more Storage servers are managed. Backup management and replication management are performed.
Agent of Softek AdvancedCopy Manager
Operates on the Storage server with which the storage device is connected. Backup management and replication management are performed.
1
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
[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 ]
1.2.2 System configuration
The system configuration of Softek AdvancedCopy Manager is shown below.
3
[Figure 1.4 System configuration used when the storage management server runs on Windo wsNT/2000]
4
[Figure 1.5 System configuration used when the storage management server runs on Solaris OE / Linux]
1.3 Function Overview of Softek AdvancedCopy Manager
1.3.1 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
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
(NetBackup, NetWorker, TivoliStorageManager) 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.
1.3.2 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.
1.3.3 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
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
1.4.1 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
1.4.2 Software requirements
1.4.2.1 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
Solaris 2.6 OE, Solaris 7 OE, Solaris 8 OE, Solaris 9 OE
Required Support OS
Sun WebServer 1.0 or later Apache 1.3 or later InfoProviderPro 2.0 or later
Required Web server
Conditionally required
Multipath disk control (MPHD) 2.0 or later
Conditionally required
When a Storage management server serves as a Storage server, and when multipass disk control is carried out
Multipath disk control load balance option (MPLB) 2.0 or later
Conditionally required
When a Storage management server serves as a Storage server, and when it carries out multipass disk control and load distribution of a path is carried out further
GR multipath driver (GRMPD) 1.0 for Solaris OE
Conditionally required
When a Storage management server serves as a Storage server, and when it carries out multipass disk control and load distribution of a path is carried out further
7
[Table 1.3 Software requirements for Agent of Softek AdvancedCopy Manager]
Product name Requirement Remarks
Solaris 2.6 OE, Solaris 7 OE, Solaris 8 OE, Solaris 9 OE Required Support OS
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
Required The manager product of Softek AdvancedCopy Manager
SynfinityCLUSTER 2.0 PRIMECLUSTER V4.1 VERITAS Cluster Server 2.0
Conditionally required
For cluster operation with Agent of Softek AdvancedCopy Manager
Multipath disk control (MPHD) 2.0 or later Conditionally required For multipath disk control
Multipath disk control load balance option (MPLB) 2.0 or later
Conditionally required
Conditionally required
1.4.2.3 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
The following devices are supported in backup management and replication management. · Sd driver resources · Hddv driver resources · MPHD resources · MPLB resources Moreover, the unit of management is a disk partition (slice) unit.
When you carry out for a SDX object by backup management and replication management, please specify from it being necessary to specify and process the physical disk which constitutes logical volume in the form of the following.
Device name Explanation
Logical volume name:c?t?d?
Logical volume nameBlock device name c?t?d? of logic volume:Physical disk name (value of DEVNAM of sdxinfo)
The stripe volume created by the stripe group by the SDX object and the volume created by the concatenation group which is not supported.
8
Chapter 2 Starting and Stopping Daemons
This chapter explains how to activate and stop different daemons provided by Softek AdvancedCopy Manager.
For more information on how to activate and stop the daemons described in this chapter, see chapter 9.4.5, "Starting and stopping AdvancedCopy Manager daemons."
2.1 Daemons that Configure Softek AdvancedCopy Manag er
Manager of Softek AdvancedCopy Manager is configured with the following daemons:
[Table 2.1 Types of daemons that configure Manager of Softek AdvancedCopy Manager]
Daemon type Description
The communication daemon
The RMI daemon Manages the GUI display
The RDB daemon Accesses the repository
The authentication daemon Manages the authentication feature
Agent of Softek AdvancedCopy Manager is configured with the following daemons:
[Table 2.2 Types of daemons that configure Agent of Softek AdvancedCopy Manager]
Daemon type Description
2.2 Starting a Daemons
Daemons must be activated on the Storage management server, Storage server, and SP server.
Normally, they are automatically activated. However, if activation fails or the daemon is stopped, activate the daemon on each server by executing the following command:
# /opt/swstorage/bin/startacm
About starting the daemon on the cluster operation, see Chapter 6, "Starting and Stopping a Daemon," in the Softek AdvancedCopy Manager Operator's Guide for cluster environment.
2.3 Stopping a Daemons
Stop daemons from the Storage management server and the Storage server. Normally, they are automatically stopped when the system stops.
To stop a daemon on a server, execute the following command on the server:
# /opt/swstorage/bin/stopacm
About stopping the daemon on the cluster operation, see Chapter 6, "Starting and Stopping a Daemon," in the Softek AdvancedCopy Manager Operator's Guide for cluster environment.
9
10
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: · Each user name consists of two to eight alphanumeric characters. (The colon symbol cannot be used.) · The password for the user name consists of 28 alphanumeric characters.
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 Description
Write permission
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.
Execute permission
Allows you to perform a series of storage operations and read information. An execute permission includes a read permission.
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
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 Yes No No
Acquisition and reflection of information on specific device Yes No No
Deleting device information Yes No No
Yes: Enabled No: Disabled
11
· 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
Backup Yes Yes No
Restoration Yes Yes No
Recovery Yes Yes No
Start Backup Synchronization processing Yes Yes No
Cancel Backup synchronization processing 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.
3.3.1 Flow of setup
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".
12
1. Specify the URL of the initial window of Softek AdvancedCopy Manager to display the initial window. 2. After the following login window is displayed, specify a root user name and the password for the root user, and
then 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.
5. From the operation menu, select [Add user]. The following window will be displayed.
13
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 name is one that is registered on the Storage management server. · 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.
Chapter 4 Backup Operations (Normal Transaction Volumes
This chapter explains backup operations for normal transaction volumes of Softek AdvancedCopy Manager.
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 maintain status has been achieved.
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]
4.1.1 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. Execute the backup execution command ((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.
15
- 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.
4.1.2 Synchronized high-speed backup processing
The Equivalent Copy (EC) or The 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. Execute the backup synchronized processing start command ((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. Execute the backup execution command ((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.
16
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. · The backup function which used ROPC is restricted to the disk array equipment in the same Storage server.
4.1.3 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.
17
If transaction volume contents are rewritten in the period between collection of the latest backup volume and a subsequent restore operation, rewritten data is not assured.
[Figure 4.4 Notes on restore operations in Softek AdvancedCopy Manager]
4.2 Operation Design
This chapter describes the backup operation on Softek AdvancedCopy Manager.
Design a backup operation as follows: · 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
4.2.1 Deciding a server on which the backup operation should be performed
Determine the server that will be used to perform backup.
The following servers can be used to perform backup: · 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.
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.
18
[Figure 4.5 Configuration of servers on which the backup operation should be performed]
4.2.2 Deciding a backup target
Softek AdvancedCopy Manager backs up data in units of slices. A slice 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".
Slices must be allocated for transaction volumes in the following manner:
· Create slices so that no VTOC is contained in them. · No slice may be duplicated on the same disk.
For backup targets, do not select slices in which a system is stored or Softek AdvancedCopy Manager is installed.
For any slice that defines an entire volume, do not register it as a transaction volume.
No file system of SynfinityFILE consisting of multiple slices can be processed. When backing up or
19
restoring a file system of SynfinityFILE consisting of multiple slices, handle the multiple slices at the same time while they are unmounted.
4.2.3 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 4.4.10, "Setting a backup policy".
4.2.4 Preparing a backup volume
Prepare the backup volume.
The backup unit of Softek AdvancedCopy Manager is a slice. In Softek AdvancedCopy Manager, the slice 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.
The backup volume size must equal the transaction volume size. The number of backup volumes used for snapshot-type high-speed buffer operations and that for synchronous high-speed buffer operations are listed below:
Backup Number of required backup volumes
For snapshot fast backup 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 Number of required backup volumes
For snapshot fast backup
Total number of backup generations in the registered backup policies + number of generations in the new backup policy being set
For synchronized high-speed backup
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
Slices must be allocated for backup volumes in the following manner: · Create slices so that no VTOC is contained in them. · No slice may be duplicated on the same disk. In a backup volume, there is no need to create a slice that
indicates a whole volume, such as slice2.
20
For backup volumes, do not select disks in which a system is stored or Softek AdvancedCopy Manager is installed.
For information on setting a backup volume, see Chapter 4.4.8, "Setting the operation type for a device".
4.2.5 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 backup synchronous processing start command and the backup execution command must be started separately, as described below.
++Starting the backup synchronous processing start command
At first, theoretically calculate the time required for the synchronized backup processing. Execute the backup synchronous 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:
21
· 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.
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 backup synchronous 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.
22
4.4 Preparations
The following preparations are required before the backup operation is started.
23
4.4.1 Activating daemons
Before the backup operation is started, the daemons of Softek AdvancedCopy Manager must be started on the storage management server and the Storage servers. Normally, these daemons are automatically started up when the system is started. If the startup of a daemon fails for some reason or if a daemon has been stopped, you need to start the daemon on each server. For information on starting a daemon, see Chapter 2, "Starting and Stopping a Daemons ".
4.4.2 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.
4.4.3 Starting the initial window
Specify the following URL to start the initial window of Softek AdvancedCopy Manager.
http://storage-management-server-address(:port-number)/swstorage/index.html
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.
4.4.4 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.
24
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 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).
4.4.5 Fetching device information on a storage server
Before the backup management can be performed, device information on a storage server must be temporarily stored to 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.
25
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).
After performing the above operations, press the OK button to reflect 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 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.
4.4.6 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.
26
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 displayed on the left side. Then, select the storage server in a list panel 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 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.
4.4.8 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 partitions, 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:
27
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).
For any slice that defines an entire volume, do not register it as a transaction volume.
If the slice configuration of a transaction volume is changed, 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.
Backup volume needs to be the same size as operating volume.
28
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 the " 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.
4.4.9 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)
/etc/opt/FJSVswsts/logical-node-name(*1)/data/DEFAULT/check.ini
(*1) Logical node name of AdvancedCopy Manager specified during setting up of a cluster.
Code as follows:
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.
4.4.10 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.
29
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 view, 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).
4.4.11 Customizing preprocessing and postprocessing scripts
In the case of one of the two operations explained below, the backup preprocessing and postprocessing scripts need to be customized. · When, because of an operational reason, you want to avoid unmount/mount processing for a transaction
volume where a file system is constructed · When you want to add special preprocessing and postprocessing to the preprocessing and postprocessing
scripts Refer to Appendix A, "Preprocessing and Postprocessing of Backup and Restoration," for details on the customization.
4.4.12 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.
30
4.4.12.1 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 (newline 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.)
· When defining output place backup volume to a log group, you have to carry out description about all operating volumes into a single file. (Description must not be straddling two or more files.)
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".
Softek AdvancedCopy Manager has two kinds of backup operation as follows. · Snapshot fast backup operations · Synchronous high-speed backup operations
4.5.1 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.
31
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., /home/usr1/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.
32
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.
4.5.2 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.
33
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., /home/usr1/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.
34
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
35
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.
4.5.3 Performing restoration
This chapter describes restoring a volume or data that has been backed up.
4.5.3.1 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. Restoration is carried out from
the backup volume managed for the newest generation's backup history.
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.
36
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.
8. To check the latest information, either: - Click the [PF5] key, or - Select [Refresh] from the View menu. 9. If the transaction was stopped in 1, restart it.
37
· You can perform restoration also using the restore execution command. · You can check the restore status also using the restore execution status display command (swstbackstat). · 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.)
4.5.3.2 Restoring an individual file
Restore an individual file as shown below. Note that you cannot restore an individual file on the GUI window. 1. Mount backup volume. To check backup volume by the history list view or executing history information display
command. 2. Copy files to restore by the cp command. 3. Unmount backup volume.
4.5.4 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.
4.5.4.1 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.
4.5.4.2 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.
38
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.
4.6.1 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 4.4.10, "Setting backup policies".
4.6.2 Deleting a device
This chapter describes deleting a device depending on the device type.
4.6.2.1 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 4.5.4.2,
"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.
39
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.
4.6.2.2 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.
40
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.
4.6.3 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
4.4.10, "Setting backup policy".
4.6.4 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 4.5.4.2, "Deleting a backup history". 3. Delete the backup policy for all the transaction volumes on the storage server to be deleted.
41
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.
42
Carefully check the server name and click the [OK] button. You can delete a server information also using the server information deletion command (stgxfwcmdelsrv).
4.7 Stopping the Operation
To stop a backup operation, stop daemons on the Storage server. Normally, they are automatically stopped when the system stops.
You can stop an individual daemon if you need to do so for some reason. For more information, see Chapter 2, "Starting and Stopping Daemons".
· When the daemons stop, all functions of AdvancedCopy Manager running on the storage server stop. · Stop daemons on a storage management server only after checking that all the storage servers that it
manages are stopped.
[Deleted]
45
46
This chapter describes backup with the SP Series.
6.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 6.1 Backup management configuration ]
6.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
6.2.1 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
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.
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.
48
[Figure 6.2 Example of Storage management server and Storage server configuration]
6.2.2 Determining the backup target
To perform backup management in linkage with models of the SP series, define the backup target as a transaction
49
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.
Please make applicable to backup neither the disk with which the system is stored, nor the disk with which Softek AdvancedCopy Manager is installed.
6.2.3 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
6.2.4 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.
6.3 Flow of Operation
The following figure shows the flow of backup with the SP series.
50
Before the start of backup, the following preparations are required.
6.4.1 Activating daemons
Before starting a backup operation, daemons on the Storage management server, Storage servers, and SP servers must be activated. Normally, they are automatically activated.
51
When starting goes wrong for a certain reason, and when a demon is stopped at once, it is necessary to start a demon by each server. Please Refer to Chapter 2 "Starting and Stopping daemons" of this Manual of Demon about Starting of Demon.
6.4.2 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.
6.4.3 Starting the initial window
Specify the following URL to start the Softek AdvancedCopy Manager initial window:
http://storage-management-server-address(:port-number)/swstorage/index.html
The following GUI (server list view) starts.
When applying only by the command, without using GUI, it is not necessary to perform this operation.
6.4.4 Registering Storage server and SP 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.
52
For 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.
6.4.5 Fetching device information on a storage server
Before the backup management can be performed, device information on a storage server must be temporarily stored to 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. Information about the hardware of the SP server need not be acquired because the SP server is not managed by AdvancedCopy Manager.
53
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 will be displayed.
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).
After performing the above operation, click the OK button to reflect the configuration information. For an explanation on the Softek AdvancedCopy Manager device name, see Chapter 1.5, "Managing a Device on Softek AdvancedCopy Manager", in the Softek AdvancedCopy Manager Operator's Guide (Windows version).
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 device information collection/reflection command (stgxfwcmsetdev).
54
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.
6.4.6 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.
6.4.7 Setting the environment for a backup operation server
Set the environment for each storage server. When [Set Storage Server Configuration 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.
55
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.
6.4.8 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 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 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).
56
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.
Please do not register the slice which defined the whole volume as operating volume.
When the slice composition of the volume set up as operating volume etc. is changed, since it once deletes from registration of transaction volume and a Storage server subordinate's device information is taken in again, it is necessary to reregister by the device information setting command.
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.
6.4.9 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
6.4.10 Customizing preprocessing and postprocessing scripts
In the case of one of the two operations explained below, the backup preprocessing and postprocessing scripts need to be customized. · When, because of an operational reason, you want to avoid unmount/mount processing for a transaction
volume where a file system is constructed · When you want to add special preprocessing and postprocessing to the preprocessing and postprocessing
scripts Refer to Appendix A, "Preprocessing and Postprocessing of Backup and Restoration," for details on the customization.
6.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 6.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.
57
6.5.1 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.
+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. It 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.
6.5.2 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.
6.5.3 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.
6.6 Stopping Backup
To stop the backup, stop the service on the storage server. In general, the service stops when the system stops.
It is possible to also make it stop individually to stop a demon by a certain reason. For more Details, see Chapter 2 "Starting and Stopping Daemons".
· When the service stops, all functions of AdvancedCopy Manager running on the Storage server stop. · Before stopping the service or daemon running on the Storage management server, confirm that the
operations on all managed Storage servers have stopped.
6.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
58
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.
6.7.1 Reflecting changes
After starting the Web GUI of Softek AdvancedCopy Manager, refer to Chapter 1.2.6.5, "Changing GR cabinet management information of the SP series," in the Solaris OE version Softek AdvancedCopy Manager User's Guide, to perform the operation to reflect changes.
59
60
Chapter 7 Replication Operation
This chapter explains Softek AdvancedCopy Manager replication in a Solaris OE system. Softek AdvancedCopy Manager uses a slice as the replication unit. In this manual, the term "volume" is used instead of "slice."
7.1 Overview