# Troubleshooting for the NetApp Storage Array

#### Snap creation fails with a busy LUN error

A snapshot enters a busy state in the following scenarios:

- When there are LUN clones being backed up in the snapshot

- When snapshots are mounted manually outside of the IntelliSnap backup, through the CommCell Console, or for IntelliSnap backup operations such as backup copy creation

Busy snapshots may cause IntelliSnap backups to go pending. If you have busy snapshots, consider the following:

- Delete the snapshots in the reverse order they were created in.

- Do not mount a volume and create another IntelliSnap backup for the volume.

  The IntelliSnap backup software will detect busy snapshots and will not allow an additional snapshot to be created until there are no busy snaps. To avoid this snapshot dependency, do not manually create a snapshot of a volume while you have a snapshot mounted.

- If you have a situation where the busy snapshot is no longer mounted but still shows as busy, proceed to delete all the additional snaps that were created while the busy snap was mounted. The snapshot will no longer be busy.

  For the 7-Mode system, to avoid the snap dependency on NetApp ONTAP version 7.3 and later, set the snapshot_clone_dependency or snapshot-clone-dependency volume option to on. With this option turned on, the snapshots can be deleted in any order even if they contain LUN clones.

  Note

  If you are using any application which relies on clones of LUNs on the same volume, review the NetApp documentation for impacts caused by using the snapshot_clone_dependency volume option. Refer to the article Examples of deleting backing Snapshot copies of deleted LUN clones, on the NetApp library.

  If you need to restore a usable LUN clone from a snapshot, the complete sequence of snapshots containing the clone, from the snapshot used to create the LUN clone up to the restore might need to be present on the volume.

#### Valid snapshots might get deleted before the snap backup jobs gets aged

On the volume properties on the NetApp software, if the option Automatically delete older Snapshot copies is selected, then valid snapshots might get deleted from the NetApp volume before the snap backup job gets aged in Commvault, which is a data loss scenario. To avoid the problem:

- Clear the Automatically delete older Snapshot copies check box.

- Ensure that you monitor the volume space usage and number of snaps on the NetApp console.

You can also use a command line to enable or disable Automatically delete older Snapshot copies:

     snap autodelete $[vol_name] $[on | off]

where vol_name is the name of the volume.

#### Unable to List Rules for Export for NetApp Cluster-Mode Mounts

##### Symptom

When you try to mount an NFS export through the NetApp Cluster-Mode, the following error is displayed:

Unable to list rules for export

##### Resolution

For NetApp Cluster-Mode, if an application mounts a directory or qtree in a volume, you must explicitly specify that the NFS export is created on the volume and the directory or the qtree is mounted. You can do this by defining the value for the additional setting sMOAllowCmodeNFSFolderMountSnap to Y (or y).

Configure the sMOAllowCmodeNFSFolderMountSnap additional setting. For instructions about adding an additional setting from the CommCell Console, see Adding an Additional Settings from the CommCell Console.

#### NFS Mount Operations do not Complete Successfully

##### Symptom

NFS mount operations do not complete successfully.

##### Resolution

For ONTAP versions prior to 8.2.3, if the Vserver root volume has the load-sharing snapmirror configured, ensure that the Vserver is configured with tunneling. This allows the update of the snapmirror on the root volume so that NFS mount operations complete successfully.

#### Netapp open replication jobs fail with a relationship mismatch error

For more information, see KB article 83177.

×

Loading...