Veeam Backup Copy Jobs

[Javezim]

Hey team,

We were advised today by a member of Veeam Support that if we ever have a failed upload, we have to do a whole new seed?!
Otherwise Merges will never complete and we will be unable to restore anything.
Some of our VMs are 6TB large base, so Re-seeding everytime there is only 1 failed transfer seems ridiculous.
Is there any merit to this, or should I escalate the case?

I am not sure if the Veeam rep was totally right because a few other things he said made me wonder.
- Veeam shouldn't be used for VMs of 6TB
- Veeam has a maximum of 6MBps (I know this isn't true!)

By failure I am talking about if we ever stop the job, or it fails to copy one of the VMs etc etc.
Apparently then the chain is completely broken and we have to reseed everything.
Anyone have any ideas?

[Shestakov]

Hi Ryan,
It depends what kind of error you had. If there was some connection problems, backup window exceeding etc. next backup copy run will run with no issues and reseeding is not needed.However if you had data corruptions, it can propagate to the next points of the chain and reseeding is highly recommended.

Could you provide your support case number?

- Veeam shouldn't be used for VMs of 6TB
- Veeam has a maximum of 6MBps (I know this isn't true!)

That`s not true, you are right. VBR successfully works with 200TB VMs and there is no speed limit for data transferring. Sorry for the confusion.
I would escalate the support case to talk to more experienced support manager.

[Javezim]

Whats worrying is that this was a tier 1 engineer.
But thanks for clearing that up re: the size of VMs and speed maximum.

So how do you know if you have data corruption in your chain?

[Shestakov]

There is backup files health check option which can determinate if there is any corruption. What error message did you have?
Do you leverage Surebackup verification for source backups?
Could you provide your support case number?