Using File System Archiving (FSA) PassThru recall with NetApp SnapMirror volumes results in Access Denied

Problem

Trying to recall Placeholders from the SnapMirror destination volume while the mirror is active will result in error.

Cause

When a SnapMirrored primary volume is configured for archiving and Placeholders are created, the destination SnapMirror Volume is in Read-Only mode while the SnapMirror link is active.

If PassThru is configured for the SnapMirror destination volume it will not work because, on NetApp Filers, PassThru can only be used with ~snapshot volumes.


Workaround:

In order to be able to recall Placeholders from the destination volume, follow these steps:

• Break the SnapMirror link to the destination volume
• Add the destination filer in to the Vault Administration Console (VAC) as an FSA Target (if the destination is on a diffferent filer to the SnapMirror source)
• Add the SnapMirror volume (CIFS share) as a valid FSA Archiving Target Volume

The destination filer must be added to the list of targets in the VAC because the ev-placeholder fpolicy needs to be created on the destination filer and the EV server registered as a screening server to process the recall requests.

Solution

Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.
 
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see http://www.veritas.com
 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.​