Solved!
Go to SolutionFMA-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
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.
Hello,
This is the output of : $fs_dhsm -connection fs_vip1_tier1 -info
[nasadmin@mtnas_sb_cs ~]$ fs_dhsm -connection fs_vip1_tier1 -infofs_vip1_tier1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBcid = 0type = CIFSsecondary = \\mtnas.domtest.ma\share_tier2_test\state = enabledread policy override = nonewrite policy = fulllocal_server = MTNAS.DOMTEST.MAadmin = domtest.ma\nasadminwins =error =Cannot establish connection between secondary server mtnas.domtest.ma and local server MTNAS.DOMTEST.MA with share share_tier2_test with user domtest.ma\nasadmin NT status=INTERNAL_ERROR c00000e5H.Mount remote file system failed with status: InternalError.connection 0 re-connect failed 51 time(s)Any idea?
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.maThank yooooooooouuuuuu Scott. We got it
That's what we found when executing $ server_log server_2
2011-02-11 22:37:58: SMB: 6:[VDM2_replica1] sendLookupSIDs pipe lsarpc reopened2011-02-11 22:37:58: SMB: 3:[VDM2_replica1] LsarOpenPolicy2::Request failed, status=ACCESS_DENIED2011-02-11 22:37:58: SMB: 3:[VDM2_replica1] lookupSIDs:no reply2011-02-11 22:37:58: SMB: 3:[VDM2_replica1] sendFirstDCQuery: NoAdminName domain=DOMTEST status=DOMAIN_CONTROLLER_NOT_FOUND2011-02-11 22:37:58: SMB: 3:[VDM2_replica1] DisconnectDC_onClose DC=SERV1 ntStatus=ACCESS_DENIED2011-02-11 22:37:58: SMB: 3:[VDM2_replica1] cMsRPC_Request::Close bad reply ntStatus=DOMAIN_CONTROLLER_NOT_FOUND2011-02-11 22:37:58: SMB: 6:[VDM2_replica1] DC0xe0c0ba04: setDCDown DC, refresh if needed (origin=ntStatus_DisconnectDC_onClose)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.
halls1
25 Posts
1545
0
Posted 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.