SharePoint Storage Optimization

613
-1

Published on

Optimización del Almacenamiento en SharePoint

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
613
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • There are several things you need to take into consideration when planning for how much storage you will need to allocate to SharePoint content.
  • There are a few basic ways to manage storage growth in SharePoint. First things first, set site quotas and alerts, we always recommend a 10 GB limit and 8 GB alert. This is going to let you stay on top of which sites are growing more quickly so you can plan future structure accordingly. Next is to monitor growth trends. Pay attention to how quickly your sites are growing, and then don’t forget to monitor the overall Content DB size. Finally, depending on growth, there’s a very good chance you’ll need to split content DB’s if they get too big. Now, what is “too big”? We’ll get to that in a minute, as there are several recommendations based on your concerns… First though, we’ll look at a couple of ways to control growth of content DBs…
  • Here’s a look at a very basic SharePoint architecture. Here we have the front end with the object model, and the SharePoint content (blobs and metadata) are stored in SQL.
  • This diagram maps out data growth over a period of time in a collaboration environment:Electronic data will continue to grow year over yearInactive data growth outpaces growth of active, operational dataHowever, most of the data is actually inactive or stale data, which is the area in between the two linesIn SharePointConsider your work on a design documentThrough drafts and edits, multiple versions are being created. Ex. Up to 32 versions of a document, if each document is 2.5 MB, full version history takes up 80MB.When document is approved, initial 30 versions no longer needed and can be archived awayConsider project sitesProject sites bring groups of people together to work on related documents, task lists, discussions, etc.Within each org, there could be hundreds of projects that get completed each year. But entire project sites still reside on SharePointAs inactive data continue to grow, resources required for current active data is saturated by inactive data. Users experience diminishing service levels (i.e. performance degradation)Additional hardware, servers, processing power may be needed, As databases continue to grow, this would also impact the current SLA’s for backup and recovery windows that are currently in place.
  • To optimize storage, we can essentially look at two major concepts. We already discussed earlier how BLOB’s don’t contribute to SQL queries, so essentially there’s no need to keep them in the database. So the first option is to move the BLOBs out of the database. The way to do this is to leverage Blob Services APIs. The second option is to Archive content, which currently there are no native tools for, so you’d have to look at a 3rd party.
  • So if we leverage EBS… this is how the SharePoint architecture would change. The provider sits with the SP object model, and gives SharePoint tokens or stubs so it knows how to retrieve the content and maintains the context of the content. The metadata is stored in SQL, BLOBs go to a storage location of your choosing. This is completely transparent to the end user.
  • However, there are some things to note about EBS. As it is implemented by SharePoint, there’s only 1 provider allowed per SharePoint farm. There’s a chance that you could run into orphaned BLOBs, and then there are also compliance concerns.
  • So now let’s take a look at RBS… As RBS is SQL specific, it can be used across applications that leverage SQL, not just SharePoint, so this gives you more of an enterprise-wide storage architecture versus EBS, and here’s how enabling an RBS provider would affect your SharePoint storage architecture. You can have an RBS provider per database. No context, no ability to manage the object
  • Natively with SharePoint 2010, MSFT offers a RBS provider, FILESTREAM. However, it does not recommend using this with very large databases in production. To leverage this feature, you’d have to 1, 2, 3, and then 4, so you would need admin privileges on SQL and Windows server. STORAGE LOCATION IS FILE SYSTEM ONLY!!
  • As with EBS, there are some things to note with RBS… one of the main benefits is the ability to mange RBS viaPowershell, which MSFT is highly encouraging the use of over STSADM, as I believe they’re eventually doing away with STSADM.
  • So again, looking that the two blob services available, which is better, with EBS we have tighter application integration, allowing for more rules and settings to determine which BLOBs are offloaded, and then you have RBS…
  • Which is simpler, and allows for a more unified storage architecture across applications, it’s not SharePoint specifid….
  • So once we leverage Blob Services APIs to offload BLOB out of SQL, these are the impacts that we’ll see relative to our previous concerns regarding Backup and Recovery, Performance, and Storage.
  • Now we come to Connecting…
  • SharePoint Storage Optimization

    1. 1. Optimización del Almacenamiento<br />Roberto Vázquez Delgado<br />EMEA Systems Engineer<br />
    2. 2. Agenda<br />Herramientasnativas SharePoint 2010 Problemas de almacenamiento<br />EBS vs RBS<br />MigrarvsConectar<br />Connector<br />Storage Optimization<br />Insert / Header & Footer to change<br />2<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />2<br />
    3. 3. Planificaciónpara el Almacenamiento en SharePoint<br /><ul><li>Papelera de Reciclaje
    4. 4. Control de Versiones
    5. 5. Información de búsqueda e indexado
    6. 6. Crecimiento</li></ul>Como reglaprácticapara la planificacióninicial: 3.5 x el sistema de archivos<br />Optimización del Almacenamiento<br />3<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    7. 7. Métodosbásicosparaadministración del almacenamiento<br /><ul><li>Establececuotas y alertas!</li></ul>10 GB cuota, 8 GB alerta<br /><ul><li>Controlalastendencias de crecimiento</li></ul>- Sitios: despaciodurante el tiempo o rápidoincremento en tamaño?<br />- Tamaño de las BBDD de Contenido<br /><ul><li> Divide las BBDD de Contenidosi son muygrandes”</li></ul>Optimización del Almacenamiento<br />4<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    8. 8. BLOBs-- ¿Cuáles el problema?<br /><ul><li> BLOBs = Binary Large Objects
    9. 9. Contenido SharePoint = BLOB + Metadata
    10. 10. BBDD Contenido = BBDD de … BLOBs + Metadata
    11. 11. BBDD SQL necesita altos IOPS (input/output operations per second) y bajalatencia
    12. 12. Altos IOPS + almacenamiento de bajalatencia = €€€€
    13. 13. Los BLOBs no participan en lasoperaciones de consulta, por lo que no tienesentido el tenerBLOBs en una BBDD
    14. 14. BBDDllena de BLOBs = €€€€ perdidos  </li></ul>Optimización del Almacenamiento<br />5<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    15. 15. Almacenamiento en SharePoint pordefecto<br />SharePoint WFE<br />SharePoint Object Model<br />BLOBs &<br /> Metadata<br />SQL Server<br />Content DB<br />Config DB<br />Storage Optimization<br />6<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    16. 16. Implicaciones del tamaño de la Base de Datos<br />Los BLOBs incrementan el tamaño de la BBDD, creandoproblemas con:<br /><ul><li>Operaciones de Backup & Recovery
    17. 17. Rendimiento
    18. 18. Costes de Almacenamiento</li></ul>Optimización del Almacenamiento<br />7<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    19. 19. Utilización de datos en Entornos de Colaboración<br />Incremento de los datosinactivos en % a lo largo del tiempo<br />Datos en SQL<br />Tiempo en años<br /><ul><li>Sitiosinactivos, documentos, listas, ocupanalmacenamiento en SQL , dificultando el rendimiento</li></ul>8<br />
    20. 20. Métodos de Optimización del Almacenamiento en SharePoint<br /><ul><li>Mover los BLOBs fuera de la Base de Datos
    21. 21. Archivar el contenido
    22. 22. Bloquear la subida de BLOBs</li></ul>Optimización del Almacenamiento<br />9<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    23. 23. Extending<br />Moviendo los BLOBs fuera de la BBDD<br />Storage Optimization<br />10<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    24. 24. APIs disponibles<br />SharePoint External BLOB <br />Service (EBS)<br />SQL Remote BLOB Service (RBS)<br />Storage Optimization<br />11<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    25. 25. Vista general EBS/RBS<br />Servicios Blob quecambian la ubicación del almacenamiento<br /><ul><li>EBS = External BLOB Service
    26. 26. SharePoint 2007 SP1+ API
    27. 27. RBS = Remote BLOB Service
    28. 28. SQL Server 2008R2 Feature Pack API, con soporte SharePoint 2010
    29. 29. Ámbos son especificaciones de la interfaz
    30. 30. Necesitan de un proveedorparapoderfuncionar
    31. 31. Imposibletenerámbosproveedores</li></ul>Storage Optimization<br />12<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    32. 32. EBS<br /><ul><li>API disponible en SharePoint 2007 SP1
    33. 33. El proveedor EBS puedetomarposesión del BLOB
    34. 34. El proveedorproporciona a SharePoint un testigo o stub paraque SharePoint sepacómoobtener el objeto
    35. 35. Transparentepara el usuario final </li></ul>SharePoint WFE<br />SharePoint Object Model<br />BLOB<br />SQL Server<br />BLOB Store<br />Metadata<br />Content DB<br />Config DB<br />EBS Provider<br />Storage Optimization<br />13<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    36. 36. EBS<br /><ul><li>Implementadopor SharePoint
    37. 37. Solo 1 proveedor EBS porgranja de SharePoint
    38. 38. BLOBs huérfanos- no existe un métododirectoque compare el almacén de BLOBs y la BBDD de Contenido
    39. 39. Cumplimiento legal- ¿Quépasasi no quieropermitir a SharePoint eliminar el objeto?</li></ul>Storage Optimization<br />14<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    40. 40. RBS<br />SharePoint WFE<br /><ul><li> API disponible en SQL 2008R2 Feature Pack
    41. 41. No esexclusivo de SharePoint, disponible a cualquieraplicación
    42. 42. Cadaproveedorpuede ser asociado con cada base de datos</li></ul>SharePoint Object Model<br />BLOB &<br /> Metadata<br />SQL Server<br />Relational Access<br />Metadata<br />BLOB<br />RBS Client Library<br />Provider Library X<br />Provider Library Y<br />Content DB<br />X<br />Content DB<br />Y<br />BLOB Store<br />BLOB Store<br />Storage Optimization<br />15<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    43. 43. RBS: SQL Server 2008 Feature Pack API<br />Se maneja de forma nativadesde la BBDD = transactional<br /><ul><li>Proveedorpordefecto: FILESTREAM</li></ul>Habilita el proveedor FILESTREAM en SQL<br />Provisiona el almacén de datos y configura la ubicación del almacenamiento<br />Instala RBS en todos los servidoresSP Web y de Aplicación.<br />Habilita RBS<br />Storage Optimization<br />16<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    44. 44. RBS<br /><ul><li>Implementadopor SQL
    45. 45. Sólo 1 proveedor RBS por BBDD de Contenido
    46. 46. Los BLOBs huérfanos no suponen un problema
    47. 47. Puedebloquearoperaciones,desde un punto de vista del almacenamiento
    48. 48. Puede ser administradovíaPowershell</li></ul>Storage Optimization<br />17<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    49. 49. EBS versus RBS, ¿cuálesmejor?<br />EBS<br />Mejorintegración con lasaplicaciones, permitemásreglas y configuraciones<br />Storage Optimization<br />18<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    50. 50. EBS versus RBS, ¿cuálesmejor?<br />RBS<br />EBS<br />Más simple, permiteunaarquitecturamásunificada entre diferentesaplicaciones<br />Mejorintegración con lasaplicaciones, permitemásreglas y configuraciones<br />http://www.codeplex.com/sqlrbs<br />Storage Optimization<br />19<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    51. 51. 2 métodos, mismoresultado<br /><ul><li>Operaciones de Backup & Recovery</li></ul>Bases de Datos son un 60-80% máspequeñas<br />Necesidad de un métodopararealizar el backup de los BLOBs de forma sincronizada<br /><ul><li>Rendimiento</li></ul>Bases de Datos son un 60-80% máspequeñas<br />Cuantomásgrande sea el tamaño del archivo/BLOB, mejorrendimiento. SegúnMicrosoft :<br /><256kb, mejor en SQL<br />Entre 256kb y 1mb, SQL y sistema de archivosporigual<br />>1mb, mejor en el sistema de archivos<br /><ul><li>Costes de almacenamiento</li></ul>Almacenamiento no tan caro<br />Archivadotodavíanecesariopara un verdaderoahorro<br />Storage Optimization<br />20<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    52. 52. Herramientas de AvePoint<br />DocAve Connector<br /><ul><li>Tomacontenidoexistente en almacenamientoexterno y lo haceaccesible en SharePoint
    53. 53. El BCS es a bases de datosexternascomo Connector es a almacenamientoexterno de archivos
    54. 54. Seimplementa gracias a un tipo especial de Bibliotecas de Documentos</li></ul>-File System Document Library<br />-Media Library<br />Storage Optimization<br />21<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    55. 55. Connecting<br />La mejormanera de anticiparse al problema de los BLOBs<br />
    56. 56. Acceso a los datos y <br />Optimización del Almacenamiento<br />DocAve Connector<br /><ul><li>Acceso a la informaciónexistente en los sistemas de archivos (sin la necesidad de migrar a SharePoint/SQL)
    57. 57. Manteniendo SharePoint comosucapa de presentaciónpara los sistemas de archivosexistentes:
    58. 58. Unidadescompartidas, servicios en la nube,sistemas ECM, etc.
    59. 59. Funcionamiento con SharePoint workflows, alertas, aplicaciones Office, aplicaciones de terceros etc.</li></ul>Storage Optimization<br />23<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    60. 60. DocAve Connectors<br />1) Creamosuna Content Library<br />2) Cargamos la metadata del origen<br />Stub<br />Diseñador de sitios<br />BBDD<br />3) Cuando los usuariosacceden a la información, estransparentementecargadadesde el origen. Los cambiosseránguardadosdirectamente al disco.<br />2) Connectamos y sincr. con el contenido del origen<br />Almacenam. en la nube<br />WebFront-end<br />Almacenamiento de disco<br />Usuarios<br />Storage Optimization<br />24<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    61. 61. Migrating vs. Connecting<br />Migrator<br />Connector<br /><ul><li>InformacióndisponibleA TRAVÉS de SharePoint
    62. 62. La información se queda elsistema de orígen
    63. 63. Se daunasegundavida al sistemanativoincrementandosu valor
    64. 64. La carga del almacenamiento la maneja el sistemanativo
    65. 65. Los cambios se propagan al origen
    66. 66. Conectar y listo!
    67. 67. InformacióndisponibleEN SharePoint
    68. 68. La información se muevedentro de SharePoint
    69. 69. SharePoint reemplaza el sistemanativo
    70. 70. La carga del almacenamientola manejaSharePoint
    71. 71. Los cambios se guardan en SharePoint
    72. 72. Migrar y deshacerse del sistemaantiguo</li></ul>Storage Optimization<br />25<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />
    73. 73. ¡Gracias!<br />Q&A<br />roberto.delgado@avepoint.com<br />Storage Optimization<br />26<br />© 2010 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system,<br />or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.<br />

    ×