Dataprotection Flashcards
What is a Metro role
Role decides
1. Which site should commit the data first.
2. Where the user vms should be running for best performance.
What is a Metro role
Role decides
1. Which site should commit the data first.
2. Where the user vms should be running for best performance.
What is a Metro status
Metro status provides information about data synchronization between the two sites
What are different types of Metro Roles
Primary = primary site which commits the data first
Standby = Data is replicated from primary.
What are different types Metro status
In sync - both the sites have same data
Decoupled - Standby site has become Primary
Disabled - Metro relation is broken no more data sync will occur
Synchronizing - Data is being replicated but not completely in sync
Remote unreachable - Peer site is not reachable
What are different failure handling types in metro
- Manual -
- Automatic
- Witness
Which site’s metro status does automatic failure handling modify
Primary site status, it can disable the primary site’s metro relationship to make the container read write
Which site’s metro status does manual failure handling modify when there is an outage
None - manual disables both the sites if they are not able to talk to each other, administrator should modify the metro relation
Which site’s status does Witness modify when there is an outage
Both sites metro status will be modified by witness
Explain the relation between recovery_point, entity_snapshot and cerebro_snapshot uuid
This is applicable for entity centric snapshots only
When cerebro takes a snapshot it creates a UUID, to find the uuid you can go to cerebro page and look at the pd name it will provide you with the snapshot handle and cerebro snapshot uuid.
If you go over to the Entity centric page you will find the vm names and when you open a vmname you will find RP UUID for each snapshot handle, this RP uuid refers to an entry in recovery_point IDF table. Now this recovery_point entity in IDF has vm_recovery_point_list entry which referes to another uuid that points to a entry in entity_snapshot table. If we go to that entry we will find a backend cerebro snapshot uuid mapping in it. When v3/vm_recovery_point or vm_snapshots api, are queried it will check the entity_snapshot table in IDF not the recovery_point table. Recovery point table is more an internal reference table not for external clients. The recovery point table is managed by Polaris and updated by it
Where can you find the EC recovery points created by thirdparty backup software
Prism Central UI can show the recovery points for the vms including third party backup snapshots created.
