![]() ![]() If the failover is undone or if you fail back to the original location, the replica IP address is changed back to its pre-failover state. If a rule applies, Veeam Backup & Replication mounts the VM disks of the replica to the backup server and changes its IP address configuration via the Microsoft Windows registry, all in less than a second. When a failover occurs, Veeam Backup & Replication checks if any of the specified re-IP rules apply to the replica. If the IP addressing scheme in the production site differs from the DR site scheme, re-IP rules can be created for the replication job. I wanted to share this here as a handy reminder of how network mapping and Re-IP works.įor Microsoft VMs, Veeam Backup & Replication also automates the reconfiguration of VM IP addresses. Access to the storage account is via public endpoints. This paired secondary region is determined based on the primary region and can’t be changed. Azure Storage Redundancyįor more detail on the different types of Azure storage check out my previous writeup here.įor the purpose of testing, A RA-GRS storage account was provisioned in Australia East from which Azure automatically configured the secondary region to Australia Southeast. The secondary location is located in a different geographic region than the primary location, ensuring that data is safe even in the event of a regional outage or natural disaster. The purpose of this article is to explore this second option by leveraging RA-GRS for achieving backup redundancy across two Azure regions.Īs a quick reminder, with RA-GRS and GRS, the data is stored in two separate locations, with one being the primary location and the other being a secondary location. The second option is to rely on the native storage redundancy provided by Azure, such as geo-redundant storage (GRS) or read-access geo-redundant storage (RA-GRS). First is a backup copy job from an external repository. Whenever using Veeam Backup for Azure, there are two recommended options for creating multiple copies of the backup data. Pick ‘Grouping expression’ as the Categorisation method. Tags can then be configured as the source for a Veeam backup job. Leveraging Veeam ONE’s business categorisation means we can tag VMs according to the specific ESXi host they are running on. For example, if there is a need to ensure transient VMs are protected to a local backup repository. In a stretched cluster scenario, where VMs can move between different data centres for improved availability and disaster recovery capabilities, the ability to group VMs based on their current location can be quite important. By leveraging the underlying ESXi host information, this feature allows IT administrators to create a seamless and dynamic approach to VM management, ensuring optimal backup and recovery strategies. The business categorisation feature available in Veeam ONE offers a solution for managing and organising virtual machines (VMs) within virtualised infrastructures, such as stretched cluster environments. ![]() To simplify this further, check out this fabulous table created by a fellow Veeam colleague, John Suh. ![]() In other words, whichever is longer out of the two will be the immutability period. 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: 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |