Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
<ul><li>Data & Database Management </li></ul><ul><li>January 7 th , 2009 </li></ul>NYC SharePoint User Group Presenter: Ni...
SharePoint Training Project Server Training
Challenge: Managing Unexpected data Issues with SharePoint <ul><li>Number of SharePoint Sites </li></ul><ul><li>Size of yo...
Target Audience <ul><li>Mid-scale to large-scale SharePoint implementations </li></ul><ul><li>Business / Platform Owners <...
Agenda
Key messages to remember: <ul><ul><li>Think and plan upfront: How big could your SharePoint environment be in the next two...
Understanding your SharePoint Sites
SQL Server Configuration Deciding on the SQL Cluster Configuration Number of nodes in the Cluster Number of instances in t...
SQL Server Configuration - Example Total data size = 1 TB 2 nodes in the Cluster Number of instances in the cluster = 1 De...
Organizing Content Databases at SharePoint Level <ul><ul><li>Where is my site collection? </li></ul></ul><ul><ul><li>How m...
Organizing Content Databases at SharePoint Level <ul><li>Number of sites in a content database </li></ul><ul><li>Size of c...
Organizing Content Databases at SharePoint Level <ul><li>Collaboration Web Application: </li></ul><ul><ul><li>Target Conte...
Managing Corresponding Databases on SQL Server <ul><li>Sites increase, so does database Size </li></ul><ul><li>Too many da...
Managing Corresponding Databases on SQL Server <ul><li>Consider 1 st  Scenario in Drive Configuration: </li></ul><ul><li>@...
Managing Corresponding Databases on SQL Server <ul><li>Options: </li></ul><ul><li>1.  Add extra drives to the SQL Server <...
Managing Corresponding Databases on SQL Server <ul><li>Consider 2 nd  Scenario in Drive Configuration: </li></ul><ul><li>@...
Managing Corresponding Databases on SQL Server <ul><li>Data grows more than 1 TB: </li></ul><ul><ul><li>Add more drives to...
Managing Corresponding Databases on SQL Server <ul><li>Moving Databases across SQL Cluster: </li></ul><ul><ul><li>Perform ...
Moving Sites across Web Applications / Content Databases : STSADM Backup <ul><li>Number of site collections increase </li>...
Moving Sites across Web Applications / Content Databases : Merge Content DB <ul><li>Merge Content Database Command </li></...
Moving Sites : Batch Site Manager <ul><li>Batch Site Manager – Another option to move sites from the Central Administratio...
Moving Sites: Batch Site Manager
Moving Sites: Batch Site Manager
Moving Sites: Batch Site Manager
Special – Managing Host Header Sites <ul><li>Syntax for creating Host Header Sites:  </li></ul><ul><ul><li>Stsadm –o creat...
Special – Managing Host Header Sites, Avoiding Corruptions <ul><li>Avoiding corruption with Host Header Sites:  </li></ul>...
Key messages to remember: <ul><ul><li>Think and plan upfront: How big could your SharePoint environment be in the next two...
Questions?   Thank you & best regards Nilesh Mehta NGenious Solutions, Inc. 1075 Easton Ave.,  Tower1, Suite #6 Somerset, ...
Prochain SlideShare
Chargement dans…5
×
Prochain SlideShare
Tp Result
Suivant
Télécharger pour lire hors ligne et voir en mode plein écran

0

Partager

Télécharger pour lire hors ligne

Mehta - SharePoint Data And Database Management

Télécharger pour lire hors ligne

  • Soyez le premier à aimer ceci

Mehta - SharePoint Data And Database Management

  1. 1. <ul><li>Data & Database Management </li></ul><ul><li>January 7 th , 2009 </li></ul>NYC SharePoint User Group Presenter: Nilesh Mehta – Sr. SharePoint Architect – NGenious Solutions, Inc.
  2. 2. SharePoint Training Project Server Training
  3. 3. Challenge: Managing Unexpected data Issues with SharePoint <ul><li>Number of SharePoint Sites </li></ul><ul><li>Size of your SharePoint farm </li></ul><ul><li>SharePoint Site Backup / Restores </li></ul><ul><li>SharePoint Site Corruptions - especially with host header sites </li></ul>
  4. 4. Target Audience <ul><li>Mid-scale to large-scale SharePoint implementations </li></ul><ul><li>Business / Platform Owners </li></ul><ul><li>SharePoint Administrators </li></ul><ul><li>SharePoint Developers Need to understand Production limitations </li></ul>
  5. 5. Agenda
  6. 6. Key messages to remember: <ul><ul><li>Think and plan upfront: How big could your SharePoint environment be in the next two years? </li></ul></ul><ul><ul><li>Organize your content databases for easy management, moving and restoring sites </li></ul></ul><ul><ul><li>Prepare for potential site corruption: Don’t put too many eggs in one basket </li></ul></ul>
  7. 7. Understanding your SharePoint Sites
  8. 8. SQL Server Configuration Deciding on the SQL Cluster Configuration Number of nodes in the Cluster Number of instances in the cluster Deciding drives per instance and drive size
  9. 9. SQL Server Configuration - Example Total data size = 1 TB 2 nodes in the Cluster Number of instances in the cluster = 1 Deciding drives per instance and drive size Drives: C: = OS D: = 250 GB (Data) E: = 250 GB (Data) F: = 250 GB (Data) G: = 250 GB (Data) H: = 500 GB (Log) I: = 1 TB (Backup) Drives: C: = OS D: = 500 GB (Data) E: = 500GB (Data) F: = 500 GB (Log) G: = 1 TB (Backup) Drives: C: = OS D: = 1 TB (Data) E: = 500 GB (Log) F: = 1 TB (Backup)
  10. 10. Organizing Content Databases at SharePoint Level <ul><ul><li>Where is my site collection? </li></ul></ul><ul><ul><li>How many sites in a content database? </li></ul></ul>
  11. 11. Organizing Content Databases at SharePoint Level <ul><li>Number of sites in a content database </li></ul><ul><li>Size of content databases </li></ul><ul><li>Best Practices: </li></ul><ul><ul><li>Naming conventions for Content Database </li></ul></ul><ul><ul><li>Setting maximum site count in Content Database </li></ul></ul><ul><ul><li>Setting site quota on content database </li></ul></ul>
  12. 12. Organizing Content Databases at SharePoint Level <ul><li>Collaboration Web Application: </li></ul><ul><ul><li>Target Content DB sizes around 100 GB for easier management </li></ul></ul><ul><ul><li>@ 1 GB Quota = 100 Sites / Content DB. Lock Site Max @ 100 Sites </li></ul></ul><ul><ul><li>Custom Content Databases for larger sites above 20 GB. Lock site maximum to single site </li></ul></ul><ul><li>Assigning Site Quota </li></ul><ul><ul><li>500 Mb, 1 GB, 2GB, 5 GB or larger </li></ul></ul>
  13. 13. Managing Corresponding Databases on SQL Server <ul><li>Sites increase, so does database Size </li></ul><ul><li>Too many databases </li></ul><ul><li>Usage increases, CPU & Memory Usage increases </li></ul><ul><li>Get better performance by upgrading to 64-bit </li></ul>
  14. 14. Managing Corresponding Databases on SQL Server <ul><li>Consider 1 st Scenario in Drive Configuration: </li></ul><ul><li>@ 1 GB quota & 100 sites, you can have a maximum of two Content DB’s / Drive </li></ul><ul><li>Highly possible that some sites will need more than 1GB from these sites </li></ul>Drives: C: = OS D: = 250 GB (Data) – Collaboration Team sites E: = 250 GB (Data) – Collaboration Team sites F: = 250 GB (Data) – Portal sites G: = 250 GB (Data) – Application sites H: = 500 GB (Log) I: = 1 TB (Backup)
  15. 15. Managing Corresponding Databases on SQL Server <ul><li>Options: </li></ul><ul><li>1. Add extra drives to the SQL Server </li></ul><ul><li>2. Moving Databases between Drives: </li></ul><ul><ul><li>Detach database from SQL Server. </li></ul></ul><ul><ul><li>Move database files as necessary on the same server </li></ul></ul><ul><ul><li>Attach database back to SQL Server </li></ul></ul><ul><li>No issues from the SharePoint side. SharePoint auto-detects the databases </li></ul><ul><li>Cons: You can only add so many drives and will soon run out of drives </li></ul>
  16. 16. Managing Corresponding Databases on SQL Server <ul><li>Consider 2 nd Scenario in Drive Configuration: </li></ul><ul><li>@ 1 GB quota & 100 sites, you can have a maximum of four Content DB’s / Drive. Here you do have room to grow in some manner </li></ul><ul><li>Tape backup of these drives take more time </li></ul>Drives: C: = OS D: = 500 GB (Data) – Collaboration Team Sites E: = 500GB (Data) – Portal and Application Team Sites F: = 500 GB (Log) G: = 1 TB (Backup)
  17. 17. Managing Corresponding Databases on SQL Server <ul><li>Data grows more than 1 TB: </li></ul><ul><ul><li>Add more drives to the same cluster instance </li></ul></ul><ul><ul><li>Based on SQL Server performance, create another SQL Instance on passive node and add drives there </li></ul></ul><ul><ul><li>Create a brand new Cluster and add drives there </li></ul></ul><ul><li>Restore sites from SQL backups: </li></ul><ul><ul><li>Need space to restore SQL backups – twice the size of the database </li></ul></ul>
  18. 18. Managing Corresponding Databases on SQL Server <ul><li>Moving Databases across SQL Cluster: </li></ul><ul><ul><li>Perform full SQL Backups </li></ul></ul><ul><ul><li>Perform stsadm –o preparetomove </li></ul></ul><ul><ul><li>Perform stsadm –o detachcontentdb </li></ul></ul><ul><ul><li>Copy SQL backup files to new cluster </li></ul></ul><ul><ul><li>Attach content db’s to the new SQL Cluster </li></ul></ul><ul><ul><li>Perform stsadm –o addcontentdb </li></ul></ul>
  19. 19. Moving Sites across Web Applications / Content Databases : STSADM Backup <ul><li>Number of site collections increase </li></ul><ul><li>Site collections need more space </li></ul><ul><li>Options: </li></ul><ul><ul><li>STSADM Backup / restore – </li></ul></ul><ul><ul><ul><li>Best Solution for moving sites. </li></ul></ul></ul><ul><ul><ul><li>Create a batch file for backups, deletes and restore. </li></ul></ul></ul><ul><ul><ul><li>Dependency on local file system for backups. </li></ul></ul></ul><ul><li>NOTE: Do not delete large sites from central administration. Always use STSADM utility </li></ul>
  20. 20. Moving Sites across Web Applications / Content Databases : Merge Content DB <ul><li>Merge Content Database Command </li></ul><ul><ul><li>good option for moving large number of sites, but has issues with Multi-Valued columns . </li></ul></ul><ul><ul><li>It does not keep the values. </li></ul></ul><ul><ul><li>Does not work across SQL Instances. Can move sites only in the same SQL Server Instance. </li></ul></ul>
  21. 21. Moving Sites : Batch Site Manager <ul><li>Batch Site Manager – Another option to move sites from the Central Administration. </li></ul><ul><ul><ul><li>Pros: Allows you to select which database to restore sites in. Works across clusters </li></ul></ul></ul><ul><ul><ul><li>Cons – I have had very little success with this. Moved 5 sites and ended up with about 3 corrupt sites. Dependency on local file system disk space for backups and can cause corruption when you run out of disk space either on local server or SQL Server </li></ul></ul></ul>
  22. 22. Moving Sites: Batch Site Manager
  23. 23. Moving Sites: Batch Site Manager
  24. 24. Moving Sites: Batch Site Manager
  25. 25. Special – Managing Host Header Sites <ul><li>Syntax for creating Host Header Sites: </li></ul><ul><ul><li>Stsadm –o createsite –url http://abc.mycompany.com –ownerlogin –owneremail –sitetemplate –hhurl </li></ul></ul><ul><li>Possible corruption caused when moving host header sites from development to staging to production </li></ul><ul><li>Example: </li></ul><ul><ul><li>Host Header Site in Development: http://devabc.mycompany.com </li></ul></ul><ul><ul><li>Restore site in QA as http://qaabc.mycompany.com (Database keeps reference to devabc.mycompany.com) </li></ul></ul><ul><ul><li>Restore site in Production as http://abc.mycompany.com (Database keeps reference to http://devabc.mycompany.com ) </li></ul></ul><ul><ul><li>Imagine creating multiple sites based on same backup because you want to keep template. They all will have reference to http://devabc.mycompany.com </li></ul></ul><ul><ul><li>When you perform content database detach / attach , configuration database does not know which site was which because they all have same Host Header column value </li></ul></ul>
  26. 26. Special – Managing Host Header Sites, Avoiding Corruptions <ul><li>Avoiding corruption with Host Header Sites: </li></ul><ul><ul><li>When you restore site from Development to QA or Prod, restore with the same URL http://devabc.mycompany.com </li></ul></ul><ul><ul><li>Once restored, perform stsadm –o renamesite command on this URL and it modifies the host header information in database properly </li></ul></ul><ul><ul><li>Perform similar action if you have multiple sites coming in from same template </li></ul></ul>
  27. 27. Key messages to remember: <ul><ul><li>Think and plan upfront: How big could your SharePoint environment be in the next two years? </li></ul></ul><ul><ul><li>Organize your content databases for easy moving, management and restoring </li></ul></ul><ul><ul><li>Prepare for potential site corruption: Don’t put too many eggs in one basket </li></ul></ul>
  28. 28. Questions?   Thank you & best regards Nilesh Mehta NGenious Solutions, Inc. 1075 Easton Ave., Tower1, Suite #6 Somerset, NJ 08873 Ph: (732) 873-3385 Cell: (201) 230-7922 Fax: (413) 803-8749 E-mail: [email_address] URL: www.ngenioussolutions.com  

Vues

Nombre de vues

1 586

Sur Slideshare

0

À partir des intégrations

0

Nombre d'intégrations

18

Actions

Téléchargements

2

Partages

0

Commentaires

0

Mentions J'aime

0

×