Have you started by verifying hostname lookup between DD and media server?
You need to add DD to media server hosts file and the media server IP/hostname on the DD:
net hosts add ipaddr {host | "alias host"}
Your Dedupe Media server is still a Media server under NBU and config will be no different to any other media server.
Extract from DD for NBU admin guide:
Media server configuration consists of the following procedures:
• registering each Data Domain system;
• adding credentials for each media server that is to communicate with a Data Domain system;
• creating disk pools;
• creating storage units, which are collections of disk pools; and
• setting backup policies.
Note the step before disk pool(s) can be added.
More extracts from manual:
Register the Data Domain systems
1. On the media server, start the backup application’s services.
See NetBackup Services on page 23. (Unix: nbrmms, Win: NBU Remote Manager and Monitor Service)
2. Verify that the plug-in is detected by the backup application by entering:
# bpstsinfo -pi
The output shows the vendor version, which is the plug-in version, and the build version, which is the OST API version.
3. Register a Data Domain system by entering:
# nbdevconfig -creatests -st 9 -stype DataDomain -storage_server <DD-name> -media_server <media-server>
4. Repeat the above procedure for each OST-enabled Data Domain system.
Add credentials
1. On a media server that is to communicate with a Data Domain system, enter:
# tpconfig -add -storage_server <DD-name> -stype DataDomain -sts_user_id username -password password
2. Repeat the above step for each media server that is to communicate with a specific Data Domain system.
Creating Disk Pools
Here the manual describe steps to create disk pool for DD-name (Storage Server, not media server)
Next you create STU for the disk pool where you can add all the media servers that can access the STU.
RiaanBadenhorst
