I have two backup schedules for the "same" task
..but first, storytime...
We have a server located ±30km away with 164Gb of data (20 files @ 8Gb, rest are small ldf's) , the backup path/sequence is
Server -> Slow radio Link (20Mhz) -> network switch -> 1Gb Fibre -> 30km -> Backup Server
This often timed out (suspect radio hardware limitations), so I broke this down into two Separate Tasks
1. A pretask copy moves an incremental backup over the "slow" wireless links (now updated to 40Mhz) to a NetApp on-site 100m away.
2. Once this task completes, another task is then kicked off to do an incremental backup over the 1Gb Fibre to the main site 30km away.
So my problem is the pretask runs beautifully as seen in the first image (was a mission to get the full backup initially)
but the secondary task pulls almost a full copy every time.
The archive attributes are all cleared when needed, any ideas..?
..but first, storytime...
We have a server located ±30km away with 164Gb of data (20 files @ 8Gb, rest are small ldf's) , the backup path/sequence is
Server -> Slow radio Link (20Mhz) -> network switch -> 1Gb Fibre -> 30km -> Backup Server
This often timed out (suspect radio hardware limitations), so I broke this down into two Separate Tasks
1. A pretask copy moves an incremental backup over the "slow" wireless links (now updated to 40Mhz) to a NetApp on-site 100m away.
2. Once this task completes, another task is then kicked off to do an incremental backup over the 1Gb Fibre to the main site 30km away.
So my problem is the pretask runs beautifully as seen in the first image (was a mission to get the full backup initially)
but the secondary task pulls almost a full copy every time.
The archive attributes are all cleared when needed, any ideas..?
Statistics: Posted by Boonew — 21 May 2024, 10:47