Forum Discussion

SteveLaw's avatar
SteveLaw
Level 5
11 years ago

Adding a robot / tape drive writes to our environment

Hi,

I have a Netbackup 7.5 Enterpise environment, currently using Data Domain. We've had a TLD robot with one tape drive (so far) added to the environment but I need help on how to proceed. 

We have a mixed Windows / Unix environment. The robot control host is a Unix server that is already configured as a Data Domain media server that currently only backs itself up. I have added the robot to Netbackup using the Configure Storage Devices wizard. The ultimate purpose of this robot will be to act as the final stage of our backup process: 1) write backup to local Data Domain, 2) replicate to remote data domain on 2nd site, 3) write production backups for long-term retention to tape. 

Where do I go from here? What I want is for a media server - not necessarily the one that is the robotic control host - to be able to read data from Data Domain and write it to the robot/tape. I assume this will be the final stage of an SLP used for a backup policy. 

At the moment I don't even know how to make any media server write to tape. For Data Domain I do the following:

  • Create a storage unit on Data Domain and add one media server to it. 
  • Create an SLP for the storage unit that duplicates to a matching storage unit on the remote data domain
  • Install the DDBoost plugin to the media server then run the commands to configure it to write to Data Domain:
    • nbdevconfig -creatests -stype DataDomain -storage_server [data_domain_box] -media_server [media_server]
    • tpconfig -add -storage_server [data domain box] -stype DataDomain -sts_user_id ostuser -password password

....and I'm good to go. 

If I want to make the current robotic control host (which obviously can see the robot on the san fabric) write it's own data to a tape, what do I need to do?

From there, how do I configure a replication to tape from Data Domain? I've scoured through the standard documentation but can't find any useful info on how to put this together. 

Thanks!

  • You are pretty much there, you say the robot control host is configured, so to make this street write to tape it also needs to see a tape drive at os level. Once done rerun the wizard to configure the tape drive to the server as a robotic drive, and create a storage unit. 

     

    Insert tapes, configure the tapes as the same density as the drive, eg. chart, run the inventory and then select that storage unit in a policy. 

     

    The device configeration guide contains the steps in a little more detail, but the above is pretty much it. 

  • You are pretty much there, you say the robot control host is configured, so to make this street write to tape it also needs to see a tape drive at os level. Once done rerun the wizard to configure the tape drive to the server as a robotic drive, and create a storage unit. 

     

    Insert tapes, configure the tapes as the same density as the drive, eg. chart, run the inventory and then select that storage unit in a policy. 

     

    The device configeration guide contains the steps in a little more detail, but the above is pretty much it. 

  • Thanks mph999. Setting up a tape robot/drives is a very different procedure to using Data Domain. Took a while to get my head round it but worked through the Device Manager doc as suggested and now it's all come together. 

  • Pleased I could help, both are accessed via storage units (for backups anyway)so there is something similar there.

    You may wish to consider some tuning to get the best performance.

    On the media server in .../netbackup/db/config (same path for windows/ unix) create two files with these names (be sure windows doesn't add any suffix)

    SIZE_DATA_BUFFERS

    NUMBER_DATA_BUFFERS

    Add into the size file, 262144

    Add into numbers file 128

    See how that performs.

    M