[[["易于理解","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\u003eThis process creates an instant virtual copy of an SAP HANA scale-out database from a backup image, suitable for data validation, logical recovery, or object-level recovery.\u003c/p\u003e\n"],["\u003cp\u003eThe virtual database is a fully functional copy in a new location that initially consumes no storage, only using incremental storage as changes are made.\u003c/p\u003e\n"],["\u003cp\u003eTo create the virtual copy, select "Mount" from the latest snapshot, choose the target HANA server, and configure the application options, including specifying the target database SID and user store key.\u003c/p\u003e\n"],["\u003cp\u003eYou can roll forward to a specific point in time using available database logs, allowing selection of a specific date and time for the restore.\u003c/p\u003e\n"],["\u003cp\u003eOnce the mount is no longer needed, you have options to unmount it, or unmount and delete the image, which will free up the storage and allow the backup image to expire.\u003c/p\u003e\n"]]],[],null,["# Mount an SAP HANA scale-out backup as a virtual database\n\n| **Note:** This information is for SAP HANA scale-out instances. For scale-up and HA 1+1 configurations, see [Backup and DR Service for SAP HANA](/backup-disaster-recovery/docs/concepts/backupdr-for-sap-hana).\n\nCreate an instant virtual copy of an SAP HANA scale-out instance to any target from a volume-level backup image for data validation\n-----------------------------------------------------------------------------------------------------------------------------------\n\nUse this procedure to create an instant virtual clone of a HANA database. The\nHANA database is recovered to the chosen point in time and the database\nis up and running and available. This new virtual clone can be used for\ndata validation and logical recovery or object-level recovery.\n\nA new virtual database, also called an application-aware mount, is a fully\nfunctional copy of the source database in another location. It consumes no\nstorage until you start writing to the database, when incremental storage is\nconsumed by the changed blocks. The new virtual database can be created with a\nnew HANA SID name.\n\n1. Click **App Manager** \\\u003e **Protected Application** \\\u003e **Access** , from the latest snapshot, choose **Mount**---not clone or LiveClone, which do different things.\n2. On the **Mount** page, from **Target**, choose the target HANA server from the drop-down.\n3. Under **Application Options**, complete the following:\n\n - Select **Create New Virtual Application**.\n - 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 which 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 applies 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.\n - For **Target Database SID**, provide the target HANA database name. In\n order to create the virtual copy, the target HANA database must be\n configured.\n\n - For SAP DB User Store-Key, provide the hdbuserstore key for the target\n database---for HANA 2.0: SYSTEMDB.\n\n - For **Mount Location** , specify a **Mount Point** to mount to new target.\n\n - At **Manage New Application** , if you want to reprotect the database copy,\n click and enable **Manage New Application**.\n\n - Choose a template and a profile to protect the database.\n\n4. Click **Submit** . At this point, the HANA database is recovered to the chosen\n point in time and the database is up and running and available for data\n validation. You can go to the **Job Monitor** to\n view the progress and details of the job. The mounted image is\n available in the [Active Mounts](#active).\n\nManagement of the active mounts\n-------------------------------\n\nOnce you have created a mount, you can track the image from the\n**App Manager** \\\u003e **Active Mounts**. Ideally, don't leave any image mounted\nindefinitely. This is because the backup image that the mount was created from\ncannot expire until all its mounts have been deleted. When you have finished\nusing the mounted image then perform one of the following actions:\n\n- [Unmount](/backup-disaster-recovery/docs/access-data/manage-active-mounts#unmount) the image. You can [remount](/backup-disaster-recovery/docs/access-data/manage-active-mounts#remount) it if needed. You can then [delete](/backup-disaster-recovery/docs/access-data/manage-active-mounts#delete) the image later when you are certain it is no longer needed.\n- [Unmount and delete](/backup-disaster-recovery/docs/access-data/manage-active-mounts#unmount-delete) the image. This deletes the mounted image, not the backup that the mount is based on.\n\nBackup and DR Service documentation for SAP HANA scale-out\n----------------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nSAP HANA scale-out instances with Backup and DR Service.\nYou can find additional information in the following pages:\n\n- [Backup and DR for SAP HANA scale-out](/backup-disaster-recovery/docs/concepts/backupdr-for-sap-hana-scaleout)\n- [Prepare SAP HANA scale-out instances for backup](/backup-disaster-recovery/docs/configuration/prepare-sap-hana)\n- [Add an SAP HANA scale-out host, and discover and protect its databases](/backup-disaster-recovery/docs/configuration/discover-sap-hana-scaleout)\n- [Configure staging disk format and backup method for SAP HANA scale-out](/backup-disaster-recovery/docs/backup/backup-method-staging-disk-sap-hana-scaleout)\n- [Set application details and settings for SAP HANA scale-out instances](/backup-disaster-recovery/docs/backup/app-details-settings-sap-hana-scaleout)\n- [Back up HANA 1+n and HANA scale-out databases](/backup-disaster-recovery/docs/backup/back-up-sap-hana-scaleout)\n- [Restore and recover SAP HANA scale-out instances](/backup-disaster-recovery/docs/restore-data/restore-sap-hana-scaleout)\n- [Mount an SAP HANA scale-out backup as a standard mount](/backup-disaster-recovery/docs/access-data/mount-sap-hana)\n- [Mount an SAP HANA scale-out backup as a virtual database](/backup-disaster-recovery/docs/access-data/mount-sap-hana-virtualdb)\n- [Mount and migrate an SAP HANA scale-out backup for instant recovery to any target](/backup-disaster-recovery/docs/access-data/mount-and-migrate-sap-hana)"]]