Restoring data using the LREP tool
You can restore data from a secondary storage system to the primary storage system using the LREP tool, without having to transfer data over the network.
At the data center, using lrep_reader, the baseline transfer is done from SEC1 to a Zip drive (drive letter E) connected to a Windows client, CL1. The Zip drive is shipped to the remote office where a second Windows client, CL2, uses
lrep_writer to write data from the Zip drive to WIN1.
Note
The restore operation of Microsoft SQL Server database is supported only on Windows platforms.
Restoring data from a secondary
storage system to the primary storage system
Complete the following steps to resynchronize a relationship after restoring the data from the secondary storage system (SEC1) to the primary storage system (PRI1) using the LREP tool.
At the data center: Assume that the LREP tool is installed on the Windows client CL1, and you have to restore the data to the remote office PRI1.
Step Action
1 Run the following command on the directory of the client (CL1) on which lrep_reader is installed:
lrep_reader -O [-c] [-e] [-m] -p snapvault_restore -o Zip_dirpath@0 -f prim_host -q prim_vol [-l reader.log]
sec:/vol/sec_vol/sec_qtree
Note
When the -c option is used, the output files generated at Zip_dirpath are compressed. When the -e option is used, you are prompted to enter and reconfirm the encryption password.
Example:
C:\> lrep_reader -O -p snapvault_restore -o E:\rest@0 -f PRI1 -q /vol/vol1/backup [-l reader.log]
SEC1:/vol/data/Logic Transfer started.
Use 'snapvault status' on source to monitor progress.
Transfer done.
Verify by using 'snapvault status' on storage system.
At the remote office: Assume that the LREP tool is installed on the Windows client CL2 and the Zip drive is connected to CL2. Complete the following step:
Step Action
1 Enter the following command in the directory of the system (CL2) on which lrep_writer is installed:
lrep_writer -O -p snapvault_restore Zip_dirpath
Note
If the files at Zip_dirpath are compressed, lrep_writer internally decompress the files. If the files are encrypted, lrep_writer prompts you to enter the decryption password and internally decrypt the files.
Example:
C:\> lrep_writer -O -p snapvault_restore E:\rest lrep_writer: Will read 1 files from prefix e:\rest Waiting for connection.
Use snapvault start command on secondary to create a relationship
2 Run the following command on the primary storage system (PRI1) to start the data transfer:
snapvault restore -S CL2:Zip_dirpath prim_vol
Example:
PRI1> snapvault restore -S CL2:E:\rest /vol/vol1/backup
Restoring a Microsoft SQL Server database
Complete the following steps to restore a Microsoft SQL server database from the secondary storage system (SEC1) to the Open Systems SnapVault primary server (WIN1) using the LREP tool.
Assume that Sample_DB is the Microsoft SQL Server database that you want to restore on the primary storage system WIN1.
At the data center: Assume that the LREP tool is installed on a Windows client CL1. Complete the following step:
3 To resynchronize the relationship on the secondary storage system, run the following command on the secondary storage system (SEC1):
snapvault start -r -S prim_host:prim_vol /vol/sec_vol/sec_qtree
Example:
SEC1> snapvault start -r -S PRI1:/vol/vol1/backup /vol/data/Logic
The resync base snapshot will be: snapshot name Resync may alter the data in this qtree.
Are you sure you want to resync the qtree? y Wed Mar 21 15:33:33 GMT
[replication.dst.resync.success:notice]: SnapVault resync of /vol/data/Logic to PRI1:/vol/vol1/backup was successful.
Snapvault configuration for the qtree has been set.
Transfer started.
Monitor progress with 'snapvault status' or the snapmirror log.
Step Action
At the remote office: Assume that the LREP tool is installed on a Windows client (CL2). Complete the following steps:
Step Action
1 Run the following command in the directory of the client (CL1) on which lrep_reader is installed:
lrep_reader [-c] [-e][-m] -p snapvault_restore -A -o Zip_dirpath@0 -f WIN1 -q C:\data [-l reader.log]
sec:/vol/sec_vol/sec_qtree
Note
When the -c option is used, the output files generated at
Zip_dirpath are compressed. When the -e option is used, you are prompted to enter and reconfirm the encryption password.
Example:
C:\> lrep_reader -p snapvault_restore -A -o E:\rest@1 F:\rest1@0 -f WIN1 -q C:\data [-l reader.log]
SEC1:/vol/data/Logic Transfer started.
Use 'snapvault status' on source to monitor progress.
Transfer done.
Verify by using 'snapvault status' on storage system.
E:\rest and F:\rest1 are existing empty directories where the LREP files are created. One LREP file is created in the E:\rest directory and the remaining files are created in the F:\rest1 directory.
Step Action
1 Connect the Zip drive to the system. Enter the following command in the directory (CL2) on which lrep_writer is installed:
lrep_writer -p snapvault_restore -A Zip_dirpath
Note
If the files at Zip_dirpath are compressed, lrep_writer internally decompresses the files. If the files are encrypted, lrep_writer prompts you to enter the decryption password and internally decrypts the files.
Example:
C:\> lrep_writer -p snapvault_restore -A E:\rest F:\rest1
lrep_writer: Will read 1 files from prefix E:\rest lrep_writer: Will read 1 files from prefix F:\rest1 Waiting for connection.
Use snapvault start command on secondary to create a relationship
2 Start data transfer by running the following command on the Open Systems SnapVault primary server (WIN1):
snapvault restore -S CL2:Zip_dirpath prim_apppath
Note
Before you start data transfer, select the Enable restart/resync on restore check box in the Configurator GUI to enable restart or resynchronization.
Example:
C:\> snapvault restore -S CL2:E:\rest app:mssql:OSSVMSSQL:Sample_DB
3 Check the status by running the following command:
snapvault status
Example:
C:\> snapvault status Snapvault primary is ON
Source Destination State Lag Status SEC1:/vol/data/Logic CL2:C:\data Broken-off - Idle 4 Resynchronize the relationship on the secondary storage system by
running the following command on the secondary storage system (SEC1):
snapvault start -r -S prim_host:apppath /vol/sec_vol/sec_qtree
Example:
SEC1> snapvault start -r -S
WIN1:app:mssql:OSSVMSSQL:Sample_DB /vol/data/Logic The resync base snapshot will be: snapshot name Resync may alter the data in this qtree.
Are you sure you want to resync the qtree? y Wed Mar 21 15:33:33 GMT
[replication.dst.resync.success:notice]: SnapVault resync of /vol/data/Logic to
WIN1:app:mssql:OSSVMSSQL:Sample_DB was successful.
Snapvault configuration for the qtree has been set.
Transfer started.
Monitor progress with 'snapvault status' or the snapmirror log.
Step Action