I had some folks return to the office recently, from a Sharepoint meetings of sorts. A message I received was:
"Speaker just talked about moving all of their file shares to SP. Eric mentioned that our file shares were 6tb and asked how their sql guy felt about that. Response was that their sql guy originally balked but was reminded that sql was geared for this. It can handle it and it will happen. Eric and I immediately thought of you. :) "
I should say I'm the SQL guy around here, but have dealt with what I consider 'relatively small' databases, and I'm the SQL guy because I'm the person most willing to look at it. I don't consider myself a 'real dba'.
All my SQL backups are to disk, and the backup program on the servers pick up the SQL backup files and write them to tape. When I need to perform a restore, often I have the most recent backup or two still on disk, but even if I don't, I can restore from tape back to disk - and perform a SQL restore to put the database back. In the past, when someone has lost a file in Sharepoint, and I have to pull back an old copy of the database -- I can restore the database to a different name, and using a vb script, pull out the file the end user needs restored. (With some databases, I have transaction log backups to work with as well, but all the Sharepoint DBs are in Simple restore mode.)
Working with 11 GB database files, that means I have 11 GB once for the database, plus a little for a transaction log. I have 11 GB for the latest backup. If I need to do a restore, I have 11 GB for the restored database backup file, plus ANOTHER 11 GB for a second copy of the database running. Working with 11 GB files, it's at least doable. If someone seriously proposes working with 6 TB Sharepoint DB files, I'm going to experience push back from the financial folks if I ask for 24 TB of drive space. (And I could bring it down to 18 TB by keeping only one backup file online for any purpose, and if I use backup compression, I might get it down to 15 TB... but that's still pretty significant to replace a 6 TB file share.)
I've done a little poking about, and I see a best practice of using differential backups to speed up the backups, and working with dbs that big, I suspect that'll be necessary, but that compounds my space problem if I ever need to perform a restore.
So now to the questions:
Are there other technologies I'm missing that solve this problem? (And if they are things like DPM 2010... are they THE solution? because I'd be giving up TSM backup to a very large tape library system.)
I'm not a Sharepoint person... but I know there is some versioning in Sharepoint... is the standard answer, "No, you can't HAVE an older copy restored?" Or are people using 6 TB Sharepoint installations just living without backups?