I have our Veeam DB now living on a proper SQL DB server but when the backup server is busy running our full backups (synthetic fulls if it matters) the time taken to process the creation of a tape job can blow out to 3-4 hours... Refer below to see what I mean
- Code: Select all
25-03-2017 21:53:45 - ARBStartTapeBackup::FullBackup: Creating Tape Job with Name TapeJob-Week5-P2-ARBBackup-ARBTS01
26-03-2017 01:49:37 - ARBStartTapeBackup::Start-Process -FilePath SQLCmd ...
I have gone through the powershell logs and cannot see anything that would explain the delay.. I see the call being made and then it just takes hours to return. Could it be that the powershell commands are being scheduled on the backup proxy and are waiting for a 'slot' to execute?
Reason why I ask is that it works just fine when i simulate it during the day, its just when the machine is loaded up that this issue occurs.
Is there a way to 'reserve' some processing power for powershell commands as waiting 4 hours to return a command is not ideal