Copy Job fails after i changed Storage optimazartion

[SteffenP]

Hii

I Changed the setting Storage optimazation from, LAN target to "Local target (16TB+ Backup files)" on my main job.
After i changed the settings the copy job fails.
I have started a new active full backup after i changed the settings, but it did not solve anything.

Any one who have experienced the same?


Case # 01097444

[foggy]

Active full is actually what caused the backup copy job failure, since only with new active full the new block size setting takes effect. You need to recreate a backup copy job after changing the block size, since it does not support mix of block sizes.

[SteffenP]

What about GFS policy? Do i have to maintain it manually? When i recreate a new copy job ?
Can it be true? it doesn't seems very flexible !!!!
i have over 30 Copy jobs, so it will make a lot of manual work next year!!!

[foggy]

Worth waiting for v9, where you will be able to trigger an active full for the backup copy job and avoid job re-creation with all further manual work it implies.

[SteffenP]

When is v9 comming ?
Because the copy jobs are not working at the moment, so i can't wait long...

[foggy]

Later this year. I meant not changing the block size on other jobs, if applicable.