Disable Compacting Backup File?

[mrholm]

Hi
Backup Copy is done to StoreOnce catalyst and when Full backup file merge is run we see that "compacting full backup file" takes very long time even on not so big .vbk files.
Is there any chance to disable this since I don't see any reason why this is needed on Catalyst storage?
This is not "Full backup file maintenance" since this is not set.

//mats

[DGrinev]

Hi Mats,

The behavior you see is expected. This is the part of the GFS retention mechanism, when the VMs data flow from the full backup to the newly one created by GFS and yes it usually takes time.
The reason could be a VM retained in the backup, it had been backing up for some time, but then it was removed from the processing. Thanks!

[mrholm]

Thanks, Yes we had 3 old servers not being bacuped anymore and after we removed those restore points it all went fine. Why is this creating a pronlem like this? How to handle this in the future since there wil lbe scenarions where a server need to be retained as a GFS copy but not being backuped anymore and we don't want to remove the GFS copy?

[DGrinev]

It's by design and cannot be avoided other than removing those VMs from the processing. Thanks!

[foggy]

You can also enable deleted VMs retention and these VMs should be deleted automatically according to it.

[mrholm]

But in our case we have several VM backuped and copied, then when a VM change ID and cretaes a new chain the copy jobs starts to compact old files after a while. The only way to comes around this is to dlete those GFS copies? Not so good if can't keep older copies of servers that doesn't exists anymore.

[foggy]

You shouldn't delete restore points. This operation shouldn't occur after deleted VMs retention applies. Old restore points will still exist in GFS files.

[mrholm]

Thanks foggy, I have a case to support around this to make sure we cofigure everything correctly

[foggy]

Right step, indeed. Could you please share the case ID for future reference?

[mrholm]

Absolutly, 03197859