HP Archive Backup System for OpenVMS Guide to Operations
Share Embed Flag
Download ePaper

HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

Architecture 11.4 Coordinator 11.4.2 Volume Sets To synchronize access to volumes in a volume set ABS keeps pseudo volume records in the volume database. The pseudo volume starts with “&+” and the volume ID of the first volume in the set. To show the pseudo volumes you have to use the /ABS_VOLSET qualifier. The fields in the volume record are used as follows: • Brand: PID of process which has the volume locked or locked the last time.Do not change! • Description: A reservation bitmap displayed as a 32 hex-digit value. The low-order bit is the general locking bit which means the volume set is in use while the other bits represent which relative volume in the set is used for a write operation. For troubleshooting purposes this can be set to an all zero value by specifying exactly 32 zeroes. • Length: Currently last volume in set by number. Do not change! • Mount Count: Number of savesets on volume set. Do not change! • Pool: The EOT tapemark position expressed in number of tapemarks and a version number. Do not change! 11-8 Architecture

12 Troubleshooting 12.1Save and Restore Requests 12.1.1 Notification of Save/Restore Completion 12.1.2 Log Files 12.1.3 Logical Names The first step to checking the status of save and restore requests is by using the notification options in the environment object. You may set several levels of notification which include start, complete, warning, error and fatal. The notification may be sent by OPCOM or by mail. If you have notification options set, you will receive notification when problems occur with your save and restore requests (or a message about start or completion). In the MDMS GUI, doing a show of the save or restore request will display the last status of the request. A green (success) or red (error) box will be displayed in the upper right corner of the show output. Each save and restore request creates a log file in the ABS$LOG directory when it is run. The log file is named by the request name. This log contains information about the request, the media management activities, the backup command and any output from the backup process. If errors occur it also contains trace information about the error. The last error message generally contains the actual cause of the error. There are some logical names which may be defined at a system level which will cause ABS to log more information in the request log files. You should not set these logical names unless advised to by a HP customer support representative because the log files can grow quite large if you use them. 12.1.4 Alpha Stack Size Logical 12.1.5 Fast Skip Errors If you are running your save/restore request on an OpenVMS Alpha system and you see either ACCVIO or CMA-F-EXCCOP errors in the logs, there is a stack size variable which may eliminate the problem. ABS$COORD_ALPHA_STACKSIZE may be used to increase the stack size beyond the 65536 default. To use the logical, define it at system level to a value which is a multiple of 8192 $ DEFINE/SYSTEM ABS$COORD_ALPHA_STACKSIZE 8192 * x If you receive an ABS_SKIPMARKS_FAILED error there is a logical name which may be defined at system level which turns off the ABS fast skip methods. To disable fast skip do the following command on the affected system: $ DEFINE/SYSTEM ABS_NO_FAST_SKIP TRUE Troubleshooting 12–1

Architecture<br />

11.4 Coordina<strong>to</strong>r<br />

11.4.2 Volume Sets<br />

To synchronize access <strong>to</strong> volumes in a volume set ABS keeps pseudo volume records in the volume<br />

database. The pseudo volume starts with “&+” and the volume ID of the first volume in the<br />

set. To show the pseudo volumes you have <strong>to</strong> use the /ABS_VOLSET qualifier. The fields in the<br />

volume record are used as follows:<br />

• Brand: PID of process which has the volume locked or locked the last time.Do not change!<br />

• Description: A reservation bitmap displayed as a 32 hex-digit value. The low-order bit is<br />

the general locking bit which means the volume set is in use while the other bits represent<br />

which relative volume in the set is used <strong>for</strong> a write operation. For troubleshooting purposes<br />

this can be set <strong>to</strong> an all zero value by specifying exactly 32 zeroes.<br />

• Length: Currently last volume in set by number. Do not change!<br />

• Mount Count: Number of savesets on volume set. Do not change!<br />

• Pool: The EOT tapemark position expressed in number of tapemarks and a version number.<br />

Do not change!<br />

11-8 Architecture

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!