I recently encountered a problem snapmirroring between a 2020 in domain x and a 3140c in domain y.
It was an interim configuration as part of a larger project. Snapmirror was being used as a way of swinging between the two filers in a production environment to minimise downtime. The fact that the filers were in different AD domainshad no part in the problem.
Preiliminary work such as configuring hosts files, dns and nfs exports had been completed.
Entries had been added to the etc/snapmirror.allow configurationg file
Destination volumes had been created and restricted.
On initialising the snapmirror the following error was encountered:-
“snapmirror may be misconfigured, the source volume may be busy or unavailable”
As well as editing the snapmirror.allow file I also needed to add a reference to the destionation filer as follows:-
options snapmirror.access host=systemA
systemA can be an ipaddress or Filer name.
However, I was still getting failures when initialising the snapmirror.
With a telnet session open to the source filer I attempted the snapmirror initialisation again.
Whilst I expected another failure it showed that the destination requesting the snapmirror initialisation was coming from a different IP address than expected.
After adding this IP address to the .access option the snapmirror initialsied succesfully.








Recent Comments