cancel
Showing results for 
Search instead for 
Did you mean: 

Robot control host to be moved to master server

MadhanKumar
Level 3

Hi All,

Setup :

Master Server - Solaris10

Media Servers - RHELinux (2 no)

NBU Version - 7.1

New LIb - IBM TS3500

New Drives - 4 HCART2

Existing Drives - 6 HCART3

Visibility - All are visible in master and media servers.

Description :- We got a new library at different location. Need to move all our backups to new library.

As part of making setup ready, configured this new library in previous week end.

The cutover is scheduled for shifting backups to new library now.

Issue :

While configuring the library, observed that the robot control host (TLD 5) is going on media server. I had finished the configuration like that ...

Now I have the doubts as below:

1. Is it mandatory to have robot control host on Master server ? If yes, what's the benefit of it..?

2. If need to move to master server, how to do it ?

3. How to move the backup setup to new infrastructure considering the drive type difference..?

4. What are the precautions to be taken before doing the movement ?

Note - All drives are visible in the master and media servers.  Have performed test backup with new TLD 5 robot and is successful.

Also making setup ready for SL3000 library for old HCART3 tapes restoration.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
1. It is not mandatory to have master as robot control host. Benefit of moving robot control to a media server is that there is less load on the master. 2. Your choice - not mandatory to have the one or the other as control host. If you want the master as control host, delete robot and drives for master and media servers and start again. First choose master only in Device wizard. Once robot and drivers are added, run wizard again, then select master and media servers. 3. Create Storage Units as part of Device Config wizard, then select the new STUs in backup policies. 4. Check STU config for amount of drives you want to allow per media server, fragment size and multiplexing. Ensure that the media to be used with new drives and STUs have matching densities. (All hcart3 ). Ensure that barcodes are unique. You cannot use the same barcode range in the new robot as in the old. You may want to read up on Media ID generation before you inventory new robot for the 1st time. If robot reads all 8 characters of the barcode (including the L# suffix at the end) NBU will use the last 6 characters of the barcode as media-id. Best to add Media-id Generation rule in Inventory Advanced options to specify 1st 6 characters of the barcode.

View solution in original post

1 REPLY 1

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
1. It is not mandatory to have master as robot control host. Benefit of moving robot control to a media server is that there is less load on the master. 2. Your choice - not mandatory to have the one or the other as control host. If you want the master as control host, delete robot and drives for master and media servers and start again. First choose master only in Device wizard. Once robot and drivers are added, run wizard again, then select master and media servers. 3. Create Storage Units as part of Device Config wizard, then select the new STUs in backup policies. 4. Check STU config for amount of drives you want to allow per media server, fragment size and multiplexing. Ensure that the media to be used with new drives and STUs have matching densities. (All hcart3 ). Ensure that barcodes are unique. You cannot use the same barcode range in the new robot as in the old. You may want to read up on Media ID generation before you inventory new robot for the 1st time. If robot reads all 8 characters of the barcode (including the L# suffix at the end) NBU will use the last 6 characters of the barcode as media-id. Best to add Media-id Generation rule in Inventory Advanced options to specify 1st 6 characters of the barcode.