[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[[["\u003cp\u003eThe Restore function overwrites current production data with a selected point-in-time image, resulting in the permanent loss of all data created since that image.\u003c/p\u003e\n"],["\u003cp\u003eRestoring databases within a consistency group will overwrite ALL databases in that group, requiring a manual process if only specific databases should be restored.\u003c/p\u003e\n"],["\u003cp\u003eFor SQL Server failover instances and Availability Groups, the database restoration will occur on the active node.\u003c/p\u003e\n"],["\u003cp\u003eThe restore process can incorporate transaction logs to roll the database forward to a specific point in time, with options to select the date and time and determine whether to apply all, some, or none of the available logs.\u003c/p\u003e\n"],["\u003cp\u003eRestoring a consistency group with a database will result in a new database image being created with data from the selected point-in-time image and can include the option of bringing the database online immediately, preventing further log applications.\u003c/p\u003e\n"]]],[],null,["# Restore a Consistency Group\n\nThe Restore function reverts the production data to a specified\npoint in time. Restoring replaces the original production application\ndata with the specified point-in-time image. This restoration results in the\nloss of all current application data as the application is restored to its\nstatus at the point-in-time when the image was created.\nThis operation cannot be undone.\n\nTypically restore operations are performed to restore a database to event\nsuch as unexpected data corruption. The amount of time required to\ncomplete a restore operation depends on the amount of data involved.\n\nBefore you begin the consistency group restore process, note\nthe following considerations:\n\n- Be very careful when restoring databases in a consistency group. When you restore databases that are in a consistency group, ALL databases in the consistency group are overwritten. If you don't want to overwrite all databases in the consistency group, first mount a single database, then use the manual VSSRESTORE command to copy the database files to the required location.\n- For a SQL Server failover instance, the database is always restored to the active node. Management console mounts the backup image to the active node and performs the restore operation on the node. For SQL Server Availability Groups, the restore is also performed on the active node.\n\nRestore a consistency group\n---------------------------\n\nTo restore a consistency group:\n\n1. Click the **App Manager** tab and select **Applications** from the drop-down menu. The **Applications** page opens.\n2. Select the **Consistency Group** that you want to restore, then choose\n **Access** from the drop-down list.\n The **Access** page opens listing backup images in the timeline ramp view.\n Image types that support a Restore operation include snapshot,\n and remote snapshot (StreamSnap images).\n\n The timeline ramp view is a time-based visualization of backups for the\n selected application. Use your mouse to select a backup to restore.\n See [Access the Timeline Ramp View of an Image](/backup-disaster-recovery/docs/access-data/access-image-copy-data-list#access-time) for details.\n\n Background differentiates snapshot images containing database with\n transaction log files, and also illustrates the restore range time period\n for the logs.\n3. Select an image and then select **Restore** from the list of access\n operations. The **Restore** page opens.\n\n4. If the source application is protected by a snapshot policy that has\n enabled database log backups, and logs are available with the image,\n you can use them to roll forward to a specific point in time by changing\n these options in the **Roll Forward Time** section:\n\n - The **Date** field contains all possible dates that the database can be rolled forward to (through the application of database transaction logs). Select the date you need the database to be rolled forward to.\n - The **Time** field contains a slider showing all possible times on the selected date that the database can be rolled forward to. If you select the latest possible date and then move the slider to the right most position, the restore job applies to all available logs. If you select the earliest possible date and move the slider to the left most position, the restore job will apply no logs.\n - You can specify to roll forward using either **User Time** or **Host Time**. User Time is relative to the local time of the current user. Host time is relative to the system that hosts the data to be restored.\n5. Select a single volume or multiple volumes to restore. By default\n all the volumes are selected.\n\n6. For a consistency group with a database, check the\n **Restore With Recovery** checkbox if you don't intend to roll\n the database logs. Restore with recovery option brings the restored\n database online. Once the database is online, logs cannot be applied.\n\n7. Click **Submit** . The image is restored. If restoring a\n consistency group with a database, the backup/recovery appliance creates\n a new database image populated with data copied from the selected\n point-in-time image."]]