[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eYou can access your protected data through various methods including cloning, LiveCloning, mounting, restoring, and utilizing workflows.\u003c/p\u003e\n"],["\u003cp\u003eClones create independent copies of data, commonly used for SQL Server databases and VMware VMs, ideal for development, testing, auditing, and other isolated data operations.\u003c/p\u003e\n"],["\u003cp\u003eLiveClones are similar to clones but can be updated on demand or scheduled, enabling teams to consistently work with the latest data, and allow for refresh, prep-mounting and prep-unmounting.\u003c/p\u003e\n"],["\u003cp\u003eMounting provides near-instant access to backup images without data movement, offering options like standard mounts for file system access, application-aware mounts for virtual databases, and mount and migrate for near-zero downtime.\u003c/p\u003e\n"],["\u003cp\u003eWorkflows automate data access tasks, including LiveClone management, data masking, and various mounting operations, providing simplified and secure self-service capabilities for end users.\u003c/p\u003e\n"]]],[],null,["# Different ways to access your protected data\n\nYou can access your protected data in the following ways:\n\n- [Clone](#clone)\n- [LiveClone](#LiveClone)\n- [Mount](#mount)\n- [Restore](#restore)\n- [Workflows](#workflows)\n\nClones\n------\n\nClones are commonly used with SQL Server databases and VMware VMs.\n\n### When to clone a Microsoft SQL Server database\n\nUse the clone function to create an independent copy of a Microsoft SQL Server\ndatabase backup images. The most common uses are the following:\n\n- Application development and testing\n- Data audit for compliance\n- Data warehousing\n- E-discovery\n- User acceptance testing.\n\nThis can also be used like a restore, but to any server.\n\n### When to clone VMware VMs\n\nFor VMware VMs, a clone copies backup images of the VMDKs directly to a targeted\ndatastore before powering on the VM, at which point the VM is independent of\nthe backup/recovery appliance. This is like a restore to a different VM.\n\nLiveClones\n----------\n\nA LiveClone can be used with all agent-based backup images like databases and\nfilesystems.\n\nThe LiveClone is similar to the clone function, however, unlike a clone,\na LiveClone can be updated on demand or according to a schedule. When an\nupdated copy of the data is available, a LiveClone allows an independent copy\nof a data to be mounted. This allows teams such as development and test to\nensure they are working on the latest set of data without having to manually\nmanage the data.\n\nLiveClones enable you to do the following:\n\n- **Refresh.** Create multiple, re-mountable copies of an active image that can be refreshed from the most recent image of the same application. See [Refresh a LiveClone](/backup-disaster-recovery/docs/access-data/liveclone#refresh).\n- **PrepMount.** Mount the LiveClone image to a specific host for a\n pre-processing operation (such as sanitizing data), even if some copies of\n this same LiveClone may already be mounted. You can prep-mount a LiveClone\n image to scrub confidential or sensitive data.\n\n | **Note:** While the LiveClone image is prep-mounted, it is busy. It cannot be deleted, refreshed, or mounted. If you mount application images before prep-mounting another image of the same application, the mounted images continue to be usable.\n- **PrepUnmount.** A prep-unmount operation on a LiveClone lets you decide\n if your changes are to be preserved or not. By default changes are tracked\n and preserved.\n\nLiveClones provide a crucial building block in managing copy data lifecycle as\nthey combine the performance and independence of a full clone with the\nefficiency and speed of incremental refreshes of data.\n\nMounts\n------\n\nThe Backup and DR mount function provides near instant access to\nbackup images without moving data. These are several options for mounting data.\n\n### VMware VM and agent based backup images\n\nThe standard mount presents and makes application data available to a target\nserver as a file system, not as an application. This is useful if an application\nis corrupt, lost, or if an application server is being replaced. In such cases\nyou can mount an image and copy the application files from the mounted image to\ntheir original location on the application server.\n\nFor standard mounts:\n\n- For VMware VMs ensure that NFS connectivity from the ESXi hosts to the backup/recovery appliance is available.\n- For Compute Engine instances, ensure that the iSCSI port of the host where the active images will be mounted is accessible to the backup/recovery appliance. Note that NFS is an option when mounting to instances running supported Linux operating systems.\n- Mounting takes a copy of the selected active image and mounts it to the selected host or VM.\n- A mounted image can be used directly from the mounted host.\n- The original image is never modified, even if the mounted virtual copy is modified or mounted and deleted.\n- The mount operation is applicable for all agent based applications and VMware VMs.\n\nApplication aware mounts allow you to mount backup images of databases as\nvirtual applications. This lets you quickly bring a database online without\nhaving to actually move the data and without having to manually configure a new\ninstance of the database.\nApplication aware mounts are particularly useful in test and development\nenvironments where multiple copies of a database must be quickly brought online.\n\nData presented as an application aware mount can be backed up like any other\napplication. Once the application aware mounted application data is backed up,\nit too can be can be mounted as an application aware mount.\nThe backup, application mount, backup sequence can be repeated to any depth.\nBy default, the sequence is restricted to five generations of the original\ndatabase.\n\nMount and migrate lets you restore an application with near-zero downtime\nby first mounting it locally, and then migrating it to the original location or\nto a new location. Users have normal access to the application while it is\nmounted, and the migration step is very fast.\n\nWhen performing a mount of a VMware VM or agent based backup from OnVault you\ncan control how much to optimize for performance versus storage consumption,\nby selecting the following:\n\n- **Storage-optimized.** This only keep writes in the local snapshot pool\n (writes are always kept locally).\n\n- **Balanced.** These blocks are read (from object storage) or written (to\n local snapshot pool) and kept in the snapshot pool, to serve as a cache for\n future reads.\n\n- **Performance-optimized.** This bring the entire image to the local snapshot\n pool, in the background. Reads will become faster as more of the image is\n available locally.\n\n- **Max performance.** The entire image is rehydrated into the snapshot pool\n first, prior to the mount. This means that the host always works against local\n storage only.\n\n### Compute Engine instance\n\nCompute Engine instance mounts create a new Persistent Disk from backup and\nthen either assign it to an existing Compute Engine instance or to a new\nCompute Engine instance, which is created at the same time.\nUnlike VMware VM or agent based backup images, this does involve the movement of\ndata from where the backup images are stored (in Google Cloud) to\nPersistent Disk.\n\nRestores\n--------\n\nThe restore function reverts the production data to a specified point in time.\nTypically restore operations are performed to restore an application to a valid\nstate after data corruption. The amount of time required to complete a restore\noperation depends on the amount of data involved.\n\nWorkflows\n---------\n\nA workflow automates access to copy data. While backup plan policy templates\ngovern the automated capture of production data, workflows automate the access\nto this data.\n\nSteps are defined within a workflow to perform a series of tasks on a schedule\nor on demand. This includes creating and refreshing LiveClones, data masking,\npersistent mounts, and non-persistent processing mounts for tasks such as\ndatabase integrity checks, and ETL loads. Workflows are also used by\nadministrators to provide simplified and secured self-service data access to end\nusers such as database administrators and application developers.\n\nThe Backup and DR getting started guide\n---------------------------------------\n\nThis page is one in a series of pages selected to introduce Backup and DR.\nThe other topics are as follows:\n\n- [Introduce the management console](/backup-disaster-recovery/docs/concepts/introduction)\n- [Introduce Backup and DR data protection backup plans](/backup-disaster-recovery/docs/concepts/backup-plan)\n- [Introduce Backup and DR data capture](/backup-disaster-recovery/docs/concepts/data-backup-overview)\n- [Different ways to access your protected data (this page)](/backup-disaster-recovery/docs/concepts/access-your-managed-data)\n- [Introduce the Backup and DR agent](/backup-disaster-recovery/docs/concepts/about-connector)"]]
