1 / 34

SharePoint Backup

AG204. SharePoint Backup. Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation. We Don't Back SharePoint Up. Why don’t we back SharePoint up? When we do back it up, we don’t do it right. Why should we back SharePoint up?. Document Versioning.

gautier
Download Presentation

SharePoint Backup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. AG204 SharePoint Backup Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation

  2. We Don't Back SharePoint Up • Why don’t we back SharePoint up? • When we do back it up, we don’t do it right. • Why should we back SharePoint up?

  3. Document Versioning • Versioning for SharePoint allows you to keep copies of past instances of documents. • Versioning is a great way to revert to previous incarnations of a document!

  4. Recycle: Environmentally Good! • SharePoint’s granularity of backup is due to the dual Recycle Bin functionality! • Administrators can restore deleted items for users using Recycle Bins.

  5. Recycle Bin Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  6. No Automated Site Backup? • Microsoft IT Site Delete Capture Feature 1.0 • Backup deleted Sites automatically!

  7. IT Site Delete Capture Feature Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  8. Command-Line Truths • Site Delete exploits our command-line functionality! • We actually do three types of command-line backup.

  9. Export • For Sites and Subsites! • Not full-fidelity!

  10. Export Sample Code (zzz) • This code example will be used to export a sub-site in our site collection. • stsadm –o export –urlhttp://servername/site/subsite -filename subsite_backup.bak • Other examples of switches include: • -overwrite, -quiet, -versions <1-4>, -includeusersecurity, -cabsize <integer value>

  11. Export Demo Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  12. Backup (Duh) • Command-line backup for a site-collection. • And only for a site collection! No sub-sites! • This backup is full-fidelity!

  13. Backup Sample Code (zzz) • This code example will be used to backup a site collection in a SharerPoint database. • stsadm –o backup –url http://servername/sitecollection -filename sitecollection_backup.bak [-overwrite] • The –overwrite switch is optional. It allows you to overwrite a previous backup of the same name in the same file path.

  14. Backup Demo Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  15. Central Administration Backup • We also offer a GUI backup option. • This allows for full or differential backups of SharePoint!

  16. Central Admin Backup Demo Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  17. Catastrophic Backup (Eeep!) • The action taking place in the GUI can also occur in the command-line! • This can then be scripted and automated.

  18. Backup Sample Code (zzz) • This code example will be used to perform a catastrophic backup of a site collection in a SharerPoint database. • stsadm –o backup –directory <UNC path/local drive> -backupmethod <full/differential> [-item] <created path from tree> [-percentage] <integer, 1-100> [-backupthreads] <integer, 1-10> [-showtree] [-quiet]

  19. SharePoint Designer • SharePoint Designer lets us do backups. • We can backup sites and sub-sites with Designer.

  20. Designer Demo Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  21. SQL Database Backups • Fundamental to most backup plans! • This should be a collaboration between SharePoint and your SQL DBAs.

  22. OSQL Backup Commands • C:\>osql –E1> USE SharePoint1_Content2> go1> BACKUP DATABASE SharePoint1_Content2> TO DISK = 'C:\BACKUP\SharePoint1_Content.bak'3> go1> exit

  23. OSQL Demo Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  24. Clusters and Mirrors – Backups? • Both Database Clusters and Database Mirroring offer a high-availability failover option for SharePoint. • Do not treat either as a ‘backup’ strategy!

  25. Is Everything I Need In SQL? • Not if you’ve customized SharePoint! • Document all changes with a Master List!!! • Maintain your list with Change Control!

  26. IIS Is Where We Live • IIS Metabase backups should be taken too. • Backup the web.config, even with an IIS Metabase backup!

  27. This Is Hard… • You can backup your whole server, but that can be a little large for what you need. • You can try a third-party backup, if you’re ready for the consequences.

  28. Data Protection Manager • Now this is an excellent backup strategy! • DPM allows you to make detailed backup plans for your total SharePoint environment.

  29. Data Protection Manager Demo Heidi Payne & Ryan Pillatzki Technical Lead & Support Engineer Microsoft Corporation demo

  30. Summary • Backup daily! Backup in multiple ways (redundancy is your friend)! • What do I do with my backups? Stick around for Restore, in just a few minutes!

  31. Post Event DVD brought to you courtesy of:

  32. SUBMIT AN EVALUATION For a chance to win an 8GB ZUNE! Submit evaluations on MySPC www.MicrosoftSharePointConference.com

  33. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related