Backup to NAS and S3 compatible in Veeam Backup & Replication

[grzegorz]

Hi everyone,

I have Veeam Backup & Replication and I use it to back up VMware virtual machines to a NAS disk over iSCSI. Additionally, I perform replication to a third host. There are several backup jobs and several replication jobs.

I recently purchased a NAS with WORM and QuObjects -S3 comp. I want to back up the same machines to this. Which Veeam functionality should I use?

Do I need to create new backup jobs for this additional repository, or can I modify existing jobs to save data to both locations?

I'm also considering using the Backup Copy feature. Can I use Backup Copy to save data to both the NAS disk over iSCSI and to the S3 compatible repository?

What is the best way to configure these jobs?

Thank you for any guidance and help!

[david.domask]

Hi Greg,

Backup Copy is probably the best answer here. Simply create an additional backup copy job with the same source job, and target the new storage.

You can accomplish this with a regular backup job as well, but keep in mind this means additional workload on the production environment (snapshots + backup), so Backup Copy is preferable in my mind if you're looking for additional copies.

[grzegorz]

Thank you for your response. I will do that and use Backup Copy Job. Which copying option is better: Immediate copy or Periodic copy? Won't immediate copy overload my network? Does it work like a backup job, mirroring, next backup, next mirroring?

[david.domask]

You're very welcome Greg.

As for controlling the Backup Copy, Immediate is usually best bet unless you have a specific reason for using Periodic. As noted in the User Guide, Immediate mode will ensure all new restore points have a copy in the Backup Copy chain, while Periodic mode will check at the scheduled time and copy the most recent restore point. So it's really a matter of preference for how you plan to meet the 3-2-1 rule.

To avoid overloading the network, there are a few controls you can use:

1. Backup Copy Window => Control when the Backup Copy is allowed to transfer data; you can set it for an inactive period when the network is not as busy

2. Network Throttling => Configure the limit for transfer between two Veeam components, in this case, the source and target Repository for the Backup Copy job

3. Adjust concurrent tasks on the target repository => This will limit how many tasks can be processed simultaneously; to avoid limiting the ingest rate on the source repository which likely will store more backups, I would limit the target in this case.

Any combination of those should help to manage the network traffic.

[grzegorz]

I'm having trouble with implementing the planned configuration.
I created a repository and added it to Veeam.




I want to create a Backup Copy Job and I'm getting an error message.



My license:


I'm not sure if this license allows for that.

[david.domask]

Hi grzegorz,

Looks like you have a merged license with a socket-based license. Merged licenses will take the level and functionality of the socket licenses in such cases, and follow the feature list here: https://www.veeam.com/veeam_data_platfo ... ets_ds.pdf.

Standard edition does not include backup to object storage functionality. Please consider migrating your socket license to VUL, or consider splitting the licenses.