Availability Machines
Availability Machines is a data management and data governance application that features managing snapshots, data sanitization, managing native backups, creating data access policies, and creating clones. You can also share your availability machine data with users who have data owner access.
Prerequisites
Ensure that you have created your database service in the Provisioning application under DB Services app family.
For more information on provisioning, see Provisioning an Oracle DB service.
Introduction
Availability Machine (AM) is an in-built application under the DB Services app family in Tessell. It offers DBAs and data administrators a centralized approach to data management, featuring differentiated automation, heavy-lifting operations, and robust data protection. When you provision a database service in Tessell, an Availability Machine gets associated with it. AM is a logical construct that encompasses the data management aspects for each database service. Availability Machines are owned by the data owners who own the database services.
Availability Machine supports:
Create and maintain database snapshots/native backups for data protection purposes. The backups are retained for short-term or long-term periods as per the RPO policy.
Take transactional logs backups as per the RPO policy.
Sanitize the data or mask the sensitive information and create sanitized snapshots.
Create database-native backups for long-term retention.
Create Data Access Policies (DAP) that help to control data sharing: what to share, how much to share, with whom to share, when to share, and where to share.
Refer to the Glossary for definitions of related terms used in this document.
Availability Machines dashboard
On the left-side menu bar of Tessell portal, select Availability Machines under DB Services to view the Availability Machines dashboard. This lists all the available AMs on its dashboard.
The fields in the dashboard filters are:
Search - In the search bar, you can specify the name of the database service to search and list the details of corresponding AM.
Engine - You can choose a database engine from the dropdown list. By default, it lists all the database engine services. The possible values are All, MySQL, Oracle, PostgreSQL, SQL Server, MongoDB, and Milvus.
Cloud - You can choose a cloud provider from the dropdown list. By default, it lists all the cloud regions. The possible values are All, AWS, Azure and OCI.
Owner - You can choose a specific username from the dropdown list to view the details of the database services owned by the user. By default, it lists all the owners. The possible values are All or any username.
Subscription - You can choose a cloud subscription from the dropdown list. By default, all the subscriptions are displayed. The possible values are All or any subscription.
Clear - Click this to clear the selected filters and revert back to default settings.
The fields in the table provide an overview of the availability machines for the services you created:
Name - Displays the name of the database service provided during provisioning your database. It also displays the database engine icon you have chosen for your database service. If you select the service name, it takes you to the AM home page of that database service.
Cloud and Region - Displays the cloud and region name you chose to host your database service during provisioning.
DAPs - Displays the data access policies configured for the database service. These data access policies are created and managed from the AM's home page.
Source DB Status - Displays the status of the database service associated with the AM.
Ready
Source database service is up and running. The connections are allowed after it is in ready status.
Stopped
Source database service is not running. The connections are not allowed after it is in stopped status.
Deleted
Source database service is deleted and the AM is not deleted.
Created - Displays the date and time on which your database service is created and assigned Availability Machine to it. It also displays the username who created the database service and assigned the AM.
Ellipsis icon - The ellipsis icon is enabled only if the source database service is deleted. It provides the option to delete the AM.
Figure 1 - Availability Machines dashboard
Availability Machine home page
Selecting any of the database services from the AM dashboard takes you to the home page of that availability machine. Every AM has a separate home page with its statistics.
Activities and updates
On the Availability Machine home page, the status of the source DB is displayed next to its name.
On the top right-side, you see the following options:
DB Service
Click to go to the My Services home page of the database service. For more information, see My services.
Dataflix
Click to go to the Dataflix home page of the database service. For more information, see <Dataflix app>.
Update RPO Policy
The Recovery Point Objective (RPO) policy dictates the frequency and retention policies for Tessell captured automated DB service snapshots and logs. This is done to ensure DB recoverability and data protection.
Click this option to update the recovery point objective policy.
Update RPO Policy and Schedule window opens to update the RPO policy and apply the changes:
Include Transactional Logs - Selecting this check box indicates Tessell platform takes backup of transaction logs (archive logs in case of Oracle). The backup of transaction logs is done at a frequency of 5 mins. These are stored in an S3 bucket in case of AWS and blob storage in Azure.
Schedule Snapshots - Toggle this option to schedule snapshots.
Tessell platform uses cloud-native snapshots as the default backup mechanism. These snapshots are application consistent in nature. They are always incremental and are much faster to restore.
Select the configuration type for RPO policy, Standard or Custom.
For Standard policy:
Specify the snapshot retention days in the range of 1 to 35 days.
Pick a time you wish to take the snapshot of your database service
For Custom policy:
Choose a RPO policy from the dropdown list.
To use an RPO policy, ensure that you have created an RPO policy in the DB governance application under the Governance app family.
Pick a time you wish to take the snapshot of your database service.
RPO Policy Details window displays the details related to chosen RPO policy, It includes:
Description of the policy if available
Type of the policy, Standard or Custom
Whether PITR is enabled for your policy or not.
Select the desired frequency for the RPO Policy to create and store snapshot backups.
RPO Policy - Displays the selected RPO Policy. The possible options are one or more from Continuous Recovery (PITR), Daily Snapshots, Weekly Snapshots, Monthly Snapshots, and Yearly Snapshots, as per the option selected in the RPO policy field above.
Every - Depending on weekly, monthly, or yearly schedule, select the frequency of the snapshot. For Daily Snapshots, this field provides the scheduled time of the snapshot in the day. For PITR, this is disabled.
Keep for - Displays the number of days for which a snapshot or a backup needs to be retained as per the selected RPO policy in the above field.
Schedule Native Backups - Toggle this option to schedule native backups. This is supported only for Oracle database services. The native backup here refers to RMAN backups. These RMAN backups are stored in object storage of your cloud accounts.
Select the configuration type for RPO policy for the native backups, Standard or Custom.
For Standard policy:
Specify the backup retention days in the range of 7 to 35 days.
Choose a day from the Full backup day dropdown list.
Pick a time from the Full backup time dropdown list.
Pick a time from the Incremental backup time dropdown list.
For Custom policy:
Choose a RPO policy from the dropdown list.
To use an RPO policy, ensure that you have created an RPO policy in the DB governance application under the Governance app family.
Choose a day from the Full backup day dropdown list.
Pick a time from the Full backup time dropdown list.
Pick a time from the Incremental backup time dropdown list.
RPO Policy Details window displays the details related to chosen RPO policy, It includes:
Description of the policy if available
Type of the policy, Standard or Custom
Whether PITR is enabled for your policy or not.
Select the desired backup frequency for your RPO Policy.
Policy Frequency - Displays the selected RPO Policy. The possible options are one or more from Continuous Recovery (PITR), Daily Backups, Weekly Backups, Monthly Backups, and Yearly Backups, as per the option selected in the RPO policy field above.
Every - Depending on weekly, monthly, and yearly schedule, it provides the frequency of the backup. For Daily backups, this field provides the scheduled time of the backup in the day. For PITR, this is disabled.
Keep for - Displays the number of days for which a backup needs to be retained as per the selected RPO policy in the above field.
The RMAN backups are taken on the source database service VM itself. If there are multiple database services on the same VM, stagger the native backup timings for each database as a best practice.
Select the Update button at the bottom to apply the changes.
Summary
Expanding the top bar on the AM gives a summary of the AM.
Summary includes following details:
RPO Policy and DB details
RPO Policy - Displays the number of retention days and type of backup as per the policy.
Transaction Logs - Displays whether transaction logs are enabled.
Source DB Status - Displays the status of the source DB service for this AM. The possible values are Ready, Stopped, and Deleted.
Cloud details
Cloud - Displays the name of the cloud hosting your database service.
Region - Displays the name of the cloud region hosting your database service.
User details
Owner - Displays the username of your Tessell account's owner.
My role - Displays your role for the database service. The possible values are Owner, Co-owner, or Read-only.
TRN - Displays the Tessell resource name. The TRN is a globally unique ID. Use the copy button to copy the TRN.
When you click a database service in the AM dashboard, various tabs are displayed on the AM home page that includes, Data Flow, Snapshots, Sanitization, Native Backups, Access Policies, Clones, and Sharing. Let us discuss each of these tabs in the next steps.
Figure 2 - Availability Machine home page
Data Flow
The Data Flow tab displays how the data is moving in the system. The data owner can configure a RPO policy and Data Access Policies (DAP) for the AM. This tab displays the flow of the data from your database service (source DB) to AM and from AM to different regions as per the configured RPO policy and DAPs.
The main box represents your source DB. The central box is your AM that is acting as the central data management construct. The box with a hand-shake icon shows your configured RPO policy. There is a continuous stream of data flowing from source DB box to AM box representing that data from source DB is captured via snapshots and logs are continuously captured and are retained as per the configured RPO policy.
If your database service is configured as multi-AZ, then the snapshots and transaction logs backups are taken from the primary node and replicated to the replica region boxes and retained as per configured RPO policy for that particular region. The data flow from AM to different region boxes is different as per the configured RPO policy and DAP policies for that region. The region with the manual snapshots does not have any continuous data flow from AM as the manual snapshots are retained until you delete it manually.
You can zoom in or out using the + or - icons from the bottom left corner of the page. Also, you can view the Data Flow in full screen using the expand screen icon from the bottom left of the page.
Snapshots
Snapshots of your database service are automatically taken, as per the configured RPO policy. You can also manually create an ad-hoc snapshot at any time. Snapshots tab displays all the details of the collected snapshots for your database service.
On the top, you can specify the name of your snapshot in the search bar and search for the particular snapshot and its details.
You can filter the snapshots according to the status using the Status field next to the search bar. The possible status of the snapshots are:
All - Displays all the snapshots with any of the possible status, it is the default option.
Available - Select this option to list all the available snapshots as per the RPO policy configured for your database service.
Queued - Select this option to list all the snapshots that are scheduled and are waiting on any other task to get started.
Creating - Select this option to list all the snapshots that are getting clicked and are not completed yet.
Failed - Select this option to list all the snapshots that are not completed and failed because of some reason.
Click Clear to clear the applied filter to search bar and status fields.
By default, it displays the list of all the manual snapshots and its details.
To take a manual snapshot,
Click + Take Snapshot button at the top right corner.
Specify the snapshot name and then click Submit.
Note: Tessell does not automatically delete the manual snapshots. You must return to this tab and delete them manually.
Select Automatic Snapshots to list all the automatic snapshots and its details. The automatic snapshots are taken as per the RPO policy configured for your database service.
The table on Manual Snapshots and Automatic Snapshots displays the following details for each snapshot in each row:
Snapshot Name - Displays the name of the snapshot.
Availability - Displays the number of regions for which the snapshot is available. Select the region for a particular snapshot to view the details of the region where the snapshot is available. It provides:
Region - Displays the region name for which the snapshot is available. If a DAP is configured, this shows all the regions where the snapshot is replicated.
Status - Displays the status of the snapshot if it is available or not as per the RPO policy.
Access Policy - Displays the name of the access policy defined for your database service.
Shared with - Displays the name of the user with whom the snapshot is shared. It displays No users if not shared with the users.
Status - Displays the status of the snapshot. The possible options are Available, Queued, Creating cloud snapshot, and Failed.
Size (GiB) - Displays the size of the snapshot in GiB.
Snapshot Time - Displays the month, date, year, hours, and minutes exactly when the snapshot was taken.
Each of the manual snapshots taken, can be removed using the Delete option from the ellipsis icon at the end of each row. Automatic snapshots are deleted as per the RPO policy.
You can update the number of days to retain the snapshots for and the time when the automatic snapshots are taken using Update RPO Policy at the top right corner.
Sanitization
Tessell offers database sanitization as both an on-demand and an automated scheduled workflow. The sanitization workflow is designed to mask/sanitize sensitive information (like credit card data, PII data, and so on) before the copies of databases are created for lower environments.
You can sanitize the snapshots manually or you can create a schedule to sanitize the snapshots automatically. Sanitized snapshots are useful for application testing or user training when a full production dataset is not required. These snapshots can be used or shared as needed.
As you know your data best, you are expected to provide the sql scripts which mask the data before creating a snapshot for a lower environment.
You need a masking SQL script added to your script library to sanitize a snapshot. For more information, see <Script Library app>.
Whenever a snapshot sanitization request is submitted, a workflow is run at the backend which creates a clone VM using the source snapshot. After creating a clone VM, the masking SQL script is run on the clone VM. After the script is run successfully and the data is masked, it captures a snapshot from the clone VM and provides a sanitized snapshot.
On top of the Sanitization tab, you can specify the name of your sanitized snapshot in the Search bar and search for the particular snapshot and its details.
You can filter the sanitized snapshots according to the status using the Status field next to the search bar. The possible status of the snapshots are:
All - Displays all the sanitized snapshots with any of the possible status, it is the default option.
Available - Select this option to list all the available sanitized snapshots as per the RPO policy configured for your database service.
Queued - Select this option to list all the sanitized snapshots that are scheduled and are waiting on any other task to get started.
Creating - Select this option to list all the sanitized snapshots that are getting clicked and are not completed yet.
Failed - Select this option to list all the sanitized snapshots that are not completed and failed because of any reason.
You can also filter the snapshots based on a particular script. The possible values are All or list of the available scripts for your database service.
You can select the Clear button to clear the applied filter in search bar, status, and script fields.
By default, table displays list of all the sanitized snapshots and its details:
Snapshot Name - Displays the name of the sanitized snapshot.
Status - Displays the status of the sanitized snapshot. The possible options are Available, Queued, Creating, and Failed.
Schedule Name - Displays the name of the schedule through which this snapshot was sanitized.
Size (GiB) - Displays the size of the sanitized snapshot in GiB.
Script Name/Version - Displays the script name and version that was used to sanitize the data in the source snapshot.
Availability - Displays the number of regions for which the sanitized snapshot is available. Select the region for a particular snapshot to view the details of the region where the snapshot is available. It provides:
Region - Displays the region name for which the sanitized snapshot is available.
Status - Displays the status of the sanitized snapshot if it is available or not as per the RPO policy.
Access Policy - Displays the name of the access policy defined for your database service.
Shared with - Displays the name of the user with whom the sanitized snapshot is shared. It says No users if not shared with the users.
Snapshot Time - Displays the month, date, year, hours, and minutes exactly when the sanitized snapshot was taken.
Sanitize Snapshot
Click + Sanitize Snapshot to create a sanitized snapshot and do the following:
Specify a name in the Sanitized snapshot name field.
Choose a source snapshot from the dropdown list.
Both the manual and automated snapshots are available to choose.
Choose a data masking script from the dropdown list.
You are responsible for providing the sanitization script, as you have the most thorough understanding of your data.
Choose a version available for your script in the dropdown list.
Click Submit.
Select Show Schedules to see the list of all the schedules and its details for the sanitized snapshots.
Schedule Name - Displays the name of the schedule created.
Script info - Displays the name and version of the script which is used to sanitize the source snapshot.
Retention - Displays the number of days for which the sanitized snapshot is to be retained.
Snapshot Name Prefix - Displays the snapshot prefix name given at the time of creating the schedule.
Create on - Displays the date and time when the snapshot was sanitized.
Create Schedule
Click + Create Schedule to create a schedule through which the automated snapshots are sanitized automatically at the configured day and time.
Schedule Name - Specify the name of the schedule to sanitize the snapshots automatically.
Description - Optionally, specify the description for the schedule you are creating for your future reference.
Frequency - Select any of the available options:
Daily - Select daily to sanitize the snapshots daily.
Weekly - Select weekly to sanitize the snapshots weekly. Further, select the days on which you want this schedule to run.
Keep each snapshot for - Specify the number of days or weeks you want to retain the sanitized snapshots.
Snapshot name prefix - Specify any name to prefix the sanitized snapshots name. By default the prefix name is ‘Sanitized’.
Script - Select the script to be used for sanitizing the snapshots.
Script version - Select the version of the script from the dropdown list if available.
Click Save.
This schedule keeps sanitizing the snapshot at the scheduled day and time.
As an alternative method, use the code for creating a sanitized snapshot and sanitization schedule.
Use the Code button from the bottom left corner of the dialog box to view the code in different languages like Shell, Python, Go, Java, Javascript, and PowerShell.
You can copy or download the code using the respective buttons in the top-right corner.
Use the Close button at the bottom right corner to return back to the main window.
Native Backups
Database native backups, such as Oracle's RMAN technology, are used for this purpose. Tessell supports taking backups either from the source database or from the existing snapshots to avoid the load of the source database. Whenever a backup is created from the snapshot, a clone VM is created from the source snapshot and the database native backup utilities are run on the clone VM to take the native backups. The native backups are stored in the object storage of the corresponding cloud account subscription (in your data plane account).
You can search the backups list providing the backup name in the Search bar on the native backups tab.
Create backup
Click + Create Backup on the native backups tab to create a manual backup.
The Create Manual Backup window pops-up.
Specify the name of the backup in the Backup Name field.
Choose whether to take the backup from Database or the Snapshot.
If Snapshot is chosen, select the source snapshot from the dropdown list from which you want to take the backup.
The available snapshots are manual as well as automated snapshots in the list.
Click Create to submit.
It runs a workflow at the backend and captures the backup for your database service using the database native backup utilities.
As an alternative method, use the code for creating a backup.
Use the Code button from the bottom left corner of the dialog box to view the code in different languages like Shell, Python, Go, Java, Javascript, and PowerShell.
You can copy or download the code using the respective buttons in the top-right corner.
Use the Close button at the bottom right corner to return back to the main window.
The automatic backups are taken as per the RPO policy configured for your database service.
The table on the backups tab lists all the backups and their details:
Backup Name - Displays the name of the backup given at the time of creation.
Status - Displays the status of the backups. The possible options are:
Available - This status is displayed when the backup is available to you for use.
Queued - This status is displayed when the backups are scheduled and are waiting on any other task to get started.
Creating - This status is displayed when the backup creation is in progress and it is running in the background.
Failed - This status is displayed when the backups are not completed and failed because of some reason.
Size - Displays the size of the backup in GiB.
Type - Displays whether it is a full backup or incremental backup.
Created From - Displays whether the backup is created from the database or the snapshot.
Availability - Displays the number of regions where this backup is available. Select the number of regions to find out more details on the regions like name of the region, status of the backup in that region, access policy for that region and name of the users with whom backup is shared.
Created on - Displays the date and time when the backup was taken.
Shared With - Displays the name of the users with whom the backup is shared.
Select the ellipsis icon on the right-side to delete the backups using the Delete icon on each row.
Access Policies
The Data Access Policy (DAP) is one of the key data management services that helps data owners to manage the availability of database snapshots and/or transaction logs for secondary environments like DR, testing, staging and so on. They can be made available for secondary use-cases like backup, archiving, data sharing, or migration, in the same region or across regions.
Production snapshots can be shared as-is, or they can be masked or processed before they are made available. Using the DAP, a data owner can define where the database snapshots or logs can be made available, whether in another region or even in another cloud subscription/account (within the same cloud provider). As part of the configuration, the data owner can define which users or user-groups can access the data for the specified policy.
You can make use of the shared data (snapshots/logs) to create a secondary copy of the database. If the DAP has continuous recovery enabled, you can also create a point-in-time database copy. The DAP can also be used to refresh lower environments on a regular basis or a defined cadence.
You can search the access policy list providing the policy name in the Search bar on the access policies tab.
The table on the access policies tab lists all the policies and their details:
Policy Name - Displays the access policy name.
Status - Displays the policy status whether the policy is active or inactive.
Shared Across - Displays the number of subscriptions the data is shared.
Content Type - Displays the content type, whether it is as-is data, sanitized data, or backups. Also displays whether the data shared is automated or manual.
Available Content - Displays the frequency and retention period in days for the content availability.
Click the ellipsis icon on the right-side to see following options:
Manage Access
Select Manage Access option to add more users to grant access.
Manage Access dialog box opens.
Specify the name of the users to grant access.
Click Update Access.
Update - Select this option to update policy details like name, target subscription, and the content settings.
Delete Policy
Select Delete Policy option to delete the policy.
The Delete DAP dialog box opens.
Select the confirmation box, Remove the access policy.
Click Remove.
This action revokes user access to the shared snapshot through this policy.
The underlying cloud snapshot is also deleted from regions.
Create Policy
Specify a policy name:
Click + Create Policy.
Create a new access policy window opens.
Specify a name for your policy in the Policy Name field.
Select target subscription:
Choose the desired target subscriptions, regions, and encryption keys for the data access policy. Additionally, specify the users who are granted access to the data.
Choose a subscription from the dropdown list.
Choose the desired target region for data replication.
Choose an encryption key from the dropdown list.
If another region is available in the selected cloud subscription, you can add another region.
In the Add users to grant access field, select the names of the users to grant access.
The replicated snapshots/logs in the target regions would be made accessible to these users.
You can also add another subscription if available and add the details in it.
Select data access mode:
Following modes are available:
As-Is Data
Share the source snapshots (PITR logs) as-is, without explicit processing.
Select whether to share automated snapshots or manual snapshots.
DAP content is effective following the subsequent automatic snapshot.
If an automated option is chosen, select frequency and retention period.
When the toggle switch is off, the default retention period is 1 day for PITR and 7 days for daily frequency. Toggle the switch to change the retention period in days for continuous recovery (PITR) and daily frequency.
If a manual option is chosen, select from the available manual snapshot list.
Sanitized Data
Share the source snapshots post processing (sanitized or masked copy).
Select whether to share automated sanitized snapshots or manual sanitized snapshots.
DAP content is effective following the subsequent automatic snapshot.
If an automated option is chosen, choose a schedule from the dropdown list.
If no schedule is available, select Click here to create a schedule.
Select the frequency and retention period in days.
For a daily frequency, 7 days is displayed by default, toggle the option to change the retention period.
Note: PITR is only possible in as-is data access mode.
Backups
Share native backup access for complete recovery.
Select whether to share automated backups or manual backups.
If an automated option is chosen, select frequency and retention period.
If a manual option is chosen, select from the available manual backups list.
Click Submit to share the data as per the configured access policy.
As an alternative method, use the code for creating access policy.
Use the Code button from the top right corner of the window to view the code in different languages like Shell, Python, Go, Java, Javascript, and PowerShell.
You can copy or download the code using the respective buttons in the top-right corner.
Use the Close button at the bottom right corner to return back to the main window.
Clones
You can create clones of databases running in Tessell using the Availability Machine and Dataflix applications.
On top of the Clones tab, you can specify the cloned service name in the Search bar and search for the particular clone and its details.
To filter the cloned services by the user who owns it, use the Owner field located next to the search bar.
You can select the Clear button to clear the applied filter in the search bar and the owner field.
Clones tab displays following details:
Name: Displays the cloned service name.
Status: Displays the status of your cloned service, available options are Creating, Ready, Stopped, and Deleted.
Cloud/Region: Displays the cloud provider selected for your cloned service, it displays the cloud region below the cloud details.
Source: Displays the source snapshot with name, time, and content type (For example, as-is).
Infrastructure: Displays the compute shape of cloned service.
Created: Displays the date and time when the cloned service creation is requested.
Create clone
Click + Create Clone.
This takes you to the Dataflix application, you can view a list of available snapshots, each with its corresponding timestamp, storage size, and number of regions.
Select from the available snapshots to view details like creation timestamp, size, number of databases, and the cloud details.
Click Clone at the bottom right corner of the window.
This takes you to the Clone creation flow.
You can change following options for your cloned service:
Service name, description, and the tags
Cloud provider settings
Compute shape
In compute shape, parent database server configuration is displayed. You cannot change the storage in compute shape for cloned service.
Configuring database instance
Additional settings like refresh schedule, maintenance window, performance insights, and availability machine
In the Refresh schedule, select from the options, No schedule or Automatic refresh.
For an automatic refresh, select the day you want to refresh the clone and refresh time.
Select the refresh mode, whether Snapshot or PITR.
Note:
In case of snapshot mode, the database is refreshed to the snapshot available at the selected time on the selected day(s) (computed based on the snapshot available at the source). If a snapshot is not available, the refresh is skipped.
In case of PITR, the database is refreshed to the latest available data at the selected time on the selected days. If no data is available, the refresh is skipped.
In the Custom Scripts for Refresh schedule panel you can select pre and post scripts from the respective dropdown list.
To use a custom script, ensure that you have uploaded scripts in the Script Library application under DB Services app family.
Click + Clone Service at the bottom of the form next to the left-hand menu bar.
As an alternative method, use the code to create a clone.
Use the Code button from the top right corner of the window to view the code in different languages like Shell, Python, Go, Java, Javascript, and PowerShell.
You can copy or download the code using the respective buttons in the top-right corner.
Use the Close button at the bottom right corner to return back to the main window.
The following steps are performed automatically:
Request is submitted to clone the database service
Creates compute instance(s)
Configures the database
Availability Machine is setup
Triggers first snapshot
Sharing
The Sharing tab allows you to share your availability machine with other users.
You can search the users list providing the user’s name in the Search bar on the Sharing tab.
Following details are displayed in sharing tab:
User - Displays a list of usernames with whom the availability machine is shared.
Role - Displays the user's defined role, which can be either Co-owner or Read-only
Click the ellipsis icon on the right-side of the user details to see following options:
Change Role
Click this option to change the role of a user.
A window pops up with the list of roles.
Select the role from the dropdown list, possible values are Co-owner and Read-only.
Click Update.
Remove User
Click this option to remove the user from sharing.
A window pops up with confirmation to remove the user.
Select the user to remove and click Remove.
To share an availability machine:
Click Share on the top right corner.
Add users to your service dialog box opens.
Choose a role from the dropdown list, possible values are Co-owner and Read-only.
Use the Search bar to search for specific users.
To grant access, move the users from the left Choices column and to the right Chosen column.
Only users with Data Owner roles appear in the left Choices column.
Note: Users and roles are managed in IAM application under the Governance app family.
Click Save to share your availability machine data.
Glossary
Clone
A duplicate of an existing database created from a snapshot or backup. A clone is typically used for testing, development, or troubleshooting without affecting the production database.
Data Access Policy (DAP)
Defines rules for accessing database data. It controls who can connect, what actions they can perform, and under what conditions.
Native Backup
A backup created using the database’s built-in tools (RMAN in case of Oracle). It supports full, differential, and transaction log backups for restoration.
Recovery Point Objective (RPO) Policy
Specifies the maximum acceptable data loss, measured in time. It defines how frequently backups or transaction log captures occur.
Snapshot
A point-in-time copy of a database or storage volume. Use a snapshot to restore the database to a specific state after maintenance or failure.
Sanitization
The process of creating a secure version of production data by applying data masking scripts to the snapshots. Sanitization ensures that snapshots can be safely used for development, testing, or analytics without exposing confidential information.
Transaction Logs
Sequential records of all database transactions. Use transaction logs to recover data or maintain consistency after an unexpected shutdown.
Last updated
Was this helpful?