I´m trying to wrap my head around the backup copy job and how it is designed. I did not find a specific answer to that (maybe bad google skills )
On the initial first Copy Job you merge the Full Backup + increments from the source side and write it as a full backup to the target side.
Due to this i "loose" all my restore points on the target side.
Shouldn´t this be the reason why i use a copy job, to have a second identical copy of my backup on a different repository?
I want to understand why it is designed that way.
My point was that you create a full for the first run of the backup copy job.
Let´s say i have a source repo with a retention policy of 60 days.
Now i create a new backup copy job to copy my backups to a secondary repo.
Due to the initial creation of a full backup i will loose my retention points on the secondary repo.
Speaking about initial sync of backup copy job, it's expected that during first run only the most recent state is copied to target location.
Due to the initial creation of a full backup i will loose my retention points on the secondary repo.
You won't loose it, you will still have it on primary repository, and backup copy job will eventually catch up, as backup job will be creating new restore points. This is actually a good reason to implement the layered backup protection from the beginning and take care about both primary and secondary backup copies.
)