Backup Copy > Write-only NAS Share

[bcburns]

Hi folks,

I'm currently evaluating Veeam B&R.

We have a storage device that presents as a NAS. We'd like to copy our backups from our primary repository to this device.

The only caveat is that, generally, you can't read from the device except in special circumstances (e.g. reading the entire contents of the device).

Will this break Backup Copy? Can we use File Copy instead?

Thanks!

[Shestakov]

Hi Brad and welcome to the community!
Backup copy job needs to read from repository since it performs merges. File copy just writes, but it will take much more space.
Is there a chance to grant full rights to VBR?
Thanks!

[dellock6]

What is the use case for this design? Having protected secondary copies of the backup to be safe from deletions or cryptolocker-style attacks?
There are ways to configure permissions on each storage or share to prevent this even without placing the entire volume in write-only. Also because a delete, depending on the filesystem, has the same rights of a write, so it could not be enough to just allow writes.

[bcburns]

What is the use case for this design? Having protected secondary copies of the backup to be safe from deletions or cryptolocker-style attacks?
There are ways to configure permissions on each storage or share to prevent this even without placing the entire volume in write-only. Also because a delete, depending on the filesystem, has the same rights of a write, so it could not be enough to just allow writes.

Great question.

Writes on the NAS aren't restricted by permissions. They're restricted by the architecture of the target NAS. Reads are possible, but they can take several hours to access. The architecture is cloud-backed or tape-backed with a disk cache frontend. It's approximately equal to a Amazon Cloud Gateway backed by Glacier.

Deletes are handled as part of a separate metadata interface that is split out from the data path.

[dellock6]

As soon as you said several hours I thought exactly about Glacier. I'd say that in this case, it's not a suitable target for Veeam, thinking of how our data patterns are in terms of read and writes. Unless again you use file copies, but at this point you can even use file system copy capabilities to store veeam files into this NAS.

Out of curiosity, which technology is it, if you can say it?

[veremin]

I'm also wondering whether the solution can be configured as a VTL. If so, it might stand to reason to do that and use backup to tape job instead of backup copy one. Thanks.