Stay organized with collections
Save and categorize content based on your preferences.
Depending on the application type, how it is managed, and where it resides in
the Backup and DR Service, the Access page lets you do the following:
Mount: This option provides instant access to data without
moving it. Use standard mounts to mount an application's data,
or an application aware mount to mount an entire application and
its data as virtual applications. Mounting an active image is
the fastest method. When you mount an image, you have full access
to its data. Mounted images use a virtual copy that does not take
additional storage. Captured copies of databases can be rolled
forward using the management console and mounted on any database server.
For more information on mounting active images,
see Mount images.
Clone: This option is used to create an independent
copy of a dataset. The most common uses include application
development and testing, data audit for compliance, data warehousing,
e-discovery, and user acceptance testing. Data sets can be copied to a
separate storage location anywhere in your environment.
For more information on clones, see Clone.
LiveClone: This option is similar to the clone function,
but unlike a clone, a LiveClone can be updated on demand,
or according to a schedule. When a refreshed copy of the data
is available, LiveClone allows an independent copy of a dataset
to be mounted, and then refreshes the primary data with the
independent copy. This allows teams such as development and test
to ensure they are working on the latest set of data without having
to manually manage the data. The LiveClone image appears adjacent to
the original data in the ramp view of the Access page.
For more information on clones, see LiveClone.
Restore. This option initiates all copy data recovery options
for a backup/recovery appliance and reverts the production data to a
specified point in time. Restores and clones are the only data
access operations that move data. Typically restore operations
are performed to restore a database to a valid state after a
massive data corruption. The amount of time required to complete
a restore operation depends on the amount of data involved. For background
information on restoring VMs and applications, see Restore overview.
Test Failover, Failover, Syncback, and Fallback: These replication
options are unique to Backup and DR Service. They are used with StreamSnap
managed applications to allow you to keep a remote copy of an
application's storage and configuration up-to-date and ready to be used
in a failover scenario, facilitating high-availability and redundancy.
When a StreamSnap managed application fails for any reason,
you can mount a failover image of the application from the
remote site—remote snapshot. When the problem has been resolved,
you can perform a restore to the local site with the
syncback image for the latest changes and then failback the
application to the production site. For detailed information
on failover and failback, see Failover and failback.
Expire: This option forces the expiration of an
active image earlier than its scheduled time in order to gain
storage space. For detailed information on expiring active images,
see Force expiration on active image.
Mark Sensitive: This option lets you mark an image as data
sensitive. Only users with access to sensitive data are able to see this
option. Sensitive images have a lock icon lock
next to their name in the timeline ramp view and the sensitive data column
set to Yes in the table view. For sensitive images, the actions drop-down
provides you with the option of marking the image as non-sensitive.
About data sensitivity
You can restrict access to sensitive data for certain users.
This is necessary when dealing with patient data in the healthcare domain for
example, or when using personal data in a test or development environment where
confidential information must only be handled by a select group of users.
By default, administrators, and those with administrator privileges, have access to
sensitive data. Your administrator can also give access to sensitive data to
individual users or to all members belonging to a certain role.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eThe Access page in the Backup and DR Service offers several options, including Mount, Clone, LiveClone, Restore, and replication options like Test Failover, Failover, Syncback, and Fallback, depending on application type, management, and location.\u003c/p\u003e\n"],["\u003cp\u003eMount provides instant access to data without moving it, allowing for either standard or application-aware mounts, while Clone creates an independent copy of a dataset for various uses like development, testing, and compliance.\u003c/p\u003e\n"],["\u003cp\u003eLiveClone is similar to Clone but allows for on-demand or scheduled updates to the dataset, ensuring teams have the latest data without manual management.\u003c/p\u003e\n"],["\u003cp\u003eRestore is used for data recovery, reverting production data to a specific point in time, typically used after massive data corruption, and is one of two options that move data.\u003c/p\u003e\n"],["\u003cp\u003eMark Sensitive allows you to designate an image as data sensitive, restricting access to authorized users, and administrators can manage sensitive data permissions.\u003c/p\u003e\n"]]],[],null,["# Access captured and backed up data\n\nDepending on the application type, how it is managed, and where it resides in\nthe Backup and DR Service, the **Access** page lets you do the following:\n\n- **Mount** : This option provides instant access to data without\n moving it. Use standard mounts to mount an application's data,\n or an application aware mount to mount an entire application and\n its data as virtual applications. Mounting an active image is\n the fastest method. When you mount an image, you have full access\n to its data. Mounted images use a virtual copy that does not take\n additional storage. Captured copies of databases can be rolled\n forward using the management console and mounted on any database server.\n For more information on mounting active images,\n see [Mount images](/backup-disaster-recovery/docs/access-data/mount-images).\n\n- **Clone** : This option is used to create an independent\n copy of a dataset. The most common uses include application\n development and testing, data audit for compliance, data warehousing,\n e-discovery, and user acceptance testing. Data sets can be copied to a\n separate storage location anywhere in your environment.\n For more information on clones, see [Clone](/backup-disaster-recovery/docs/access-data/clone).\n\n- **LiveClone** : This option is similar to the clone function,\n but unlike a clone, a LiveClone can be updated on demand,\n or according to a schedule. When a refreshed copy of the data\n is available, LiveClone allows an independent copy of a dataset\n to be mounted, and then refreshes the primary data with the\n independent copy. This allows teams such as development and test\n to ensure they are working on the latest set of data without having\n to manually manage the data. The LiveClone image appears adjacent to\n the original data in the [ramp view](/backup-disaster-recovery/docs/access-data/access-image-list-and-yaml#access-time) of the **Access** page.\n For more information on clones, see [LiveClone](/backup-disaster-recovery/docs/access-data/liveclone).\n\n- **Restore.** This option initiates all copy data recovery options\n for a backup/recovery appliance and reverts the production data to a\n specified point in time. Restores and clones are the only data\n access operations that move data. Typically restore operations\n are performed to restore a database to a valid state after a\n massive data corruption. The amount of time required to complete\n a restore operation depends on the amount of data involved. For background\n information on restoring VMs and applications, see [Restore overview](/backup-disaster-recovery/docs/restore-data/restore-overview).\n\n- **Test Failover, Failover, Syncback, and Fallback** : These replication\n options are unique to Backup and DR Service. They are used with StreamSnap\n managed applications to allow you to keep a remote copy of an\n application's storage and configuration up-to-date and ready to be used\n in a failover scenario, facilitating high-availability and redundancy.\n When a StreamSnap managed application fails for any reason,\n you can mount a failover image of the application from the\n remote site---remote snapshot. When the problem has been resolved,\n you can perform a restore to the local site with the\n syncback image for the latest changes and then failback the\n application to the production site. For detailed information\n on failover and failback, see [Failover and failback](/backup-disaster-recovery/docs/access-data/failover-and-failback).\n\n- **Expire** : This option forces the expiration of an\n active image earlier than its scheduled time in order to gain\n storage space. For detailed information on expiring active images,\n see [Force expiration on active image](/backup-disaster-recovery/docs/concepts/manage-image-expiration).\n\n- **Mark Sensitive** : This option lets you mark an image as data\n sensitive. Only users with access to sensitive data are able to see this\n option. Sensitive images have a lock icon lock\n next to their name in the timeline ramp view and the sensitive data column\n set to **Yes** in the table view. For sensitive images, the actions drop-down\n provides you with the option of marking the image as non-sensitive.\n\nAbout data sensitivity\n----------------------\n\nYou can restrict access to sensitive data for certain users.\nThis is necessary when dealing with patient data in the healthcare domain for\nexample, or when using personal data in a test or development environment where\nconfidential information must only be handled by a select group of users.\n\nBy default, administrators, and those with administrator privileges, have access to\nsensitive data. Your administrator can also give access to sensitive data to\nindividual users or to all members belonging to a certain role."]]
