Copy per-VM to not per-VM

[Drakko]

Hello,

I have a main Job to a repository with per-VM option selected.

I have a Job Copy (from main) to a repository without per-VM option selected.

But on the second repository, backup are still divided per VM.

A copy job can't aglomerate a main backup ?

Regards

[Vitaliy S.]

Hi Philippe,

Are you using a backup copy job or just a file copy?

Thanks!

[Drakko]

Hello,

that's backup copy job.

But I removed per-VM option few days ago. Maybe I have to restart a full sync to make change applyed?

Thanks

[Vitaliy S.]

Yes, active full is required here to apply new settings.

[Drakko]

Great !
'working
Thx Vitaliy

[Drakko]

Oh!

I'va got an other problem.

The job is set to keep 40 restore points.

After I disable per-VM option, the job is adding restore point.

So after 2 runs, I have 42 points… Old backups are not removed :'(

I suppose that is not normal.

Regards

[DGrinev]

Hi Drakko,

Is it forever forward incremental backup chain? Thanks!

[Drakko]

Thanks!
It is a copy job so this option does not exist.
The main job is incremental.
Before removing "per-VM" option, the number of restore point was good.
I changer nothing else.

[Vitaliy S.]

Philippe,

Your old backup chain will be deleted as soon as the new one reaches the configured retention policy (40 restore points). Right now the backup server cannot delete your oldest file which is VBK (1st one) as subsequent incremental files will be invalid after that. You can either wait till 40 restore points are created, or lower the retention policy to delete the old backup chain to free up some space. It's up to you and your backup policy.

Thanks!