Overview
The true hot restore feature enables you to backup and store the hot recovery point of the server data on-premise with the help of TurboTier.
In the event of failure with TurboTier, you can use the Backup to Cloud if unable to backup to TurboTier option on the Configured page, to back up the data directly to cloud.
You can:
Select this option to back up the server data on Druva Cloud, if the Hybrid Workloads agent is unable to synchronize the backup data to the TurboTier during a given backup time frame either because the TurboTier server is not reachable, or it has run out of the disk space. This ensures that the server backups are always complete.
However, when you select this option, it is likely that all the backed-up server data during a hot recovery point might not be present on TurboTier. Therefore, during restore, the data might have to be fetched from the Druva Cloud.Deselect this option if your organization prefers to store the hot recovery point data locally on TurboTier. If the TurboTier is unavailable during the backup time frame of a server, the backup fails after performing a certain number of retries to connect to the TurboTier. For more information about disabling the option, see Configure TurboTier page.
📝 Note
To enable this option, you must upgrade the Hybrid Workloads agents to version 6.x or later and TurboTier to version 4.2 or later(for TurboTier R1), and 6.0 or later(for TurboTier R3). After upgrading TurboTier, TurboTier backs up all deduplicated blocks in all subsequent backups.
After you upgrade TurboTier to a version that supports true hot restore, you need to reattach the backup set to TurboTier so that the latest backed up data is synchronized to the upgraded TurboTier. This will result in one time full backup where all data present in the backup set as well as Cloud is synchronized to the TurboTier.
For more information about detaching a backup set, see Detach a backup set. For more information about attaching a new backup set, see Attach a new backup set.
📝 Note
The data is resynced from the server to the TurboTier. However, if the data from the TurboTier is never synced to the cloud, then the triggered decommission job will process in the next schedule.