So here is the current story.
The Sql service can't be bounced until we get a full backup first. It's just too risky
We have completed a log file backup this morning with no issues.
We are going to do a database backup tonight - however the cause of all this mess was that we added a new drive (NAS Storage) to the server to receive the DB backup files as we were out of space on the local drive.
The DB is about 900GB
My plan is to split the DB backup into 30 files - each of 30GB
I have got the plan on the attached spreadsheet.
Is there a limit on the number of backup files we can use?
Does anybody see any reason why this backup plan would not work?
We normally split the backup into files anyway and spread it over the A and B drives in the spreadsheet.
Note that the DB data files are on the drive letters f : u