How to have a single job write to multiple repositories?

[MattG]

I would like a single job to write to multiple repositories for the purposes of fast restore (local disk on Veeam server) vs archival (HP StoreOnce).

This does not seem to be a builtin functionality of Veeam? If not, what are some suggested methods of accomplishing without having multiple jobs writing to different repositories.

Thanks,
-MattG

[Vitaliy S.]

Hi Matt,

You can use post backup job script (ex. rsync script) to transfer backup files to the second repository.

Please search these forums for existing topics on this theme, btw here is one of them, take a look: v6 - How to have a local and off-site backup copy?

Thanks!

[veremin]

Long story short - if you're using reversed incremental mode and willing to constantly (after each job execution) update .vbk-file on different location with the changes that have happened since the last job run, you should put into use something like RSync, that is built for block-level file synchronization.

In this case don’t forget to enable previous naming convention in order to guarantee that only block level changes will be transferred by rsync and not the backup file as a whole. It can be done by the means of the regkey mentioned in the following KB article:

http://cp.veeam.com/knowledgebase/article/KB1076/

Hope this helps.
Thanks.

[kjc3303]

Hi Vladimir, I have a question regarding the above suggestion

How does performing active full's affect the above solution? with regard to previous naming convention? ie what happened after a active full? does the active full retain the existing name?

Thanks

Kev

[Vitaliy S.]

Based on what I read from the KB article, the next active full backup file will have a timestamp in its name:

The issue is that if you ever do "Perform Full Backup" at any time, it will use the 5.x style naming and append a timestamp, rather than following the old 4.x style, even with the registry key in.

[kjc3303]

Thanks

[cpfleger]

Hi,

You could also use the Veeam Backup Cloud Edition for that - it has the feature, to replicate your existing repository (or just folders of it) not just to the cloud but also to a file system.

Regards!

[richhartdr]

Hi,

You could also use the Veeam Backup Cloud Edition for that - it has the feature, to replicate your existing repository (or just folders of it) not just to the cloud but also to a file system.

Regards!

Why would this possibly have been only in the cloud edition? I'm guessing more than a few people want this, yet do not have the pipe, have too many changes daily, or no budget for...a cloud scenario.

[cpfleger]

Well, maybe we'll see that included into BnR in future. For now that is one (very handy) of some solutions.

Regards!