Testing a new backup server in parallel

[FECambot]

Hi all,

my company bought a similar one, who is closing, and we retrieved some nice assets.

I have a "new" physical backup server, with somehting like nine times the available space of my current backup server .

I would like to tweak/adjust backups on the new backup server, while not disrupting the current system.

Is there a way "not to break" CBT mechanism, even if it means doing full backup on my newer system ? which is not a issue . Will just uncheck everything CBT-related on the new server do the work ?

The vSphere is 6.5 and Veeam will be on its latest.

[david.domask]

Hi FECambot,

For the CBT element, most important part is disable Reset CBT on each Active Full backup automatically on the new VBR server. By default this option is enabled as a safety; if I remember correctly originally it was added to address a CBT corruption issue in VMWare that I believe was resolved, but it's best practice to reset CBT on fulls. (i.e., for production use, keep this option enabled) The "Important" note on that pages explains this in a little more detail.

Similarly, ensure you are NOT sharing components between backup servers, as this is unsupported and may lead to issues with operations. It is especially important that you do NOT share repositories as well, as this will likely cause issues and may result in data corruption.