- This topic has 1 reply, 2 voices, and was last updated May 25, 2021 by Kalsang D.
File system inconsistency after test recovery
The forum ‘Support Q & A’ is closed to new topics and replies.
During our recent test failover with the client the operation team had some difficulties with database. It seems that some of the file systems were corrupted and the database startup was not possible.
What can be the root cause of such problem. How does Zerto ensure the integrity and consistency of the data on target replication VMDKs?
From Zerto Portal everything looked correct, no issue reported, the RPO was below 10s.
This raised a serious concern about the Zerto recovery.
The production systems were clean and the databases were consistent. There were no problems to start up the production systems on primary site after the failover tests.
Hi,
This is Kalsang from Zerto.
There’re certain things to consider before doing Failover operations for database applications with Zerto. Feel free to review the below documents.
http://s3.amazonaws.com/zertodownload_docs/Latest/SQLBestPractices.pdf?cb=1621956721
If all the protocols are followed according to the above documents then I suggest submitting a ticket with us for further investigation.
Best regards,
The forum ‘Support Q & A’ is closed to new topics and replies.