Multi location exchange backup hangs with “Initiating communication between the current machine and DAG member machines”
Virtual client has exchange members at more than one location
In the run status section of job management we see “Initiating communication between the current machine and DAG member machines” and the backup hangs and requires an abort to terminate the job.
The machine.dat files are normally populated by themselves using broadcast. With multi locations the machine.dat file does not get updated with the client information from a different location.
1/ Take a copy and edit the …\NetVault Backup\etc\machines.dat file on the NetVault server. This will have a stanza for each the clients within the virtual client.
2/ First stop the service on each client Modify each machines.dat by adding the stanza for the clients belonging to the virtual client that are not there.
3/ once the machine.dat file on all clients has an entry for all clients belonging to the virtual client and the services are started the job should now run.
Note: The need to edit the machines.dat files is addressed in the exchange plugin user guide under “addressing cluster-related issues”
