Hi, we have one location with NetWorker Server (also working as Storage Node).
In this location and in one remote location we connected two DataDomains with DDboost protocol to his server.
Backups were done locally in both locations to DD devices, with cloning beetwen DD devices.
After some time it occured, that in remote location we must deploy NetWorker Storage Node (because not always working "client direct" option on that site).
My question is how must i configure DDboost device in NetWorker that new storage node will have access to its DD in this remote location?
Of course I'd like to be able to do cloning savesets beetwen locations with DDBoost protocol as previous.
Simply the goal is to add Storage Node in remote location and keep already done backups.
Unfortunately documentation is not clear for me in that case.
Yes, I know this. But what should I do to present existing resource with backups that new SN will be able to read and write to IT. By resource i mean "folder and mount point" on DD that was defined in main NW server.
Bingo already answered question - see hint with access information. Eventually, to keep things clear, you can create new set of devices and stage old one where and when needed to new ones... and once done decommission old setup.
Unmounting happens when your device daemon is too busy and gets not update in timely fashion. To keep those "mounted on demand", enable automedia device management on device level.
Hi Bobby, it has been said in this very forum by EMC folks that statement that AMM should not be used with DD is bogus quote from docs - change of mind again? I've been running it that way for past year+ and I see no issues.
bingo.1
1 Rookie
•
2430 Posts
1007
0
Posted June 6th, 2014 07:00
This is what we have in our configuration ...
Device Name:
rd=storage_node:dd_name_device_name
Device access information:
dd_name:/server_name/device_name