Phoenix provides the Backup to Cloud if unable to backup to Cache option to back up the server data to Phoenix Cloud in case Phoenix CloudCache is not available or not reachable. Selecting this option ensures that your server backups are always complete even if your configured Phoenix CloudCache is either unavailable or unreachable during the backup timeframe of a backup set mapped to the CloudCache. The disadvantage of selecting this option is that all the backed up server data in the hot snapshot might not be present on the CloudCache, which means that backup data might not be truly hot. So, during restore, the data might have to be fetched from the Phoenix Cloud.
If your organization preferred to have the hot snapshot data stored locally on the CloudCache, you need to disable the Backup to Cloud if unable to backup to Cache option. This enforces to store the backup data always on the Phoenix CloudCache. If CloudCache is unavailable during the backup timeframe of a server, the backup fails after trying a certain number of retries to connect to the CloudCache. For more information about disabling the option, see Configure CloudCache page.
Note: To enable this option, you must upgrade the Phoenix agents to version 4.3 or later and Phoenix CloudCache to version 3.1 or later. After upgrading Phoenix CloudCache, CloudCache backs up all deduplicate blocks in all subsequent backups.
After you upgrade your CloudCache to a version that supports true hot restore, you need to detach the backup set from Phoenix CloudCache and attach the backup set again so that the latest backed up data is synchronized to the upgraded CloudCache.
Detaching and again attaching the backup set, results in a one-time full backup where all data present in the backup set as well as Phoenix Cloud is synchronized to the Phoenix CloudCache. 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 CloudCache. However, the data from the CloudCache is never synced to the cloud, then triggered decommission will process in the next schedule.