SQL backups to share

[web4fun]

SCENARIO:

One of our administrators has setup a 500GB share on a server that is running SQL Server 2005. He has been backing up not only the local server dbs but also has setup a myriad of other servers to backup to this share as well which of course is not uncommon to do with servers that are short on disk space. The issue is that now he's requested another 500GB on this same server for even more additional backups from other servers. Aside from the obvious reasons; i.e. disk I/O and tape backup windows, and single point of failure(disk) I would think that this is not a good long term solution. I would think you'd want to spread out where backups are stored. I understand it may be easier to manage but at some point I would think that it would begin to become unmanageable? Does anyone have any input/suggestions/best practices? Thanks in advance.

 

[JayKusch]

Actaully his plan is quite common and used frequently.

It is better of course to spool all of your SQL backups to a remote server/location in order not to loose the backups if the server went DOA.

It is also easier to manage, as you made mention, not only in the backup process but in the restore process.

Having one location where the backups are held helps in recovering the file quicker knowing where they are located as oppose to needing to find out what server/location has the backup you need to restore.

As long as the disc to tape process (and the more up to date method of disc to disc backups and/or mirroring) you are better off with a single location.

But that is just my opinion as a DBA - lol.

Thanks

J. Kusch

 

[web4fun]

Thanks Jay. It's just an awful lot of data on one server and the tape backup window would just not be large enough to complete every night...not to mention FULL backups would take a couple of days. What you said makes perfect sense but I believe that because this server is a QA / Certification SQL server with high disk I/O combined with the shrinking backup window, just don't think it's feasible. If we were to let's say create a CIFS share and have everything backing up to it, then to tape, then I wouldn't be as concerned, but obviously this is a heavily used DEV SQL Server with a bunch of disk space. Thanks for you input.

 

[JayKusch]

Absolutely correct. A dedicated storage area/server is what is needed.

Thanks

J. Kusch

 

[web4fun]

Great thanks Jay. Just wanted to get an idea of what other DBAs are doing with regards to this topic.