Highlighted
2 Bronze

Problem with FMA archiving

Hi,

I want to archive data from Celerra to Celerra. To configure FMA, I've used "FMA Getting Started Guide" version 7.3

I've done all tasks that figured in this document but when I opened my share to see archived file, I don't find ay archived file (with a right click on one of my files

I find that the size of my file still the same: size = size on disk)

could you please help me thx

0 Kudos
6 Replies
Highlighted
2 Bronze

Re: Problem with FMA archiving

FMA if it's set up correctly has to do two things to actually archive data.  First, you must run a policy that determines what files should be tagged as archivable and then there's a process that creates a stub of that file which is actually the point when the file is archived on the Centera.  In almost all cases, the tagging of a file and the stubbing of the files are independant processes and happen at different times.  You can check your FMA scheduler (on the main GUI) for when this occurs or if it's scheduled to occur.  Via NFS it's hard to determine that a file is stubbed and archived, but in Windows it's very easy.  In windows, the file will appear with a small circle with a line thru it but the file's size, permissions, name, etc will all be the same.  You want the file to be represented with the same size at the file system level even though the stub is very small.

If after this you're still not sure, open a chat session and EMC support can help get you going in the right direction.

Tom Whalen

Highlighted
2 Bronze

Re: Problem with FMA archiving

thx it works now

0 Kudos
Highlighted
2 Bronze

Re: Problem with FMA archiving

Great to hear that!

Tom Whalen

0 Kudos
Highlighted
3 Argentum

Re: Problem with FMA archiving

Hi Tom,

I'm happy to see you on this Open Exchange forum. Thanks for jumping in to help ou!

Kris

0 Kudos
Highlighted
2 Bronze

Re: Problem with FMA archiving

Hi Tom,

I was trying to run import task from Celerra CIFS to Celerra CIFS, but I always got the same error " Failed to create the NAS CIFS DHSM connection with  error XmlApi::recvXmlResponse Error". I did all steps in the " FMAVE Trial Installation Instructions 0110.pdf".

server_http <data_mover> -append dhsm -users <user> -hosts <ip_address>

server_http <data_mover> –service dhsm –start

fs_dhsm -modify <primary_fs> -state enabled

all steps succeeded.

The following lines include the Archiving log (error is in red color):

May 05 13:46:36 Trying to create a CIFS to CIFS dhsm connection between primary server "EMCCIFSONE" share="FMASOURCE" and secondary server "EMCCIFSONE" share="FmaStore"

May 05 13:46:36 Trying to connect the Celerra XML API server '10.20.2.13' with user 'rffm'.

May 05 13:46:37 Trying to query the file system's ID of \\10.20.2.17\FMASOURCE.

May 05 13:46:37 Trying to enable DHSM on the file system 23

May 05 13:46:39 Trying to create a CIFS DHSM connection to \\emccifsone.dotnet.criticalsites.local\FmaStore for file system 23. NetBIOS domain 'DOTNET', CIFS user 'administrator'.

May 05 13:46:55 (WARNING) Failed to create the NAS CIFS DHSM connection with unknown error -13. You may need to manually create the DHSM connection.

May 05 13:46:55 (WARNING) Failed to create the NAS CIFS DHSM connection with  error XmlApi::recvXmlResponse Error

...

Cannot establish connection between secondary server emccifsone.dotnet.criticalsites.local and local server EMCCIFSONE.DOTNET.CRITICALSITES.LOCAL with share FmaStore with user DOTNET\administrator  NT status=INTERNAL_ERROR c00000e5H.

<Description>This is a failure of the actual attempt to map the share over the network. status c00000e5H is a Microsoft SMB error code that among other places can be looked up here ... http://source.winehq.org/source/include/ntstatus.h
 1. BAD_NETWORK_NAME may mean that the share is not valid for the server.
 2. BAD_NETWORK_PATH may mean that the host name is wrong.
</Description>

<Action>1. Look at the NT status code which is a CIFS error and act on the message.

2. Verify that the server emccifsone.dotnet.criticalsites.local name is an FQDN and not just the machine name or IP address. IP addresses cannot be used in place of a server name.

3. Verify that the user account belongs to the domain and has the correct credentials.

4. Verify that the Celerra Data Mover EMCCIFSONE.DOTNET.CRITICALSITES.LOCAL is joined to its domain. The CIFS server status will display that information.

5. If the error message seems incorrect based on the displayed input parameters then look at the Celerra Data Mover server log for more detailed information. Pay special attention to the log messages associated with the facilities MGFS, DHSM, SMB, and KERBEROS.</Action>

Actually I got the same error when I try to connect manually from CLI:

$ fs_dhsm -connection FS01 -create -type cifs -admin 'DOTNET\administrator' -secondary '\\EMCCIFSONE\FmaStore' -local_server EMCCIFSONE

Enter Password:********

Error 13158252563: Cannot establish connection between secondary server EMCCIFSONE.DOTNET.CRITICALSITES.LOCAL and local server EMCCIFSONE.DOTNET.CRITICALSITES.LOCAL with share FmaStore with user DOTNET\administrator  NT status=INTERNAL_ERROR c00000e5H.

I don't know how does the FMA know this password to enter it?. But it seems that it executes the same command (without the password  !!!)

Please Advise.

Thanks

Hatem Mostafa

0 Kudos
Highlighted
Not applicable

Re: Problem with FMA archiving

Hatem,

The connection-creation failure can be the result of a few things. As seen in the messages, you have to make sure the data mover has joined the domain.  Also: there are a number of steps listed in the Getting Started Guide that are prerequisite to these automatic connections being created. Go through them carefully and make sure they've all been completed.

To get to the Getting Started Guide, open the FMA in a browser, click on "Help for this page", and find the "File Management Getting Started Guide" link in the upper left. Click on it to open the Guide.

The "Deploying the File Management Appliance" section has a chapter titled "Using the FMA with the Celerra Data Mover".  There are a number of prerequisites that have to be followed. If you haven't already, go through this chapter and follow the instructions. There are things that have to be done on the Celerra control station, and some on the FMA. The creation of the dhsm user, the update of the xlt.cfg file, the xml api server, etc... All have to be done correctly in order to give the FMA the ability to create connections.

You shouldn't ever have to create a connection manually, although you could try to create an NFS connection manually, to see if the problem is possibly related to AD. (If the NFS connection succeeds, and the CIFS fails, that may be the case.)

0 Kudos