Forum Discussion
All NetBackup entities, i.e. Master or Media or Client, all maintain their own private cache of names and IPs in case DNS goes AWOL. So, when changing names of anything, then you always need to execute this command, and usually it is best to execute this command on all three layers, i.e Master, all Medias and Appliances, and on the client itself:
bpclntcmd -clear_host_cache
Hi sdo
Thanks for your reply first. Yes, I executed the following command on the Master, Media servers and client.
bpclntcmd -clear_host_cache
Consequently, the backups still worked fine on the Master system. I am confused that the backups should have failed without renewing the certificate after change the hostname of the client.
- sdo5 years agoModerator
Hi - the fact that client name change does not break certification must be by design. With certification when clients are initially installed they select (self-create and self-assign) for themselves a "host GUID". And it is this "host GUID" which is certificated, not a client name. Hence clients still work after changing name.
Related Content
- 10 years ago
- 11 years ago
- 11 years ago
- 9 years ago