COPY Backup - Source job importance?

[EddyMandemaker]

Hello,
Does it matter for a COPY BACKUP what the source backup job is (a incremental / reversed incremental job) or not ?
If yes, is there a Best Practice ?
Regards

[Shestakov]

Hello Eddy,
Backup copy jobs support both forward(including forever incremental) and reversed incremental as a source.
However seeding is possible for forward incremental backup chains only.
Could you explain your use case? Have you considered using Forever Forward Incremental Backup method?
Thanks!

[EddyMandemaker]

Hello,

Probably I misunderstood the manual Seeding procedure.
My original backup is reverse incremental, and used a copy backup (local) to seed a WAN repository manually (via USB disk)
The problem is the first run copy job takes very long time when using the remote repository (whichj i seeded via USB disk) and mostly does not complete in 24 hours..

So? Can i change the backup job to Incremental and will the copy backup work after this ? or do I need to redo the seed?

Regards

[EddyMandemaker]

Hello,

I have a FULL COPY backup at the remote site!

Regards

[Shestakov]

Eddy,
Did you do all steps just like it described in the provided KB?
I`m just trying to figure out if the seeding actually worked well. Do you use WAN Acceleration for your backup copy jobs?
Note that if you use our WAN Acceleration it will have to sync a disk catalog from the source Wan Accelerator to the target Wan Accelerator. You will notice that the job will run longer on its first Sync. Direct mode, does not experience this delay.

Can i change the backup job to Incremental and will the copy backup work after this ?

Yes, it will work. Backup copy job itself is always forward incremental.
Thanks.