locked
MOSS 2007 Backup techniques RRS feed

  • Question

  • Hi,

    I Would like to ask about the best techniques for backup a huge database

    Currently the size of my content database is 600GB, and I am taking backup directly from SQL Server. I am also taking backup of all other database like Config DB, SSP, Search database and central admin db.

    Is it enough for a restore process? In case i have to restore all my farm and site. or I have to use some other way for backup.

    Thanks

    Sunday, September 30, 2012 8:12 AM

Answers

  • Hiya,

    No that is not enough. You also need IIS backup as well as single file backup for your web app servers. Also if you have any custom developed kode, you need those DLL's as well.

    You could consider dividing your content database into chunks of 200GB instead, which might improve performance and/or ease backup operation.

    • Marked as answer by Amjad Dars Tuesday, October 2, 2012 5:15 AM
    Monday, October 1, 2012 6:16 AM
  • I agree with jesper, you should divide your content db in to 4 dbs atleast.

    Use stsadm enumsites to get the list of all site collections in your each web app and then use stsadm merge contentdatabase command to split your SC's in to different content dbs.

    Back up mode should be full...

    This will release the overhead

    For the SQL backups the recovery model should be Full in order to avoid loss of any data.

    • Marked as answer by Amjad Dars Tuesday, October 2, 2012 5:34 AM
    Monday, October 1, 2012 10:06 AM

All replies

  • Hiya,

    No that is not enough. You also need IIS backup as well as single file backup for your web app servers. Also if you have any custom developed kode, you need those DLL's as well.

    You could consider dividing your content database into chunks of 200GB instead, which might improve performance and/or ease backup operation.

    • Marked as answer by Amjad Dars Tuesday, October 2, 2012 5:15 AM
    Monday, October 1, 2012 6:16 AM
  • I agree with jesper, you should divide your content db in to 4 dbs atleast.

    Use stsadm enumsites to get the list of all site collections in your each web app and then use stsadm merge contentdatabase command to split your SC's in to different content dbs.

    Back up mode should be full...

    This will release the overhead

    For the SQL backups the recovery model should be Full in order to avoid loss of any data.

    • Marked as answer by Amjad Dars Tuesday, October 2, 2012 5:34 AM
    Monday, October 1, 2012 10:06 AM
  • Hi Jashper,

    Thanks for the reply, I will take the backup for my IIS Webs as you said to save my custom code and other related files.

    Regarding database I am planning to split it soon...

    Thanks :)

    Tuesday, October 2, 2012 5:22 AM
  • Hi,

    I already used enumsites, to check which sitecollection has more size so i can split it in a separate db, the report gave me Total 128 site collections and 2 of them are with huge size 1st with 108GB and 2nd 77GB rest of them are below 50GB, so I am planning to split those two SiteCollections into separate databases but I read somewhere on internet that if you split a SiteCollection which has bigger size then it can corrupt the data and will take much time, so wht will be the best solution in this case!

    Thanks

    Tuesday, October 2, 2012 5:33 AM
  • Please follow this link this is the best practice for this

    http://technet.microsoft.com/en-us/library/cc825323(v=office.12).aspx

    Tuesday, October 2, 2012 6:50 AM