SnapProtect - FAQ - NAS iDataAgent
- Can I backup data residing on a vFiler?
- Can I configure a subclient to include the root volume of a file server?
- Can I use a vFiler as a destination for SnapVault or SnapMirror copies?
- Can I use the file system for NAS restores?
- Can I enable the Image Backup Set option on a SnapVault copy?
- Do I have to restart SnapMirror to tape backups from the beginning?
- Can I use filters for SnapMirror to tape backups?
- Can I perform an In-Place restore of root volumes for SnapMirror to tape backups?
- Can I perform a Direct Access restore of an image backup?
- Can I configure a full backup operation to create a new index?
- Can I use an existing storage policy that is used for backing up data for Catalog snapshots?
- Can I use a storage policy associated with subclients from other agents for Cataloging snapshots?
- Can I switch between backup copy and Catalog Snapshots options?
- Which snap iDataAgents support catalog snapshots?
- Which version of NAS supports catalog snapshots?
- How can I manually select jobs for cataloging?
- Can I re-catalog the snap backup job?
- Will Data Aging prune the backups although they are in picked state?
- Can I have a vault copy as the source for cataloging data during an SnapProtect backup?
- Will Cluster-Mode work with an older version of MediaAgent?
- Can I back up infinite volumes using Cluster-Mode arrays?
- Is browsing subclient content supported for SnapProtect backups on Cluster-Mode?
- Can I back up physical cluster nodes?
- Are junction points supported for Cluster-Mode arrays?
- Is SnapMirror to tape supported for Cluster-Mode?
- Why don't I see "Skip Catalog Phase for Snap Backup" when creating a schedule policy?
- How can I revert a snapshot operation on an Infinite Volume?
- How do I mount CIFS or NFS for Infinite Volume?
- Why are the statistics inaccurate when I browse the index of an Infinite Volume snap backup?
- Does Infinite Volume backup support SnapVault or SnapMirror?
Yes. If the data you want to backup resides on a vFiler, set it up as follows:
- Add the vFiler as a NAS client as explained in the Getting Started - NAS Configuration procedure.
If you plan to add more vFilers as NAS clients, ensure they have unique names. vFilers with the same name are not supported.
- During the NAS client configuration, ensure not to include the vFiler root volume in the subclient content.
- When performing a backup, indexing is supported if the physical file server (where the vFiler resides) has been specified in Array Management. If not, ensure you select the Skip Catalog phase for SnapProtect option during backup as indexing will not be supported.
- To restore the data, create a backup copy as explained in the Snap Backup Copy procedure and restore the files and volumes from the backup copy.
- Other operations you can also perform with the snapshot are mount and revert operations.
No, data that resides on the root volume cannot be part of the NAS subclient content.
It depends on the OnCommand Unified Version. For OCUM 5.x, vFilers can be the destination location for SnapVault/SnapMirror copies. For OCUM 6.x, vfilers cannot be the destination location for SnapVault/SnapMirror copies as it is not supported by the OnCommand Unified Manager.
Yes. Restore of NAS data to a Windows or Unix computer using File System is supported for NAS iDataAgent snapshots.
No. When you perform a full backup, the Create New Index option is not available for selection as a new index is always created for NAS backups. During a full backup, the existing index is copied and modified to create a new index. The new index will then be incrementally updated with the changes of the current full backup.
Yes, you can enable the Image Backup Set option (for SnapMirror to Tape) on a backup set containing the SnapVault copy. However, for 7-Mode file servers the image backup of the SnapVault copy will not exactly match the primary (source) volume. For example, the non-qtree data on the primary volume will be in a qtree on the SnapVault copy; the SnapVault copy may also contain data from other primary volumes.
Yes. You must restart SnapMirror To Tape backups from the beginning of the job. You cannot restart SnapMirror to Tape backups from another point in the backup.
No. Backup filters cannot be used for SnapMirror to Tape backups. If you add filters, they are ignored.
No. In-Place restores of SnapMirror-To-Tape backups (also referred to as Image Backups) of the root volume on a NetApp file server are not supported. While you can perform a SnapMirror to Tape backup of the root volume, you cannot restore to it because the root volume cannot be turned offline.
No. The Direct Access Restore option is ignored for restores from image backups. If selected, the option does not affect the restore.
No. You should always use a new storage policy for catalog snapshots. If you wish to use an existing storage policy, ensure that no backup copy operations have been performed using the storage policy.
No. The storage policy should only be associated with a NAS subclient. If you associate the storage policy with subclients from other agents, you will not be able to perform a backup copy operation for those subclients.
No. Once the catalog snapshots option is selected and the backup is performed, you will not be able to switch to the previous configuration (backup copy).
NAS iDataAgent is supported.
ONTAP version 7.3 and higher.
If you want to catalog snapshots for specific backup jobs, you can do so by enabling manual selection of backup job from the storage policy. Once this is enabled, you need to manually pick the backup jobs to catalog from the list of storage policy jobs.
- From the CommCell Browser, navigate to Policies | Storage Policies.
- Right-click the <Storage Policy> and click View | Jobs.
- Clear the Specify Time Range check box from the Job Filter for Storage Policy dialog box, and then click OK.
By default, the jobs initiated in the past 24 hours are displayed. Clearing this option will display all the jobs associated with the copy.
- A list of jobs associated with the copy is displayed in the right pane of the CommCell browser.
- Right-click the job and select Pick for Catalog.
No. The option to re-catalog a snap backup job is not available.
Yes. The data will be pruned according to the retention criteria in the storage policy even though the backups are in picked state.
Yes, you can use a Vault copy as the source for cataloging data for NAS SnapProtect backup.
However, it is strongly recommended that you use a Mirror copy which has Primary or Mirror as the source. This is because the SnapVault copy may not exactly match the source volume.
For instance, if a qtree is created on a volume after the snap creation, it may not be included in the catalog and hence might not be available for browse and restore. Following is an example in which case a qtree added after snap creation will not be available for browse and restore:
- Create snap1 on Primary volume
- Create qtree1 on Primary volume
- Create snap2 on Primary volume
- Replicate snap1 and snap2 to the Vault node
In this case qtree1 will be transferred to the destination during baselining. After this snap1 and snap2 will be moved.
Since SnapVault works at the qtree level and not the volume level, when copying snap1 it will not copy qtree1 on the destination volume since qtree1 was not part of snap1. On the other hand since Snapdiff work at the volume level, when snapdiff is done between snap1 and snap2, it won’t find qtree1 as qtree1 is present in both snap1 and snap2 on the destination volume.
No. In order to properly configure and use Cluster-Mode arrays, all components must be version 10 or later.
Infinite Volumes can be backed up using the Network Share Backup support as described in the documentation for Infinite Volume Backup Support. It is not recommended to use the NAS iDA to protect infinite volumes since there is limited snapshot indexing support and NDMP backups are not supported.
No. You cannot browse subclient content from SnapProtect backups on Cluster-Mode NetApp arrays.
No. You can back up either Vservers or the entire cluster. You cannot back up physical cluster nodes.
No. You must follow mount points for Cluster-Mode NetApp arrays. Junction points are not supported.
SMTape is only supported for Cluster-Mode NetApp arrays running ONTAP 8.3 or later. The array must also belong to a SnapProtect version 10 CommCell updated to SP9 or later.
When creating a Schedule Policy, the Skip Catalog Phase for Snap Backup option only appears for NAS agents. If a non-NAS agent is selected, the Skip Catalog Phase for Snap Backup option will not be visible. Refer to Skip Catalog Phase for SnapProtect Backup for more information.
- Manually unmount the Infinite volume at a junction point
- Perform revert operation through GUI
- Manually mount the Infinite volume at a junction point
Note that GUI mount from infinite volumes are read-only, CIFS share/NFS export is mounted from a snapshot because infinite volume does not support volume clone from snapshot.
Consult NetApp documentation to volume mount and unmount at a junction path for more information.
GUI mount from infinite volumes are read-only, CIFS share/NFS export is mounted from a snapshot because Infinite volume does not support volume clone from snapshot.
Indexing Infinite Volume snap backups has limited support. Therefore, the statistics shown might be inaccurate.
No, infinite volume does not support SnapVault or SnapMirror because it is not supported by OnCommand Unified Manager 6.0.