Skip to main content
  • EN

We have been using Veeam for almost 2 years now.  We recently had to redo our Hardened repository due to a poor setup the first time around.  We got the repository reformatted and setup correct but now we cant do a 1:1 copy from the primary data store.  I would think that when you do the backup job and select copy the whole primary data store it would indeed do that, but Veeam support told me it will only copy day forward.

 

We are just looking to have the Hardened Repo be a 1:1 of the primary datastore.  Support told me the only way to do that is to do a file copy of each job to said repository.  This of course would duplicate anything that was already on this repo.  Is there another way to accomplish this?  Or does anyone know if there’s anything on the horizon for Veeam to make it copy 1:1 like one would think a “copy” of the main datastore would be?

As far as I know doing the File Copy is the only way to replicate things.  I am unsure if there is anything on the horizon but who knows what may come out with v13.  I highly doubt this would be a feature in this release but something I would suggest over at the forums - https://forums.veeam.com

Are you trying to move the backups off the primary repository (the poorly setup one) and onto your new hardened repository with the intention of decommissioning the primary repository?

Or are you looking to have 2 identical copies of the backups across both repositories?

Are you trying to move the backups off the primary repository (the poorly setup one) and onto your new hardened repository with the intention of decommissioning the primary repository?

Or are you looking to have 2 identical copies of the backups across both repositories?

He is looking for identical copies - 1:1 so the File Copy job is the best route to accomplish this.

Support is your “go-to” for ‘how-to’ advice within any of Veeam products. Agree here...File Copy appears to be the only way to accomplish your goal. Not a seamless task really.

The only other thing that would allow you to have an “exact” copy of every restore point would be to set up a Scale-out Backup repository with a capacity tier and the “Copy” policy selected.

However, the capacity tier can only be configured with an object storage repository.

The only other thing that would allow you to have an “exact” copy of every restore point would be to set up a Scale-out Backup repository with a capacity tier and the “Copy” policy selected.

However, the capacity tier can only be configured with an object storage repository.

Agreed here. My personal goal would be to avoid having another job to manage, I‘d let SOBR handle this.

Comment


Terms & Conditions