15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Status Codes<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Media Manager Status Code: 159<br />

Message: the volume guid is not unique in the database<br />

Explanation: A volume entry being added to or changed in the volume database had an<br />

RSM GUID specified which was a duplicate of the RSM GUID <strong>for</strong> another volume already<br />

in the volume database. All volumes in a volume database must have an RSM GUID that<br />

is either unique or null. (RSM is the Microsoft Removable Storage Manager, and GUID is a<br />

Global Unique Identifier.)<br />

Recommended Action:<br />

1. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error.<br />

a. Enable debug logging by creating the necessary directories/folders. Increase the<br />

level of verbosity by adding the VERBOSE option in the vm.conf file and<br />

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

b. Retry the operation and examine the logs.<br />

2. Try the following procedure:<br />

a. From the daemon debug log file, determine the offset of the volume that has an<br />

RSM GUID conflict with the volume entry being added or changed. The offset is<br />

the index of the volume in the volume database.<br />

b. Dump out all volume records in the volume configuration <strong>for</strong> the targeted<br />

volume database host using the vmdb_dump command. Look up the volume<br />

offset indicated in the debug log file, noting the associated RSM GUID, which is<br />

the field volume_guid.<br />

The condition may have occurred because the media name <strong>for</strong> a volume may<br />

have been changed in the RSM media configuration, followed by a change to the<br />

volume configuration in Media Manager that caused a new volume to be added.<br />

Since RSM media names are equivalent to media IDs, if the existing media ID is<br />

not deleted from the volume configuration, the conflict appears when the new<br />

volume is added. Do not change media names in RSM if volume entries have<br />

already been established <strong>for</strong> the media in the volume configuration.<br />

Media Manager Status Code: 160<br />

Message: the global device database device type is invalid<br />

Explanation: An invalid device type appeared in a request to modify the device<br />

configuration.<br />

278 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

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

Saved successfully!

Ooh no, something went wrong!