Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- VOX
- Data Protection
- NetBackup
- VMGLOB
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
VMGLOB
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2009 02:44 AM
Hello,
dawer:/export/home/sario >vmglob -listall -b | grep S85NUS01-9940B-50
drive S85NUS01-9940B-50 479000019853 buwere
drive S85NUS01-9940B-50 479002036354 dawer
drive S85NUS01-9940B-50 479000019853 wecserwe
drive S85NUS01-9940B-50 479000019853 werwer
drive S85NUS01-9940B-50 479000019853 bhjtyj
drive S85NUS01-9940B-50 479000019853 bnjgyuu
drive S85NUS01-9940B-50 479000019853 gironmou
i want to change the serial number of the drive in dawer server. Please let me know the command to change the same. all the drives are SSO shared.
Thanks and regards,
Rupert
Labels:
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2009 05:53 AM
How to replace devices in a shared storage option configuration on NetBackup media servers
http://support.veritas.com/docs/271280
Exact Error Message
Device Configuration must be run on all servers to complete drive replacement
Device Configuration must be run on all servers to complete drive replacement
Details:
This is related to VERITAS NetBackup Enterprise Server (tm) (version 5.x). Step 5 in the Media Manager System Administrator's Guide for Windows (Page 335 - Appendix A) is a little confusing and this document hopes to clarify the steps involved.
If you replace an existing device in your shared drive configuration with a new device, the serial number of the device will likely change. This change can lead to a wrong configuration in Media Manager of the global device database and also the local device databases on each server.
The tpautoconf options used in this procedure are available only with NetBackup release 5.0 or later. Media servers that are also robot control hosts, must be running NetBackup release 5.0 or later to use this procedure
1. Configure the new device on all servers sharing the device. The device must be available through the operating system of each server. This device configuration may require remapping, rediscovery, and possibly a reboot of the operating system (refer to the NetBackup Media Manager Device Configuration Guide for more information).
2. On a server running NetBackup 5.0 or later, run tpautoconf -report_disc on one of the reconfigured servers to produce a list of new and missing hardware. This command will scan for new hardware, and produce a report showing the new and replaced hardware.
3. Ensure that all servers that are sharing the new hardware are up and are running NetBackup services.
4. On a server running NetBackup 5.0 or later, run tpautoconf with the -replace_drive drive_name or -replace_robot robot_number option. Also specify the -path hardware_path option. hardware_path is the new hardware path, as shown in the output of the report created in step 2. The serial number is read from the new hardware device and the media manager global data base is updated. Also any servers (running NetBackup 5.0 or later) sharing the new device will replace the serial number in their local databases.
5. If the new device is a drive, run the device configuration wizard on all servers that are sharing the drive. If the new device is a robot, run the wizard on the server that is the robot control host and on all servers that are running any version of NetBackup 4.5.
Example:
C:\>tpautoconf -replace_drive IBMULT3580-TD22 -path Tape2
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso1
update of local DB on host nbusso1 completed globalDB update for host nbusso1 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso2
update of local DB on host nbusso2 completed globalDB update for host nbusso2 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso3
update of local DB on host nbusso3 completed globalDB update for host nbusso3 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso4
update of local DB on host nbusso4 completed globalDB update for host nbusso4 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso5
update of local DB on host nbusso5 completed globalDB update for host nbusso5 completed
Device Configuration must be run on all servers to complete drive replacement
NOTE:
Step 5 is at times a little confusing when reviewing the output of tpautoconf -replace_drive and reading the description provided in Step 4. In case the device being replaced is a drive, please stop and restart the device manager service on all the hosts sharing the drive.
The last line in the output of Step 4 states "Device Configuration must be run on all servers to complete drive replacement." Restarting the Device Manager service on all hosts sharing the affected drive should be sufficient for all non-clustered NetBackup media servers sharing drives using shared storage option.
If you replace an existing device in your shared drive configuration with a new device, the serial number of the device will likely change. This change can lead to a wrong configuration in Media Manager of the global device database and also the local device databases on each server.
The tpautoconf options used in this procedure are available only with NetBackup release 5.0 or later. Media servers that are also robot control hosts, must be running NetBackup release 5.0 or later to use this procedure
1. Configure the new device on all servers sharing the device. The device must be available through the operating system of each server. This device configuration may require remapping, rediscovery, and possibly a reboot of the operating system (refer to the NetBackup Media Manager Device Configuration Guide for more information).
2. On a server running NetBackup 5.0 or later, run tpautoconf -report_disc on one of the reconfigured servers to produce a list of new and missing hardware. This command will scan for new hardware, and produce a report showing the new and replaced hardware.
3. Ensure that all servers that are sharing the new hardware are up and are running NetBackup services.
4. On a server running NetBackup 5.0 or later, run tpautoconf with the -replace_drive drive_name or -replace_robot robot_number option. Also specify the -path hardware_path option. hardware_path is the new hardware path, as shown in the output of the report created in step 2. The serial number is read from the new hardware device and the media manager global data base is updated. Also any servers (running NetBackup 5.0 or later) sharing the new device will replace the serial number in their local databases.
5. If the new device is a drive, run the device configuration wizard on all servers that are sharing the drive. If the new device is a robot, run the wizard on the server that is the robot control host and on all servers that are running any version of NetBackup 4.5.
Example:
C:\>tpautoconf -replace_drive IBMULT3580-TD22 -path Tape2
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso1
update of local DB on host nbusso1 completed globalDB update for host nbusso1 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso2
update of local DB on host nbusso2 completed globalDB update for host nbusso2 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso3
update of local DB on host nbusso3 completed globalDB update for host nbusso3 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso4
update of local DB on host nbusso4 completed globalDB update for host nbusso4 completed
Found a matching device in global DB, IBMULT3580-TD22 on host nbusso5
update of local DB on host nbusso5 completed globalDB update for host nbusso5 completed
Device Configuration must be run on all servers to complete drive replacement
NOTE:
Step 5 is at times a little confusing when reviewing the output of tpautoconf -replace_drive and reading the description provided in Step 4. In case the device being replaced is a drive, please stop and restart the device manager service on all the hosts sharing the drive.
The last line in the output of Step 4 states "Device Configuration must be run on all servers to complete drive replacement." Restarting the Device Manager service on all hosts sharing the affected drive should be sufficient for all non-clustered NetBackup media servers sharing drives using shared storage option.
