Lets asssume I have a Proxy (called proxy001) and a VM (called vm002).
The Proxy has some backups already scheduled, e.g. "All", NMC, etc.
Now I have created a 3rd Instance of this Client as the vcbproxy_instance and gave it all the Application Information it needs.
The VM vcb_client is created via "Client Backup Configuration" Wizard in the Virtualization Panel from the Configuration Tab.
1st VCB Backup runs successfully, but suddenly (without intervention) the vcbproxy_instance changes to the NMC-Schedule of this client
and therefore loses all the Application Information.
How are vm002 (the vcb_client) and proxy001 (the vcbproxy_instance) tied together?
How can I prevent NetWorker from changing the defined Relationship?
Thanks for shedding some light on this ... Steffen
I dont know the answer but as a workarround i have copied the Application Information to all instances of my vcb-Proxy.
It does not interfere with save or savepsm commands.
sure, was my 1st guess as well, but unfortunately not the solution <for me>
because the proxy contains the NMC also, it always (?) picks the NMC backup client
and finally failes, because savepsm will not do the VCB trick
on the other hand, NMC backup still works, because savepsm will not interfere with Appl.Info as you have already mentioned