This post is more than 5 years old
22 Posts
0
4163
FMA-Celerra Disaster Recovery Configuration
Hello,
I have two sites (Site A and Site B) with one Celerra and one FMA each.
I configured the FMA with the Celerra on Site A. So that the FMA can archive from one file system fs1_tier1 to a second file system fs1_tier2 connected both to a CIFS_Server.
I replicated the VDM containing the CIFS_Server and his two file systems.
Now what I need is to access the archived files on Site B.
In fact, I can access the replicated CIFS_Server through \\CIFS_Server. I can access also the two file systems on it and the files which are not archived.
However I can not open the archived files.
Do you have any idea.
How can I recall files on the secondary site (Site B)?
Thanks in advance
halls1
25 Posts
0
February 11th, 2011 08:00
You will need to address this connection error first. Looks like the user cannot authenticate to the domain. Make sure all of the CIFS and domain connectivity is working on the secondary CIFS Server.
Run "server_cifs server_2", to look at CIFS and Domain status. (Assuming Data Mover is server_2.)
Run "server_http server_2 info dhsm" to look at Filemover DHSM service status.
Run "server_log server_2" to look at Data Mover log information, which may point out the issue.
condor4
22 Posts
0
February 10th, 2011 15:00
Yes I did. But it didn't work.
Should it be done before switch over of the replication or after.
Or it doesn't matter?
In fact, I understood that the FMA in site B is not responsable for recall. The recall is done from the API on the Celerra.
halls1
25 Posts
0
February 10th, 2011 15:00
Have you configured DHSM on the Site B Celerra?
halls1
25 Posts
1
February 10th, 2011 17:00
You don't need FMA at the secondary site for this configuration. That is correct. But the File System still has to be configured with DHSM to point to the secondary CIFS location. Run the "fs_dhsm -connection {File System Name} -info" and see if it's configured. If not, it's needs to be setup the same as the primary. The same server_http and fs_dhsm commands you ran on the primary Celerra, run on the Secondary.
condor4
22 Posts
0
February 11th, 2011 02:00
Hello,
This is the output of : $fs_dhsm -connection fs_vip1_tier1 -info
Any idea?
halls1
25 Posts
1
February 11th, 2011 07:00
Delete and re-create the connection string manually.
fs_dhsm -connection -create -type cifs –admin ‘ \ ’ -secondary ‘\\ \ ’ -local_server
Example with your information:
fs_dhsm -connection fs_vip_tier1 -create -type cifs –admin 'domtest.ma\nasadmin' -secondary '\\mtnas.domtest.ma\share_tier2_test\' -local_server mtnas.domtest.ma
condor4
22 Posts
0
February 11th, 2011 08:00
Thank yooooooooouuuuuu Scott. We got it
That's what we found when executing $ server_log server_2
When we verified the server_2 clock, we found that its clock is not synchronized with the Domain Conroller clock.
After we changed the clock all worked fine.
Thank you again Scott.
condor4
22 Posts
0
February 11th, 2011 08:00
I deleted the dhsm connection and recreated it but still the same Error :-(
halls1
25 Posts
0
February 11th, 2011 09:00
That's good news. You're welcome.
Cheers