We have Celerra,Rainifnity & Cenetra .
I have created policy for one of the fileshare archive scheduling for every 2 weeks on Sunday.Unfortunatly that has not happend this Sunday and i have ran manulatty today and getting File Ops failed.I checked everything on rainfinty like....Policies,Schedules etc.
Can any one help to resolve this.Thanks in advance.
Well firstly you shall check your FIle System connections status and relevant pool connections for centera on your CTA.
If your all files resulted in File Ops Failed (no files were archived) than it means CTA was not able to find any location to which it has to write. This could happen if you lost your network connectivity...
If you have installed CAVA in your environment than it can cause some similar issues too...
I hope this may help in initial troubleshooting
File Ops failed -- refers to Failed Operations Failed, and it could due to connectivity or permissions issues. Moreover the issue could be for a certain set of files. Do we've any logs for the issue.
Yes we have logs.
tag_id = "6270"
May 07 16:49:03 total_dirs_processed = "295019"
May 07 16:49:03 last_dir_processed = "\Custodian_Collections\Sepp_Tiffany\My_Documents_20120320\DEVO\To Be Filed\USB Key 19Nov2010\ABH\Address Book - 2010-07-31.abbu\Images"
May 07 16:49:03 last_file_processed = "\Custodian_Collections\Sepp_Tiffany\My_Documents_20120320\DEVO\To Be Filed\USB Key 19Nov2010\ABH\Address Book - 2010-07-31.abbu\Images\FF9EA30C-9CE8-4F96-B065-CDBAE8FAA954"
May 07 16:49:03 total_files_processed = "6289659"
May 07 16:49:03 total_files_archived = "54393"
May 07 16:49:03 total_bytes_archived = "68,169,884,130 (63.49 Gbytes)"
May 07 16:49:03 total_fileops_failed = "4046"
May 07 16:49:03 disk_capacity = "634,414,678,016 (590.84 Gbytes)"
May 07 16:49:03 disk_usage_start = "579,868,786,688 (540.04 Gbytes)"
May 07 16:49:03 disk_usage_end = "529,582,243,840 (493.21 Gbytes)"
May 07 16:49:03 total_files_stubbed = "54394"
May 07 16:49:03 total_bytes_stubbed = "68,169,969,122 (63.49 Gbytes)"
May 07 16:49:03 total_files_delay_stubbed = "0"
May 07 16:49:03 total_bytes_delay_stubbed = "0 (0.00 Kbytes)"
From your log, you are getting a failure to wrote to the Centera, which implies the Centera profile used by CTA (Rainfinity) has had its access priviliges modified, or the Centera cluster access has been modified.
From your desktop, use jCenteraVerify, confirm the CTA (Rainfinity) PEA is still valid.
If it passes, regenerate the PEA and upload to the CTA.
If the PEA check out, then log onto the Celerra control station, check the fs_dhsm settings, spcifically the connections. The CTA confioguration docs has all the info you need to check these settings.