Replication management

Introduction

DCT 9.0.0 introduces the feature to differentiate between the replicated objects and original objects in case of a parent and replicated engines, both are registered with DCT.

Prerequisites

One parent and one replicated engine is required with few replicated dSources and VDBs.

User interface

Convenient separation between the replicated objects(VDB/dSource/environments) and original objects.
Users can filter the replicated object using the advanced filter.
All the actions on the replicated objects are disabled.
The status of the replicated objects are N/A.
On the VDB provisioning wizard, replicated objects(VDB/dSources) are marked as replicated.

API

Expand the section below to show search APIs that are updated to return three additional fields: is_replica, namespace_id, and namespace_name. These fields are described below.

Search APIs

Sources
GET: /sources
GET: /sources/{sourceId}
POST: /sources/search
VDBs
GET: /vdbs
GET: /vdbs/{vdbId}
POST: /vdbs/search
dSources
GET: /dsources
GET: /dsources/{dsourceId}
POST: /dsources/search
CDBs
GET: /cdbs
GET: /cdbs/{cdbId}
POST: /cdbs/search
VCDBs
GET: /vcdbs
GET: /vcdbs/{vcdbId}
POST: /vcdbs/search
Environments
GET: /environments
GET: /environments/{environmentId}
POST: /environments/search
Dataset-groups
GET: /groups
GET: /groups/{groupId}
POST: /groups/search
Timeflows
GET: /timeflows
GET: /timeflows/{timeflowId}
POST: /timeflows/search
Policies
GET: /virtualization-policies
GET: /virtualization-policies/{policyId}
POST: /virtualization-policies/search
Snapshots
GET: /snapshots
GET: /snapshots/{snapshotId}
POST: /snapshots/search

is_replica: Boolean telling that this object id replicated or not.
namespace_id: This field will only come for replicated objects and is essentially the namespace id of the replicated object.
namespace_name: This field will only come for replicated objects and is essentially the namespace name of the replicated object.