Please note that your text contain messages generated by multiple source/devices.
The obvious problem seems to be network/name resolution - make sure that this still works fine.
Another potential problem reported by 'Data Domin login to dd6800.datadomin FAILED': the password for the DD user account may have expired. So the connection request will be rejected.
What about the possible resolving issue? If some parts cannot resolve other parts, then a login to the dd won't be possible.
Also you like to torment yourself by still using nw8 and vba (which runs avamar under the hood and a nw b&r appliance besides the vba proxies if memory serves me right?) instead of the simpler approach from nw9 onwards, using the nw vproxy appliance to be deployed in each vmware esxi cluster?
I must say, once we got the hang of it, and went through many an issue in mainly nw9, it is fairly easy to setup and configure (only network topology might make things a challenge still). Never had to upgrade/migrate from vba to vproxy based backups, which however also improved in such a way that vproxies could be used for restoring vba backups, no longer requiring the old vba components to be kept as well.
bingo.1
2.4K Posts
0
February 3rd, 2022 05:00
Please note that your text contain messages generated by multiple source/devices.
The obvious problem seems to be network/name resolution - make sure that this still works fine.
Another potential problem reported by 'Data Domin login to dd6800.datadomin FAILED': the password for the DD user account may have expired. So the connection request will be rejected.
shkim0125
2 Posts
0
February 3rd, 2022 17:00
hello bingo.1
Thank you for the reply. I'm not good at English, so I used Google Translate. I hope you understand even if my english is weird.
I had the same thoughts as you. So I created a new pool using a new storage unit in DD. It uses DD's sysadmin account.
However, the above error message still occurs and the backup failed.
barry_beckers
393 Posts
0
February 7th, 2022 16:00
What about the possible resolving issue? If some parts cannot resolve other parts, then a login to the dd won't be possible.
Also you like to torment yourself by still using nw8 and vba (which runs avamar under the hood and a nw b&r appliance besides the vba proxies if memory serves me right?) instead of the simpler approach from nw9 onwards, using the nw vproxy appliance to be deployed in each vmware esxi cluster?
I must say, once we got the hang of it, and went through many an issue in mainly nw9, it is fairly easy to setup and configure (only network topology might make things a challenge still). Never had to upgrade/migrate from vba to vproxy based backups, which however also improved in such a way that vproxies could be used for restoring vba backups, no longer requiring the old vba components to be kept as well.