A customer wants to move (well, copy) their backups from a hardened linux repository to a new S3 platform. I hoped I could just do "Move backup" on the backup chain, and continue the old jobs, but then VBR complains that the job has synthetic fulls which can't be done on object. All right, but I can't uncheck the synthetic fulls because the current repository is immutable. Is there a way around this or will I have to create new jobs, letting the old backups age out?
Statistics: Posted by DanielJ — Sep 09, 2025 1:13 pm
