Design Question..

[SDMatt]

I'm looking at replacing my current Backup Exec setup with Veeam Backup and Replication, and I'm trying to figure out what pieces need to be installed/setup, and where.

I've searched through the forums, but I didn't see anyone with my particular scenario.

Here's a brief summary of my environment:

I have 8 remote sites to protect, each with their own ESX host - with approximately 1TB to backup.
My central office has 5 ESX hosts to protect, with about 20TB to backup off of an iSCSI SAN.

Remote sites are connected to central via 500MB WAN links, with the exception of 1 that uses a 1000MB link.

I average about a 2% daily change rate (e.g. my daily incrementals are about 2% of a full).
Most jobs are targeted to a Backup Exec Deduplication Folder.
Backups of our central office are replicated offsite to another Backup Exec server's Dedupe Folder.
Monthly backups of all data are archived onto tape.

From what I read my design should consist of:
1) a single backup server
2) a backup proxy on a VM at each of my remote sites
3) a backup repository - probably an existing SAS RAID Array attached to my [physical] backup server
4) for replication - a VMWare datastore at a remote site with enough storage to house replicated data
5) for replication - a backup proxy (can a single proxy be used for backup of local ESX and receive replicated data??)

Another design consideration I have is replication vs creating an offsite copy of my backup repository. Is this possible, and if so how? Is it baked in or would I be scripting something with Robocopy or RSYNC? Are there any special considerations I need to keep in mind (i.e. replication of any metadata)?

Thanks

[veremin]

Hi, Matt,

The described scenario looks solid.

A backup proxy (can a single proxy be used for backup of local ESX and receive replicated data??)

Tne machine can be used by both backup and replication jobs without any issues.

Is this possible, and if so how? Is it baked in or would I be scripting something with Robocopy or RSYNC?

If you're after creating additional copy of existing backup data, then, the backup copy job would the way to go. More information regarding it can be found here.

Another design consideration I have is replication vs creating an offsite copy of my backup repository

I recommend using both, because they serve different purposes. Backup copy job gives you an additional copy of backup data (backup copy job), meanwhile, replication job is used mostly as Disaster Recovery means that provide you with minimal RPO/RTO.

Thanks.

[SDMatt]

I recommend using both, because they serve different purposes. Backup copy job gives you an additional copy of backup data (backup copy job), meanwhile, replication job is used mostly as Disaster Recovery means that provide you with minimal RPO/RTO.

Good point.. Backup strategies have really evolved from the old fashion DR model to more of a business continuity model.. that's something that my current backup solution is lacking.

Thanks for the feedback on the design.

[veremin]

Glad to hear my input was helpful. Also, there is a great blog post that describes ultimate backup infrastructure; should give some hints on how backup and backup jobs should be properly utilized. Thanks.