1M to 4M conversion

[efd121]

I’m in the process of converting my backup jobs from the default 1M block size to 4M.
My question is if I create a new backup job that is set to 4M then move a VM from a job that is currently set at 1M to this new job will it inherit the 4M and run an Active Full the next time the job runs or will I need to manually run an AF for that VM?
Dave

[Gostev]

We do not recommend 4MB blocks because they double backup storage requirements vs. 1MB blocks.
Do you really want to pay for 2x backup storage going forward? It's a big difference.

You will need to manually run AF. It might be easier to schedule one for the entire job?

[efd121]

I would not be considering 4M if it wasn't for a performance issue with my on premise S3 immutable appliance.

Thanks for confirming that it might be easier to make the switch for the entire job. This is going to take several weeks, I have over 200 jobs and almost 1,500 VMs that are backed up daily and I will have to manage the free space on the performance tier as the backup chains are rebuilt.

Dave

[Gostev]

So you're ready to pay your storage vendor for 2x more storage in the long run than what would be needed with alternative on premise S3 immutable appliances? Or is this just a temporary solution for you? Sorry, just curious what is your thinking here.

[efd121]

Unfortunately, I’m in a tight spot where I don’t have a choice now. I informed my management that this change would result in purchasing additional performance tier capacity and will have an impact on recovery speeds. I’m not convinced the 4M switch and code update I’m expecting in the next couple of weeks will be enough to resolve the slowness but it’s a process I have to go through before I can consider sending the system back for a full refund.

[Gostev]

Thank you for these details, it makes sense!