• Save
SharePoint Storage Optimization
Upcoming SlideShare
Loading in...5
×
 

SharePoint Storage Optimization

on

  • 816 views

Optimización del Almacenamiento en SharePoint

Optimización del Almacenamiento en SharePoint

Statistics

Views

Total Views
816
Views on SlideShare
812
Embed Views
4

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 4

http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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 SharePoint Storage Optimization Presentation Transcript

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