Versions Compared

Old Version 1

changes.mady.by.user Michael Litner

Saved on

compared with

New Version 2

changes.mady.by.user Dima Urban (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Add Source Host: define the connection to the server that hosts the source databases from which VDBs are created.

  2. Add Test Data Environment: define access to the source database that resides on the source host and create a golden image (GI).

  3. Add Target Host: define the connection to the server that hosts the VDBs.

  4. Add DB Home: define access to the target database that resides on the target host from which VDBs are created.

  5. Create (master) VDB: create and start a VDB on a golden image snapshot.

  6. Assign the VDB to the data consumer users.

...

Source Host

A source host is a server that hosts the source databases. To access the source databases, it is necessary to configure the connection to the source host. The following operations can be done on a source host object:

...

For more information, see MS-SQL Source Management.

Source Database

A source database can be a production database, a Data Guard Standby database, or a source database replica (for a LIVE GI) that resides on a source host.

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#EAE6FF

Source databases are created and managed with the test data environment object.

Golden Image

A golden image is a full synchronized copy of the source database files. A golden image is used to create VDBs. Golden images reside on the Accelario server.

...

  1. RMAN STANDBY GI – a golden image that is created and synchronized using RMAN incremental forever backup mechanism from a Data Guard standby source database. RMAN incremental backups can be automatically scheduled or a GI Refresh operation is used to do a manual backup.

  2. Native SQL Server Backup GI - provide automatic initial load and refresh using the customer Native SQL Backup files. The initial load and subsequent restores are scheduled automatically by the system.

Golden Image Snapshots

GI snapshot (GI snap) – a read/write point-in-time copy of the golden image. It uses minimum storage space because the unchanged data is accessed directly from the golden image. A GI snap can be created manually or can be scheduled.

Managing GI snapshots for a RMAN GI and a RMAN Standby GI

  • At the end of a successful refresh operation, a snapshot is automatically added.

  • A refresh operation is done each time a scheduled snapshot is added. Before the snapshot is added, the system automatically does an RMAN incremental backup operation.

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#EAE6FF

Golden images are created with the test data environment object.

Test Data Environment

A test data environment includes the access definition to one source database and a GI. The following operations can be done on a test data environment object.

...

For more information, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/21371969202176975966/Oracle21%3AOracle+Initial+Setup#To-create-a-test-data-environment%3A

For more information, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/21370985002176977920/PostgreSQL21%3APostgreSQL+Initial+Setup#To-create-a-test-data-environment%3A

For more information, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/21371964152176980307/MS21%3AMS-SQL+Initial+Setup#To-create-a-test-data-environment%3A

GI Management

After a golden image is made and started with the Create Test Data Environment operation, the golden image is shown in the VDB management work area. The following operations can be done on the three types of GI objects:

  1. Add or remove a snapshot manually.

  2. Create a VDB on a GI point-in-time snapshot.

  3. Modify the GI parameters.

Oracle

Additional operations available to do for a RMAN GI and RMAN Standby GI:

  1. Refresh GI – executing an RMAN incremental recovery. After a successful refresh, a new snapshot is added.

  2. Remove GI object – only a GI that does not have configured VDBs can be removed.

  3. Activate GI - when creating an RMAN GI without selecting Refresh immediately the GI is in deactivated mode. Use this operation to activate it.

Additional operations available to do for a LIVE GI:

  1. Activate LIVE GI – when the LIVE GI is created it cannot be activated automatically. It is only possible to do this after an initial manual copy of the source database is made by the system administrator. Only after the Oracle database files are moved and the source database is up is it possible to activate the LIVE GI.

  2. Deactivate GI - before a GI object can be removed it is necessary to remove its first snapshot. Only after the first snapshot is successfully removed is it possible to deactivate the GI.

PostgreSQL

Additional operations available to do for a LIVE GI:

  1. Activate LIVE GI – when the LIVE GI is created it cannot be activated automatically. It is only possible to do this after an initial manual copy of the source database is made by the system administrator. After the PostgreSQL database files are moved and the source database is up is it possible to activate the LIVE GI.

  2. Deactivate GI - before a GI object can be removed it is necessary to remove its first snapshot. Only after the first snapshot is successfully removed is it possible to deactivate the GI.

MS-SQL

Additional operations available to do for a Native SQL Server Backup GI:

  1. Activate Native SQL Server Backup GI – when the Native SQL Server Backup is created it cannot be activated automatically. It is only possible to do this after an initial manual copy of the source database is made by the system administrator. After the MS-SQL database files are moved and the source database is up is it possible to activate the Native SQL Server Backup.

  2. Deactivate GI - before a GI object can be removed it is necessary to remove its first snapshot. Only after the first snapshot is successfully removed is it possible to deactivate the GI.

Additional operations available to do for a LIVE GI:

  1. Activate LIVE GI – when the LIVE GI is created it cannot be activated automatically. It is only possible to do this after an initial manual copy of the source database is made by the system administrator. After the MS-SQL database files are moved and the source database is up is it possible to activate the LIVE GI.

  2. Deactivate GI - before a GI object can be removed it is necessary to remove its first snapshot. Only after the first snapshot is successfully removed is it possible to deactivate the GI.

Target Host

A target host is a server that hosts the VDBs that are used by the data consumer users. The following operations can be done on a target host:

...

For more information, see MS-SQL Target Management.

DB Home

A DB Home is the target database that is used to initiate VDB instances. A target database is defined by its DB Home. The following operations can be done on a DB Home object:

...

For more information, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/21371969202176975966/Oracle21%3AOracle+Initial+Setup#To-add-a-DB-Home%3A

For more information, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/21370985002176977920/PostgreSQL21%3APostgreSQL+Initial+Setup#To-add-a-DB-Home%3A

For more information, see https://accelario.atlassian.net/wiki/spaces/DVPD/pages/21371964152176980307/MS21%3AMS-SQL+Initial+Setup#To-add-a-DB-Home%3A

Managing VDBs

VDBs are the primary function to use the Data Virtualization Module. Because VDBs use snapshots as their database file containers they use minimal space and can be created quickly (usually in a few minutes).

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#EAE6FF

When an Oracle VDB is first created, the time that is necessary to create it is longer than the time necessary to create the other VDBs on the same GI. This is because when the first VDB is created, an additional Oracle recovery process is done to merge all the archive logs that were generated during the initial RMAN recovery process.

The following operations can be done on a VDB object:

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#EAE6FF

An admin-user and a non admin-user can do operations on a VDB object.

...

For more information, see MS-SQL VDB Management.

Shared Snapshots

Non-admin users can share snapshots with other non-admin users that belong to a different User Role. It is permitted only for User Roles that have authorization to the same Test Data Environment. Shared Snapshots are used to share a point-in-time copy of a VDB between different uses groups (e.g. Dev and QA) for development and testing purposes.

...

For more information, see MS-SQL Sharing Snapshots.

Managing Duplicates

Duplicates are a full point-in-time copy of the golden image or of a VDB file container. It uses the full capacity of the source database. It is treated as a mutable golden image with one snapshot from which VDBs and duplicates are created. Duplicates reside on the Accelario server.

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#EAE6FF

If a secondary storage pool exists, duplicates will automatically be created on this storage pool. Otherwise duplicates are created on the primary storage pool.

The following operations can be done on a duplicate object:

  1. Create a Duplicate – from any GI, VDB, or duplicate snapshot.

  2. Modify Duplicate – modify all the GI parameters.

  3. See info about the Duplicate.

  4. Remove Duplicate object – only a GI that does not have configured VDBs can be removed.

Users and Roles

The Data Virtualization Module uses a role-based user management system. Users and roles are divided into the following categories:

...

For more information, see Users Management.

Storage Pool Management

Storage pools are the storage containers of the Accelario server. These storage pools store the golden images and duplicates.

...

For more information, see Storage Pool Management.

System Setup

The System Setup is used to define the system setup such as SMTP, Active Directory, etc. The following operations can be done in the System Setup window:

...

For more information, see System Setup.

Event Viewer

Used to see and save all user events. The following operations can be done on Events:

...

For more information, see 21:Event Viewer