Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1728

October 2nd, 2008 12:00

Rainfinity FMA

I am setting up rainfinity FMA to archive files from a celerra to a centera. I am getting errors trying to archive. I have a test filesystem with 1 file and I am trying to archive to verify the setup. I have attached the log from the FMA, anyone have any ideas?

Oct 01 22:11:52 START SUPPORT: Wed Oct 1 22:11:52 2008

Oct 01 22:11:52 Commands: -Fs Celerra -Ft 10 -Fw nfs -Nh ohcolnas0220 -Na 10.220.163.1 -Ne /archive_test -Nd / -Mu rainadmin -Mp
vG+rvPJq1A28b6u88mrUDbD1l1AqwVpS7hVjrbUmD1Az3SyVqT9LT7xvq7zyatQNvG+rvPJq
1A0=
-Ph 127.0.0.1 -Pt 29108 -Pi 60 -Fi 7 -Fp Archiver -Rn s-core-fma.nwie.net
Oct 01 22:11:52 Archiver::initialize(): Creating DB connection pool with 10 connections
Oct 01 22:11:52 Log control client received message
Oct 01 22:11:52 Log control processing message: command=0
Oct 01 22:11:52 Sent log control response
Oct 01 22:11:52 Received policy "Test_Policy":
define action "my_action" = archive to "ohcolcentnas" delay_stub 0 days retain 0 years
for size > 1 bytes do archive to "ohcolcentnas"

Oct 01 22:11:52 Archiver::setdelayedstubbingtimesecs() - zero value of "0" for "delay_stub" in Policy delayed stubbing will not be enforced
Oct 01 22:11:52 Archiver::setThreadPoolSize() - setting archiver thread pool size to 80
Oct 01 22:11:52 SL_CenteraFileServer::SL_CenteraFileServer() successfully connected to Centera: "ohcolcentnas"
Oct 01 22:11:52 ARContext::ARContext() starting 80 archiver threads
Oct 01 22:11:52 Archiver queue size = 1
Oct 01 22:11:52 Error no buffer available or it's size is less than 78199.
Oct 01 22:11:52 writeBlob: Unable to write blob, FP_STREAM_ERR - An error in the generic stream occurred sysError: 8.
Oct 01 22:11:52 Unable to create file blob in C-Clip, Unknown.
Oct 01 22:11:52 SL_CenteraFileServer::private_secondary_archiveNfsFile() - error, failed to write file data to Centera
Oct 01 22:11:52 SL_CelerraFileServer::private_primary_archiveOrRestubNfsFile() failed to write file /archive_test//export.post to Secondary File Server
Oct 01 22:11:52 ARThread::processNfsQueueEntry: Failed to archive NFS file "/export.post"

Oct 01 22:11:55 All walker threads completed, rfwalker progress report follows:
Oct 01 22:11:55 tag_id = "29108"
Oct 01 22:11:55 total_dirs_processed = "1"
Oct 01 22:11:55 total_files_processed = "1"
Oct 01 22:11:55 last_dir_processed = "/"
Oct 01 22:11:55 last_file_processed = "/export.post"
Oct 01 22:11:55 total_files_archived = "0"
Oct 01 22:11:55 total_bytes_archived = "0"
Oct 01 22:11:55 total_fileops_failed = "1"
Oct 01 22:11:55 disk_capacity = "10573561856"
Oct 01 22:11:55 disk_usage_start = "712704"
Oct 01 22:11:55 disk_usage_end = "712704"
Oct 01 22:11:55 total_files_stubbed = "0"
Oct 01 22:11:55 total_files_delay_stubbed = "0"
Oct 01 22:11:55 total_bytes_delay_stubbed = "0"

22 Posts

October 2nd, 2008 19:00

You might also try that b117 upgrade patch from support, or upgrade to the current 7.2.3 posted on Powerlink. It was also recommended when we were troubleshooting our issues writing from Celerra to Centera.

22 Posts

October 2nd, 2008 12:00

What version of FMA? There are some new interesting configuration issues with 7.2.3 with regards to File Server settings.

When I had this problem it was because I didn't have ALL IP addresses for ALL CIFS servers defined on my Celerra in the File Server configuration on the FMA. It was explained that even though the test CIFS file system has a separate IP defined, the Celerra could respond to the request on any of the CIFS server IPs. Therefore, in the FMA config IP addresses for each CIFS server needed to be defined even if they don't seem to apply.

I see you're using NFS, but the same requirements should apply.

Hope this helps.
--Jeff

90 Posts

October 2nd, 2008 12:00

File Management 7.2 b115

I do only have the primary interfaces defined with the server_http command. I have a replication interface and a AV interface as well, that I will add these tonight to see if that resolves the issue. I remember reading this now, and it is supposed to be fixed in 5.6 to use only the primary interface. I will try to add the IP's tonight and post my results.

22 Posts

October 2nd, 2008 12:00

Good luck. I'm on DART 5.6 also, but still needed to add the IPs. I agree it seems that it should stay with the primary interface.

There was also a 7.2 b117 patch that was needed to resolve problems with archiving some types of files. Support could not provide me with the specifics, but applying the patch did fix some archiving errors. Hard to tell if that's what you're experiencing with testing a single file.

90 Posts

October 2nd, 2008 12:00

Thanks for the info, I just re-read the doc and it states 5.5 has the multiple IP issue, but not that 5.6 fixed it. I must have assumed that part.

90 Posts

October 2nd, 2008 18:00

I added the additional IP's and still get the same error. I have engaged the FMA resource from EMC asigned to us for this project. Hopefully I will get something from him soon. I will post the fix once we figure it out.

90 Posts

October 9th, 2008 12:00

The FMA update corrected the issue.
No Events found!

Top