Skip to main content

How I Migrated Veeam Backup & Replication for Supermercados BH


matheusgiovanini
Forum|alt.badge.img+5

Recently, I had the opportunity to lead a challenging project for Supermercados BH, one of the largest supermarket chains in Brazil. The mission? To migrate the entire Veeam Backup & Replication environment to a new server, rebuilding everything from scratch. Instead of simply restoring the old configuration, we chose to redesign the architecture to optimize performance, security, and ensure a more efficient RTO.

 

One of the main concerns was the network design to ensure that backups and restores were fast and efficient. Properly segmenting the traffic, adjusting the transport proxies, and load balancing the repositories made all the difference. Additionally, we implemented an immutable repository based on Linux Red Hat, providing an extra layer of protection against ransomware.

 

Another critical point was backing up critical machines. For this, we configured snapshots via SAN, minimizing the impact on the production environment and speeding up the process. Of course, one of the key aspects of this project was the integration with Oracle RMAN via the Veeam plugin, ensuring consistent backups and restores aligned with the business requirements.

 

Besides the primary backup, we also set up a backup copy to an external repository in the datacenter, ensuring redundancy and protection against disasters. All of this was closely monitored with Veeam ONE, which helped optimize the environment’s performance post-migration.

 

In the end, this project reinforced some important lessons: well-planned architecture makes all the difference in recovery times, automation reduces errors and speeds up implementation, and continuous monitoring prevents headaches later on.

 

I’d love to hear your feedback - especially if you have any suggestions on improvements or different approaches I could have taken during the project. How have you tackled similar challenges?

lukas.k
Forum|alt.badge.img+10
  • Veeam Vanguard
  • March 3, 2025

Hi ​@matheusgiovanini,

The approach sounds great! It doesn’t matter how exactly you design the environment but preparation is king!

 

I know the customer (but not from my business experience tbh), does the customer move backups to a cloud / external S3 target?

 

From my personal opinion the S3 protocol (object storage in general) will in the future offer the most flexibility with native immutability among other features so this will be the way things move to.


matheusgiovanini
Forum|alt.badge.img+5
lukas.k wrote:

Hi ​@matheusgiovanini,

The approach sounds great! It doesn’t matter how exactly you design the environment but preparation is king!

 

I know the customer (but not from my business experience tbh), does the customer move backups to a cloud / external S3 target?

 

From my personal opinion the S3 protocol (object storage in general) will in the future offer the most flexibility with native immutability among other features so this will be the way things move to.

 

Thank you for your comment! I completely agree that preparation is key, regardless of how the environment is designed. Regarding S3, here in Brazil, the high dollar exchange rate often makes it challenging to move backups to an S3 or external cloud target, making it unfeasible in many cases. However, we have worked around this by using Backup Copy to an external datacenter, also leveraging immutability. This approach still aligns with the 3-2-1-1-0 rule, ensuring data protection and redundancy. I do recognize that object storage, especially with native immutability, is the direction things are heading, and I hope it becomes more viable in the future.


Comment