Update Remote Host on DDBoost Association
Hello Community, We recently relocated our backup environment to a new physical location which forced us to change the domain suffix of our NBU environment and Data Domain. The prefix/hostname has stayed the same. We have NBU AIR configured with DDBOOST/EMC Data Domains. So initially we used this similar article to configure NBU Air for a Data Domain (https://www.veritas.com/support/en_US/article.100015147_ however with the move now the remote host information has changed and should be updated. Can this be edited or does the association have to be destroyed and recreated? Sorry for the lame dns suffixes but had to generalize it.. original location: westcoast.acme.corp new location: eastcoast.acme.corp So westcoast.acme.corp needs to be updated to eastcoast.acme.corp ddboost association show Local Storage Unit Direction Remote Host Remote Storage Unit Import To ------------------ -------------- ----------------------- ------------------- --------- air_lsu replicate-from dest.westcoast.acme.corp remote_local local_lsu replicate-to dest.westcoast.acme.corp remote_air_lsu - ------------------ -------------- ----------------------- ------------------- --------- Thanks so much.938Views0likes1CommentNetbackup value and planning
Dear All, Sorry if I send the message to improper place, but I did not find better. This converstaion is going to be a bit deep but I try to summ up. I am in front of change and planning our outdated backup solution. Presently we have NB 7.5 master servers (2) in windows 2008 they are on our outdated HP servers with EMC vnx dedupe storage. The deduped data is around 8-10TB so this looks not a big ammount also some more on tape. Backups mostly from vmware and some oracle rman backups with couple physical server backups.(with one drs site) Presently we are on the planning phase. Costs and investment budget are low :(. Our netbackup licence is still purchased for this year. I still a bit clueless. As for the on premis netbackup appliance looks the best solution but very expensive. Other idea was data domain with NB but that is not really good because it also needs to buy new servers for master, plus it also needs NB licences yearly for continuity. In that case we should rather move to a less expensive simple backup solution other storage solution. Besides if we move to a different backup solution nb msdp should be migrated to the new enviroment. I am also not sure how complicated it should be or that is possible at all to migrate all the data. So many question and still not know where to move.Solved1.5KViews0likes3CommentsOST upgrade
Hi, I need to upgrade OST plugin on Linux Media servers 7.7.2 because we have Data Domain OS upgrade lined up. Current OST version is 2.6.x and plan is to upgrade it to 3.2.5.0. As per DD Documentation i just need to stop NBU service on media server and install OST binaries and it will overwrite old OST binaries. My question is do i need to make any other change in NBU or DD for upgrading OST plugin and making it work except stopping NBU services and simply installing OST binaries?1.3KViews0likes2CommentsDual NIC Media Server credentials already exist - OST / Data Domain
Hi all, I have a new Media Server with dual NICs, separate IP address and hostname for each, e.g. nbuserver-a & nbuserver-b. Both entries registered as Media Servers in the NBU domain. When attempting to add these two entities to the list of Media Servers able to address a Storage Server (OST-based Data Domain), I can add one but not the other. Error message advises 'Credentials already exist (99)'when attempting to add the second - as in picture attached. Any idea where I'm going wrong?1.1KViews0likes3Comments