• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 463
  • Last Modified:

Full SQL backup - how many files

Hi Guys,

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

thanks
EE-Backup-Plan.xlsx
0
smythsit
Asked:
smythsit
  • 2
1 Solution
 
EvilPostItCommented:
The maximum i believe is 64 therefore i see no problem with you backing up to 32. This is a very good idea to speed up the backup process. Although you are using SQL Server 2008 which means you can also use backup compression which will also speed up the backup time and reduce the footprint.
0
 
EvilPostItCommented:
Sorry was out at lunch and have just read the latest comment on the last thread. Is the unkillable backup command still running? If so you will not be able to do another backup as it will be blocked by the previous backup database command (As you mentioned, last nights backup failed too).

Normally this wouldnt be a problem due to the fact that you have taken a transaction log backup and would therefore just be able to restore the log backup (and a few extra steps the if you need just let me know).

The problem you may have is that you dont know if all of the transactions have actually been backed up by the log backup.
0
 
smythsitAuthor Commented:
Hi

I think we've found the answer to both issues
http://connect.microsoft.com/SQLServer/feedback/details/428738/nativebackup-spid-get-in-to-suspended-mode-with-backupio-and-backupthread-as-last-wait-type-when-backup-process-get-intrrupted-in-sql-server-2008-rtm

It appears that the DB backup was caused by the above.
The Transaction is closed so a server restart will not cause a lengthy roll forward.

Thanks for all the help - we'll still do the file splitting once the DB is back up and running ok again
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now