docu9297 rainfinity file management appliance release notes

5/21/2018 Docu9297 Rainfinity File Management Appliance Release Notes

1

These release notes contain supplemental information about this release of theEMC Rainfinity File Management Appliance. Topics include:

Revision history ......................................................................................................... 2 Product description................................................................................................... 2 New features and changes ....................................................................................... 3 Fixed problems .......................................................................................................... 4 Environment and system requirements ................................................................. 5 Known problems and limitations ........................................................................... 5 Technical notes......................................................................................................... 10 Documentation ........................................................................................................ 10 Software media, organization, and files................................................................ 11 Installation................................................................................................................. 11 Troubleshooting and getting help......................................................................... 12

EMCRainfinity

File Management Appliance

Version 7.3

Release NotesP/N 300-005-095

Rev A12

December 3, 2009


2 EMC Rainfinity File Management Appliance Version 7.3 Release Notes

Revision history

Revision history

Table 1 on page 2presents the revision history of this document.

Product description

EMCRainfinityFile Management Appliance (FMA) provides automatedstorage tiering capabilities for the NAS environment. FMA automates the task ofmoving infrequently accessed files across storage tiers to drive storage cost savingsand streamline backups.

Rainfinity File Management Appliance/VE (FMA/VE) is a software edition ofFile Management Appliance available separately as a VMware virtual appliance.FMA/VE runs in a VMware virtual machine and provides all the functionality ofRainfinity File Management Appliance with the following differences:

FMA/VE is a VMware virtual appliance and installs on a VMware ESX/ESXiserver.

FMA/VE supports only Celerra to Celerra and Celerra to EMC Centerastorage tiering.

FMA/VE supports 75 million files for archiving.

FMA/VE release notes are available on the EMC Powerlinkwebsite:http://Powerlink.EMC.com. Navigate from Support > Technical Documentationand Advisories > Software P-R Documentation > Rainfinity File ManagementAppliance/VE.

Table 1 Revision history of FMA release notes

Revision Date Description

A12 December 3, 2009 Updated New features and limitations for 7.3

A11 August 31, 2009 ONTAP 7.3.1 limitation removed

A10 July 13, 2009 G7 hardware support added

A09 May 8, 2009 NetApp API limitation added

A08 May 8, 2009 Network connectivity improvements

A07 October 3, 2008 Changed CWORM to File Level Retention

A06 October 3, 2008 Updated New features and limitations for 7.2.3

A05 April 24, 2008 Added 7.2.2 limitations

A04 February 8, 2008 Updated and added limitations

A03 November 19, 2007 Added 7.2 upgrade limitation

A02 August 23, 2007 Added delayed stubbing and CFA conversion service.Major revamp of documentation

A01 July 18, 2007 First release of the product
http://powerlink.emc.com/http://powerlink.emc.com/


3

New features and changes

EMC Rainfinity File Management Appliance Version 7.3 Release Notes

New features and changes

FMA 7.3 includes all the features and maintenance fixes from the previous releasesplus the following new features:

Multi-tier archiving

Stub protection on CelerraDART 5.6

Delay stubbing for NAS repositories

Support for Windows 2008 Domain Controller

Support for Windows 2003 and Windows 2008 servers as archive destinations

Support for the Atmos server as an archive destination.

Delete policy

NAS repository configuration

Usability enhancements

Supports up to 250 million files for archiving.

Multi-tier archiving

The multi-tier policy archives files to one tier based on one rule, and then relocatesthe files to another tier based on another rule. Stubs referencing relocated files areupdated to reference the new destination. Archiving may be scheduled to beginimmediately, on a periodic schedule, or when a capacity threshold is reached.

Multiple rules in a single policy can each support a different destination ormultiple tiers. Redundant scanning is eliminated, thus making archiving moreefficient.

Stub protection on Celerra DART 5.6

With stub protection on Celerra DART 5.6, unneccessary orphan files are no longercreated. If a stub is under retention, its retention time will be synchronized withthe retention time of the archived file. This will prevent the deletion of the stubfrom primary storage before the retention period for the file on secondary storageexpires.

Delay stubbing for NAS repositories

Previously, the delay stubbing policy attribute applied to EMC Centeradestinations only. The delay stubbing attribute has been expanded to include NAS

repositories which are Celerra Data Movers, NetApp Filers, and Windows servers.

Support for Windows 2008 domain controller

FMA operates in a Windows 2008 domain with a domain controller that isconfigured for NTLM authentication.



Fixed problems

Support for Windows 2003 and Windows 2008 servers as archive destinations

Windows has been added as a new file server type. Windows servers areconfigured as NAS destinations and support the CIFS protocol.

Support for the Atmos server as an archive destination

Atmos is supported as an archive destination from a Celerra source. Atmos is acloud-optimized storage (COS) product from EMC.

Delete policies

Delete policies simplify FMA administration and manage the growth of secondarystorage. The types of delete policies are:

The delete orphan policy automates orphan management.

The policy to elete stubs and associated archived files when retention expiresautomates capacity management of an archive destination with retentionconstraints in effect.

NAS repository migration

FMA provides a feature to move an entire NAS repository from one destination toanother, while updating stub files on the source to reflect the new destination.

Usability enhancements

Usability enhancements apply to the FMA GUI and include:

Authentication verification.

NAS repository configuration.

NAS repository migration.

Simulation.

Automated backup and recovery of FMA database and configuration files.

Removal of VDM IP filtering.

New file attribute for directory name on Add File Matching Criteria to Rulepage. dirnameallows users to exclude directories for evaluation per ruleinstead of globally per file server.

These enhancements are documented in the online help.

With the removal of VDM IP filtering, the upgrade process is also affected.Additional steps using FMA 7.2.5 are required before upgrading to FMA 7.3. Thegetting started guide provides details on performing software upgrades.

Fixed problems

A single stubRecoveryCLI command issued with the restorealloption can restoreup to 10,000 files at a time. Previously the limit was 1000 files.


5

Environment and system requirements


Environment and system requirements

The Interoperability Matrix lists the supported environment and configurationdetails for NAS and CAS API interoperability. The latest Interoperability Matrix isavailable on the EMC Powerlink website.

Known problems and limitations

This section describes known limitations and workarounds associated with theFMA:

When archiving a CIFS file that was created using NFS hardlink, the stub filecould be archived as a second version of the file. To restore the original versionof the stub file, use the Recover Stubfeature available on the Archived FileListpage of the FMA GUI. To avoid this situation, do not run CIFS archivingtasks on sources that contain NFS hardlink files.

When archiving to a NAS group with a repository that is not available, FMA

will archive to the next repository in the group if attempts to archive to theunavailable repository timeout after 20 minutes or more.

Archiving and stub scanning tasks will be slow while the database VACUUMis in progress. The database VACUUM is required to rebuild the indexes andensure that the overall FMA task performance is good. The VACUUM intervaldepends on the frequency of the database updates.

The maximum number of archive tasks to be run concurrently is set to 3 bydefault. FMA imposes this limit to maintain CPU consumption at a reasonablelevel for multi-tier and NAS migration tasks. However, the number ofconcurrent tasks may be manually set to a value between 1 and 5 with thecommand setTaskQueueLimitsas documented in the CLI man pages.

If the source or target server becomes unavailable while performing a

migration, the process will attempt to reconnect to the unavailable server andthe task will continue to run. The task must be manually stopped.

If stub files are restored from backup after running a multi-tier archive or NASmigration task, the stub from the backup will point to the old destinationwhich is no longer valid. If the FMA stub scanner encounters these stub files, itwill update the database to point to the old destination and the database entrywill be invalidated. To avoid this problem, before restoring stub files from

backup, take care to ensure that no multi-tier archive or NAS migration taskhas been run since the backup was created.

For Celerra Data Movers running DART 5.5.27.5 or later, the backup flagshould be set to pass through and not offline. If the flag is set to offline, theCelerra will return a 0 file size for stub files and multi-tier policies will not

execute correctly.

A delete policy with a file name or directory match rule but without a specificsource will only detect files archived with the CIFS protocol.

For stub files, NetApp reports the file size on disk to be the the logical size andnot the actual size. Therefore, if an archive condition is based on the capacityused, FMA cannot accurately ascertain the actual disk usage and will startarchiving before the capacity limit is reached. When archiving with NetApp asa source, capacity-based archiving is not supported.




If a task listed on the Schedule Summary appears to have completed, but theView Summary shows that it is still running, the task is not running and didnot complete successfully. This can occur if the File Management daemon isrestarted while a task is active.

FMA does not support SMB signing. For FMA to authenticate properly with aCIFS file server, SMB signing must be disabled within the Active directory

domain. If SMB signing is required and enabled for client-servercommunications, FMA will not be able to browse CIFS shares on the file serverserver or execute any CIFS archiving tasks.

When archiving to a server that is offline, a generic error message appearsindicating that the capacity of the server has been exceeded. If this occurs,check the status of the server.

When a Windows server is an archive destination, the share quota is notsupported. FMA will continue archiving to a Windows destination until theserver capacity is reached.

When using a NetApp filer as an archiving source, filenames containing thetilde symbol (~) will not archive.

If several tasks are scheduled to run concurrently, a few may fail due to theslow response of the Celerra. The failed tasks may be manually restarted orwill succeed in the next scheduled run.

If using Entrust encryption software to encrypt files before archiving, archivedfiles must be recalled before opening. Entrust will not allow archived files to beopened due to the checksum difference between the stub on the source and theoriginal file.

When archiving multiple files larger than or equal to 1 GB in size to a NASrepository, error messages may appear indicating that the disk space on thedestination is full even if disk space is available. To work around this problem,run the archive job again. Files that were not archived during the first run will

be archived during the second run.

The Celerra Callback Service name is inconsistent with the Atmos CallbackService name that has been added for the FMA version 7.3 release. The CelerraCallback Service recalls from an EMC Centera to a Celerra. The AtmosCallback Service recalls from an Atmos to a Celerra. In the case of the CelerraCallback Service, the name of the service refers to the name of the source. In thecase of the Atmos Callback Service, the name of the service refers to the nameof the destination.

When archiving from a Celerra, the file system access policy must be nativewhich is the default setting. To check the file system access policy, type:

server_mount -| grep

If the file system access policy is not native, change it to native with the

command:

server_mount -option accesspolicy=NATIVE

The Celerra backup policy should be set to passthrough. This will ensure thatRainfinity will receive the original file attribute of the stub:

fs_dhsm -modify -backup pass-through


7



After upgrading from FMA 7.2.1 to FMA 7.2.5 or later, existing scan stubs tasksmust be redefined manually. This is due to a change in the scan stubsimplementation. Both the server and path are required for the stub scanner inFMA 7.2.5.

For Rainfinity FMA LDAP to work with Active Directory, the minimumsupported configuration is:

Windows 2000 or Windows 2003 R2 domain controller.

The Services For Unix 3.5free module installed and downloaded fromMicrosoft on the domain controller.

If the maximum number of concurrent NFS TCP connections is reached whenrunning multiple archiving tasks on the same NetApp server, a task may failwith the error message Client credential too weak. To work around thisproblem, restart the archiving task. Subsequent archiving tasks will succeed ifthe server has enough available connections to respond to FMA. Note that thislimitation is for NFS TCP connections only. If FMA is archiving using NFS,concurrent CIFS archiving tasks are not affected.

For FMA to archive from a CIFS server configured on a Celerra Data Mover,

the CIFS server must be joined to an Active Directory domain.

Up to 10,000 orphan files can be deleted at one time using the CLI command(rffm). To delete up to 1 million orphan files, use the Delete Orphan policy.

The API that automatically creates the DHSM secondary connection on theCelerra Control Station may fail intermittently. This is due to a limitation onthe Control Station. The Control Station cannot process multiple requests tocreate the connections when multiple archive tasks are scheduled to start at thesame time. As a result, archive tasks that are initially unable to create aconnection call will exit with failure, but will most likely succeed forsubsequent runs.

Stub files on a NetApp are sparse files. To back up stub file content only, use

NDMP. Then mount the export and use the ducommand to validate the stubfile size.

After upgrading FMA from a version older than version 7.2.2, a script may berequired to update the stub scanner schedule. To obtain the script, contact anEMC Customer Support Representative.

The number of connections open to an EMC Centera during archiving mayexceed the EMC Centera connection limit. For instructions on how to reducethe default number of connections to an EMC Centera, contact an EMCCustomer Support Representative.

The Celerra callback service does not support HTTP/1.1 pipelining. If HTTPstatus 400 errors are written to the Celerra log, turn off this option on theCelerra Data Mover by typing the following command on the Celerra Control

Station for each Data Mover:

$ server_param server_x -facility http -modify maxOutPipeline-value 0

If the command fails due to the Celerra 5.6 version, type:

$ .server_config server_x -v "param http maxOutPipeline=0"




If an upgrade fails with No Packages marked for Update/Obsoletion error, theyum cache may be corrupted. To work around this problem, remove thersupgrades directory by typing:

# rm -rf /var/cache/yum/rsupgrades

and retry the upgrade.

A Celerra Data Mover that is configured to use basic authentication for itsDHSM interface is not supported. Reconfigure the Celerra to use digestauthentication by typing:

server_http -modify dhsm -authentication digest

For scheduled tasks based on the Capacity used Archive Condition, there maybe a slight delay between the time that the threshold is reached and the timethat the task is started. This is due to the fact that quota information is polledevery 5 minutes.

When a Celerra Data Mover initiates a request to FMA to recall offline data onan EMC Centera, each Celerra file system can initiate up to 32 simultaneousconnections to send the request. FMA creates a new thread for each connection

received from Celerra and responds to each request with the requested piece ofdata read from an EMC Centera. The Celerra callback daemon (CCD) on FMAsupports up to 1000 threads for recall requests from Celerra.

The total number of available recall threads on FMA can be saturated if thereare more than 31 source file systems and each file system is using all 32connections for recalls simultaneously. For small files, the Data Mover may usefewer than 32 connections to send recall requests to FMA. If the maximumnumber of recall threads on FMA is reached, new connections from a Celerraare reset by FMA and an error is logged by both the Celerra and FMA in theirrespective logs. The Data Mover retries the reset connection and it is processed

by FMA if there are recall threads available. As outstanding recall requests arehandled by the CCD, threads are freed up to process new connections fromCelerra.

When an administrator impersonating a user is attempting to recall files froman EMC Centera to a NetApp, the operation may fail. This is because the homedirectory path for a user on a NetApp may be different from the directory pathfor the administrator. To work around this problem, administrators shouldspecify the full pathname when recalling files to a NetApp filer.

Do not use paths of the form:

\\filername\~

Instead use paths of the form:

\\filername\CIFS.HOMEDIR\\dir1\file1.doc

When archiving files from a NetApp filer with thousands of files in a widedirectory on the source, an archiving task may experience timeouts and maynot complete properly.

For NetApp version 7.2.3, documents that are opened with MS Word andmatch policy criteria may be archived while the document is being edited.When the document is saved, the archived version gets recalled before theactual save and the user may experience a delay.


9



Rainfinity cannot archive to a NAS destination with the word archive in itsname.

When upgrading, the stub_management.archived_files table is reindexed,which may result in a longer upgrade time. For example, a table containing 50million entries may require a few hours to reindex.

After upgrading from 7.1.x to 7.2 and later, run the Rainfinity setup script(rfhsetup) to immediately configure network settings.

When attempting to archive a file with local user permission to a NASrepository, the task fails because the user does not exist on the destination.

If a file on a NetApp that was originally modified during daylight savings timeis archived to a NAS repository and then recalled back to the primary NetApp,the modified time is shifted by 1 hour. Since FM relies on the modified time toidentify files, if the file is archived again, it will be archived as a new version.

The GUI may hang if multiple sessions are opened to create or edit policies. Ifthis occurs, close some GUI windows and wait a few minutes beforecontinuing.

The File Management application does not run on the FM High Availabilityappliance. An attempt to start this application/daemon results in a failure anda reference to an empty database directory.

When nearing the threshold of a NAS destination, a race condition can occurthat causes multiple parallel threads to assess that the threshold has beenreached. This results in an underutilized repository.

Because VDMs on the Celerra only support CIFS, when configuring Celerraproperties, CIFS-specific settings are required for the File Managementapplication to execute tasks.

For Celerras running older software versions, if the NTLMv2 authenticationattempt fails with the RPC NT UNSUPPORTED AUTHN LEVEL error fromthe CIFS server, Rainfinity uses NTLMv1 authentication.

Windows and UNIX files must appear the same. Thus, when archiving withUnicode filenames, Rainfinity may fail if the character encoding is not set toUTF-8. The file server documentation provides instructions on how to changethe character encoding.

File Management provides Unicode file path support for the UTF-8 characterset only. Therefore, Unicode must be enabled on any type of file server thatFMA supports.

File Management does not support moving stub files to a NetApp destinationthat is managed by another FMA. Doing that risks identifying files as orphanson the destination when they are not, and can lead to data loss.

When viewing archived files, the same share or export used during archiving

must be selected. To further limit the results displayed, subdirectories orpartial filenames with wildcards (* or ?) can be specified after the share orexport name.

If a virus scanning or backup program runs on your NetApp filer, type the IPaddress of the machines that host these applications as Excluded Clients on theNetApp FPolicy Special Clientsconfiguration GUI page.



Technical notes

Clients will experience latency when accessing stub files because they mustwait until each file is read from secondary storage. Several variables willimpact the latency:

File size Larger files require more time to write back.

Concurrent client access EMC Centera supports a limited number of

concurrent file recalls (about 20 per file access node). Network bandwidth.

Network traffic.

NetApp throughput.

Files under 8 KB on Celerra or 4 KB on NetApp are not archived unless theminimum file size override option is set. The amount of disk space that a fileoccupies on a Celerra is 8 KB, and varies between 4 KB and16 KB on a NetApp,depending on the original file size.

To obtain a detailed report for any task listed on the Scheduletab, click ViewDetailsfor that task. A task that is terminated prematurely may list incorrectvalues. To obtain accurate results, click View Logon the Detailed Report page.

When trying to use Windows Explorer to copy and paste a file over a NetAppstub file of the same name, an access denied error message appears. To workaround this Windows Explorer limitation, recall the original file, and insteadcopy and paste over the original file.

When the callback daemons (CCD/FCD) are supporting multiple FileManagement Appliances, it may become overloaded with callback requests.Recalls may fail on the first attempt generating a false email/SNMP alert;however, the recall will succeed on the second attempt.

If a NAS repository is 100 percent full or has reached its threshold, or all NASrepositories in a single logical group are 100 percent full or have reached theirthresholds, the archiving task will not archive files to the next availabledestination and exits the task.

Technical notes

There are no technical notes for this release.

Documentation

Table 2 on page 10shows the documentation for Rainfinity File Managementversion 7.3.

Table 2 EMC Rainfinity File Management 7.3 documentation (page 1 of 2)

Part number Name

053-001-951_A06 EMC Rainfinity FMA Documentation CD

300-005-093_A09 Rainfinity FMA Getting Started Guide


11

Software media, organization, and files


All documentation is available on the EMC Powerlink website:http://Powerlink.EMC.com. Navigate from Support > Technical Documentationand Advisories > Software P-R Documentation > Rainfinity File ManagementAppliance.

Software media, organization, and files

The FMA is shipped with preinstalled software. To upgrade an installation, or if asoftware image is damaged in transit, Rainfinity media is available from the EMC

Powerlink website under Support > Software Downloads and Licensing >Downloads D-R > Rainfinity.

Table 3 on page 11includes the physical contents of the Rainfinity FileManagement Media Kit.

InstallationThe Rainfinity File Management software may be reinstalled with a CD cleaninstall, or upgraded with a CD full upgrade or a UPG upgrade. The EMC RainfinityFMA Getting Started Guide Version 7.3 provides installation and upgradeinstructions.

The following upgrade paths are supported for FMA 7.3:

1. Upgrade from 7.2.3 to 7.3

2. Upgrade from 7.2.5, 7.2.5SP1, and 7.2.5SP2 to 7.3

3. Upgrade from 7.2.4 to 7.2.5 SP2 to 7.3

FMA 7.3 does not support File Management High Availability (FMHA) on a

Global File Virtualization (GFV) appliance. To redeploy a GFV appliance as anFMHA device, reimage the GFV appliance by reinstalling FMHA with thefmaha_cleaninstallation command.

300-005-095_A12 Rainfinity FMA Release Notes

300-009-004_A03 Rainfinity FMA Online Help

453-001-852_A13 EMC Rainfinity FMA Electronic Doc Distribution

Table 2 EMC Rainfinity File Management 7.3 documentation (page 2 of 2)

Part number Name

Table 3 EMC Rainfinity 7.3 media

Part number Name Description

053-001-950_A07 EMC Rainfinity FMA Recovery CD CD ISO image of File Managementapplications.



Troubleshooting and getting help

Troubleshooting and getting help

EMC support, product, and licensing information can be obtained as follows.

Product information For documentation, release notes, software updates, or forinformation about EMC products, licensing, and service, go to the EMC Powerlink

website (registration required) at:

http://Powerlink.EMC.com

Technical support For technical support, go to EMC Customer Service onPowerlink. To open a service request through Powerlink, you must have a validsupport agreement. Contact your EMC Sales Representative for details aboutobtaining a valid support agreement or to answer any questions about youraccount.

Copyright 2007 - 2009 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS

PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FORA PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisoriessection on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

docu9297 rainfinity file management appliance release notes

Documents

fmave release notes

vmware virtual appliance

release notespn

file level retentiona06

vmware virtual machine

technical notes

vmware esxesxiserver

emc powerlinkwebsite