michelandre
"To workaround set timeout to 23 hrs, this allows the backup to timeout cleanly, it will restart and attempt to complete the first full backup on the next run."
I don't quite understand "on the next run".
It means on the next automatic scheduled run, as set in server manager panel.
ie if backup is set to "run" (or perform the backup) at 2 am, then it will time out at approx 1 am the next day. Then at 2am a scheduled backup will commence. The system sees that an interrupted backup exists & will recommence the original backup, from the point it was up to, until it finishes.
It may take 2 or 3 days even until it is finished.
With that amount of data, you really should backup to a USB drive attached to the server.
Backing up across a network to a workstation has many "bottlenecks" which can collectively cause a backup to take an excessively long time to complete.
Also for practical reasons you should do one full backup & then daily incrementals. The first backup may take a while but subsequent backups should be much faster depending how much data changes on the server each day.
I do not want to try anything until certain as this server is very critical.
If it is very critical, then for sure I would stop playing around with backup to workstation (which can be very unreliable due to other network issues etc), and connect a 2Tb USB drive to the server & start backing up to that. Swap the disk nightly too, if it is that critical.
There is more to say on this if you are interested.
I can not add another disk on the server for backing up to local.....
Why not ?
.... and then scp to workstation.
Why would you even think about scp'ing 1.2Tb of data across the network, it will take a long time.