Skip to main content
NetApp Knowledge Base

Can SCE be restored from snapshot on primary storage?

Views:
20
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter 4.9
  • SnapCenter Plug-in for Exchange 4.9

Answer

Yes, Exchange Databases can be restored from primary storage snapshot

Additional Information

Steps to Take for Restoring
  1. On the left navigation pane, clickResources in the upper left corner of the Resource page.

  2. Select the Exchange Server plug-in from the drop-down list.

  3. In the Resources page, selectDatabase from the View list.

  4. Select the database from the list.

  5. From the Manage Copies view, selectBackups, from the Primary Backups table, and then click restore icon.

  6. In the Options page, select one of the following log backup options:

    Option Description

    All log backups

    Choose All log backups to perform up-to-the-minute backup restore operation to restore all of the available log backups after the full backup.

    By log backups until

    Choose By log backups untilto perform a point-in-time restore operation, which restores the database based on log backups until the selected log.

    Note The number of logs displayed in the drop-down list are based on UTM. For example, if full backup retention is 5 and UTM retention is 3, the number of log backups available are 5 but in the drop-down only 3 logs will be listed to perform restore operation.

    By specific date until

    Choose By specific date until to specify the date and time up to which transaction logs are applied to the restored database. This point-in-time restore operation restores transaction log entries that were recorded until the last backup on the specified date and time.

    None

    Choose None when you need to restore only the full backup without any log backups.

    You can perform one of the following actions:

    • Recover and mount database after restore - This option is selected by default.

    • Do not verify the integrity of transaction logs in the backup before restore- By default, SnapCenter verifies the integrity of transaction logs in a backup before performing a restore operation.

      Best Practice: You should not select this option.

  7. In the Script page, enter the path and the arguments of the prescript or postscript that should be run before or after the restore operation, respectively.

    Restore prescript arguments include $Database and $ServerInstance.

    Restore postscript arguments include $Database, $ServerInstance, $BackupName, $LogDirectory, and $TargetServerInstance.

    You can run a script to update SNMP traps, automate alerts, send logs, and so on.

    Note The prescripts or postscripts path should not include drives or shares. The path should be relative to the SCRIPTS_PATH.
  8. In the Notification page, from the Email preferencedrop-down list, select the scenarios in which you want to send the emails.

    You must also specify the sender and receiver email addresses, and the subject of the email.

  9. Review the summary, and then clickFinish.

  10. You can view the status of the restore job by expanding the Activity panel at the bottom of the page.

    You should monitor the restore process by using theMonitor > Jobs page.

When you restore an active database from a backup, the passive database might go into suspended or failed state if there is a lag between the replica and the active database.

The state change can occur when the active database's log chain forks and begins a new branch which breaks replication. Exchange Server attempts to fix the replica, but if it is unable to do so, after restore, you should create a fresh backup, and then reseed the replica.

For more information on how to restore Exchange Databases please go to the following link:

https://docs.netapp.com/us-en/snapcenter/protect-sce/task_restore_exchange_databases.html

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.