• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Restore node doesn´t work after Netapp Ontap Update


We have updated our Netapp from version 9.1P9 to 9.3P5. Now it turns out that the RESTORE NODE no longer works (BACKUP NODE always works).
The problem is that the TSM does not find the volume set to "Restricted" (worked under 9.1P9):

ANR2017I Administrator ADMIN issued command: RESTORE NODE in-sv-nasvm01-mir /in-sv-nasvm01-mir/tpd /in-sv-nasvm01-mir/RESTORE TYPE=SNAPM
ANR2516E RESTORE NODE: The specified file space, /in-sv-nasvm01-mir/RESTORE, does not exist on the NAS device associated with the node IN-SV-NASVM01-MIR.

If we mount the volume on the Netapp again, you get the message that the volume is not set to "Restricted":
ANR2017I Administrator ADMIN issued command: RESTORE NODE in-sv-nasvm01-mir /in-sv-nasvm01-mir/tpd /in-sv-nasvm01-mir/RESTORE TYPE=SNAPM
ANR2688E RESTORE NODE: The SnapMirror Restore of NAS node IN-SV-NASVM01-MIR, file system /in-sv-nasvm01-mir/tpd, cannot be started. The destination file system /in-sv-nasvm01-mir/RESTORE is not set to "Restricted" on the NAS device.

Has anyone the same problem and knows how to solve it? Calls are made to Netapp and IBM.

Kind regards
Walter Reis


Hi, I had a customer who had the same symptoms and it was resolved by working with netapp.
Also this error ANR2688E means the target destination was not set up as a snapmirror target

Check also https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.7/srv.reference/r_cmd_node_restore.html

SNAPMirror Specifies that the file system should be retrieved from a NetApp SnapMirror image. SnapMirror images are block-level full-backup images of a NetApp file system. A SnapMirror image can only be restored to a file system that has been prepared as a SnapMirror target volume. Refer to the documentation that came with your NetApp file server for details.
After a SnapMirror image is retrieved and copied to a target file system, Tivoli Storage Manager breaks the SnapMirror relationship that was created by the file server during the operation. After the restore is complete, the target file system returns to the same state as that of the original file system at the point-in-time of the backup.

When setting the TYPE parameter to SNAPMIRROR, note the following restrictions:

  • You cannot specify the FILELIST parameter.
  • Neither the source_file_system_name nor the destination_file_system_name can be a virtual filespace name.
  • This parameter is valid for NetApp and IBM® N-Series file servers only.


It was a error from netapp. It is fixed since version 9.3P7 (or 9.4P1)

"In that case it was discovered that NDMP SMTape restores fail in OnTap 9.3. The reason for the failure was due a change in OnTap behavior such that the "restricted" volumes, which are required for a snapmirror restore, are not returned to the DMA in the NDMP_CONFIG_GET_FS_INFO reply message. The DMA in this case is IBM Spectrum Protect.
The result achieved:
- the restore fails with ANR2516E in case the volume is restricted.
- the restore fails with ANR2688E in case the volume is online.
Per Netapp documentation: SMTape restore destination volumes must be in "restricted" state. However, OnTap 9.3 does not allow restricted volumes to be mounted. This results in these volumes not being included in the NDMP_CONFIG_GET_FS_INFO reply message sent back to the DMA as available volumes. The IBM Spectrum Protect server will fail the restore and report that the destination volume is not valid because it wasn't in the list of available olumes in the NDMP FS_INFO reply message.

Additionally, this changed behavior causes another more serious problem: For a DMA to perform a Cluster Mode NDMP restore from a locally attached tape drive, it needs the Netapp cluster affinity identifier for the destination volume. And the affinity ID is supposed to be sent by the filer to the DMA in the NDMP_CONFIG_GET_FS_INFO reply message. Since the filer no longer sends "restricted" volumes in the NDMP_CONFIG_GET_FS_INFO reply message the DMA doesn't know the cluster affinity for a restricted destination volume and you can no longer perform an NDMP SMTape restore."

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 59 60.8%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.4%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Latest member