![]() During the estimate phase, the agent fetches the database information from MS-SQL server using the Volume Shadow Copy API.If the services are not running, then the agent attempts to boot these processes automatically. Before the backup operation starts, agent checks if VSS Service and SQL Writer service are running or not.The request is executed after Hybrid Workloads agent is up and running. If the agent is not running, Druva queues the backup request. The full backup contains the following steps: To read more about CloudCache and hot recovery points, see CloudCache. A recovery point created in November, and retained based on the retention period can be considered as a cold recovery point for this example. You can see hot recovery points if you have configured CloudCache. You can directly restore your database using a warm recovery point. The recovery points created on February 1, 2017, and February 8, 2017, fall under warm recovery points. ![]() If the recovery point created on February 1, 2017, is the latest recovery point in the week ending February 5, 2017, 11:59:59 PM, it is retained based on the weekly retention period. When you trigger a restore job from the Hybrid Workloads Management Console, you see the following recovery point options to restore your data from:ĭruva retains a recovery point in warm storage for 90 days. Restoring a database from a recovery point created after a full backupįor example, you are restoring your database on February 12, 2017, at 11:00:00 AM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |