You cannot use Snap Creator to restore a SnapMirror copy of the data. If you want to restore a mirror copy, you need to break the mirror first, then manually restore the data. For more information, see the ONTAP 9 Volume Disaster Recovery Express Guide.

Only point-in-time volume restores are available when you restore a SnapVault copy from secondary storage. You cannot perform an up-to-the-minute volume restore or a single-file restore. You can work around this limitation by first restoring from secondary storage to primary storage. From primary storage, you can then perform an up-to-the-minute volume restore or a single-file restore as needed.

Volume restores and single-file restores typically have different destination directories. You specify the destination directory in the Data Restore Directory parameter in the backup and restore configuration file (see step task_using_the_gui_to_create_a_configuration_file.md#STEP_E6C507729B3647FD8B2E8D0818F22D3B):

This means that if you alternate restore types, you need to modify Data Restore Directory to point to the correct setting for each restore type. Otherwise, change information will not be applied correctly, and the data will be inconsistent with the database state you want to restore to. Of course, you can create different configurations for volume and single-file restores if you prefer.

With one exception, you can use either the Snap Creator GUI or the Snap Creator CLI to restore databases. For single-file restores in a SAN environment, you must use the CLI, as described in Performing a single-file restore in a SAN environment.

Related information

Performing a volume restore Performing a single-file restore Performing a single-file restore in a SAN environment