DB2 Version 10.1 for Linux, UNIX, and Windows
DB2 Version 10.1 for Linux, UNIX, and Windows
By providing your own script for snapshot operations, you can use storage hardware that does not provide a vendor library.
A script specifies the type of snapshot operation that you want performed, as well as some additional options. You specify the script name with the -script parameter for the appropriate command or API. The library for DB2® ACS invokes the script at various times through the operation.
You have to create the script yourself and ensure that it is executable. There is a sample script called libacssc.sh provided in samples/BARVendor for your reference. The sample script creates one tar file containing the database files and, if logs are included, a second one for the log files. You can use the sample script as a template for your own script, with the appropriate modifications that set it up for your storage device. You would probably want to remove the section that creates the tar file.
During a snapshot backup, the script extracts the information that is required for the current phase from the protocol file and runs the required actions for creating the snapshot. The script writes progress information to the protocol file for debugging reasons.
During snapshot restores the protocol files that were written during snapshots are read, and new protocol files are written (to the same repository) to show the progress of the restore operation. Every restore operation writes a new protocol file. If the restore is successful, the corresponding protocol file is removed. If the operation fails, the protocol file remains for debugging purposes.
When a snapshot backup image is deleted, the protocol files that were written during snapshots are read, and new protocol files are written (to the same repository) to show the progress of the delete operation. If the delete operation is successful, the corresponding protocol file is removed. If the operation fails, the protocol file remains for debugging purposes.