H13-629_V3.0 · Question #498
In the scenario of protecting the database, when the slave end uses the virtual snapshot method to verify the LUN data consistency of the production end and the disaster recovery end, it is found…
The correct answer is A. After creating a snapshot of the LUN at the disaster recovery site, the snapshot is not activated at B. When creating a snapshot of the LUN on the disaster recovery side, the production side is C. The data sent for storage in disaster recovery mode remains in the cache and has not yet been. See the full explanation below for the reasoning.
Question
In the scenario of protecting the database, when the slave end uses the virtual snapshot method to verify the LUN data consistency of the production end and the disaster recovery end, it is found that the database of the disaster recovery end LUN cannot be started normally. What could be the possible reason? (Multiple choice)
Options
- AAfter creating a snapshot of the LUN at the disaster recovery site, the snapshot is not activated at
- BWhen creating a snapshot of the LUN on the disaster recovery side, the production side is
- CThe data sent for storage in disaster recovery mode remains in the cache and has not yet been
- DThe production and disaster recovery ends use the disaster recovery solution of incremental LUN
How the community answered
(27 responses)- A70% (19)
- D30% (8)
Topics
Community Discussion
No community discussion yet for this question.