![]() On Archive Tier: Within the Archive Tier, data immutability is for the entire GFS retention period.Īn essential note from the forum post highlights that if the GFS retention period is shorter than the Repository immutability period, the Repository immutability period becomes the minimum for all backup files.On Capacity Tier: For backup data stored on capacity tier, the immutability aligns with the repository’s settings.Performance Tier with Move Policy Enabled: When the Move Policy is enabled within the Capacity Tier, unlike the previous example, immutability is applied as per the repository’s immutable retention period.Performance Tier with Move Policy Disabled: Similar to the previous scenario, if the ‘Move Policy’ is disabled within the capacity tier, the data will be immutable for the entire GFS retention period.Performance Tier without Capacity Tier: When using the Performance Tier without the Capacity Tier, data immutability holds for the complete GFS retention period.This means the backup data is secure and unchangeable throughout the entire GFS retention timeline. Standalone Repositories: In the case of standalone repositories, data remains immutable throughout the GFS retention period.The key takeaways from the forum discussion are as follows: To specify or change the quarantine network that will be used for infected machines, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 12).Determining immutability periods when working with Grandfather, Father, Son (GFS) backups can be a bit tricky considering GFS immutability periods can be determined by eitherī) the Backup Repositories immutability period.įortunately, Fabian from the Veeam R&D forums shared valuable insights that simplify this process. To change the resource group to which the recovered VMs will belong, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 9). To change the Microsoft Azure region in which the recovered VMs will reside, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 8). To change the cloud proxies used for job performance optimization, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 7). To change the repositories where the machine restore points are stored, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 6). To change the Microsoft Azure cloud subscription, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 5). To change the Veeam Backup & Replication server that will manage the process of recovering machines to Microsoft Azure, follow the instructions provided in section Adding Microsoft Azure Recovery Locations (step 4). To change target hosts and clusters to which recovered volumes will be mounted, follow the instructions provided in section Adding Storage Recovery Locations (step 6). To change the datacenter used to recover VMs, follow the instructions provided in section Adding Storage Recovery Locations (step 5). To change the target storage systems used to recover VMs, follow the instructions provided in section Adding Storage Recovery Locations (step 4). To enable or disable VM recovery across different Veeam Backup & Replication locations, follow the instructions provided in section Adding VMware Recovery Locations (step 9). To change the datastore capacity level that must not be breached during the recovery process, follow the instructions provided in section Adding VMware Recovery Locations (step 6). To change the destination datastores and datastore clusters where machine files will be stored, follow the instructions provided in section Adding VMware Recovery Locations (step 5). To change the target hosts and clusters where recovered VMs will be registered, follow the instructions provided in section Adding VMware Recovery Locations (step 4). To configure re-IP rules for recovered VMs, follow the instructions provided in section Adding VMware Recovery Locations (step 8) or Adding Storage Recovery Locations (step 8).To configure network mapping, follow the instructions provided in section Adding VMware Recovery Locations (step 7), Adding Storage Recovery Locations (step 7) or Adding Microsoft Azure Recovery Locations (step 11).To change the specified recovery options, follow the instructions provided in section Adding VMware Recovery Locations (step 3) or Adding Microsoft Azure Recovery Locations (step 3).To change the name and description of the location, follow the instructions provided in section Adding VMware Recovery Locations (step 2), Adding Storage Recovery Locations (step 2) or Adding Microsoft Azure Recovery Location (step 2).Complete the Edit Recovery Location wizard:.If you want to change settings specified while adding a recovery location, the Orchestrator UI allows you to customize the location.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |