none
DPM NTFS Volumes Concern RRS feed

  • Question

  • Hello,

    When I go to my Computer Management -> Disk Management. I see the following picture

     


     

    there are too many Dynamic NTFS volumes here. Myquestion is that is there a limit on the dynamic volumes? could it be that someone adds a new content database to my sharepoint environment and DPM fails because it cannot create new volume?

    I have plenty of space on my disk though. I have 15 TB of space which is way higher than what should be required for all databases along with 30 days snapshot.

    So my concern is not disk space ... my concern is that is there a limit on Windows or DPM in creating these Dynamic volumes? or can DPM create as many as it likes, so long as the disk has space?

     

     


    Tuesday, May 3, 2011 12:12 PM

Answers

  • There is a limit to the number of volumes, but it's something like 600.  Since DPM uses two volumes per protected data source (one replica and one recovery point volume) this means you can protect about 300 data sources.  If you use colocation (DPM 2010 feature) you can protect many SQL databases using a single set of volumes.

    You don't have anything to worry about - you have very few volumes compared to some of the servers I manage (probably approaching 400 volumes).

    There is one thing you everyone should keep in mind if you are running DPM on a 2008 server (not 2008 R2).  There's an important hotfix that prevents possible loss of all dynamic volumes when you have 100+ volumes.  I was bit by this bug - not pleasant.  http://blogs.technet.com/b/dpm/archive/2010/02/18/dynamic-disk-hotfix.aspx

    • Marked as answer by MSDN Student Wednesday, May 4, 2011 1:43 PM
    Tuesday, May 3, 2011 1:09 PM
  • Hi

    Sharepoint data can't be co-located only "pure" SQL databases.

    The difference is that your protecting SQL databases through SharePoint (this is the way you should do it) and not directley as a SQL database.

    Regarding your picture of the disk-management, this is allright. As the former answer you can have up to 300 datasources. DPM uses GUID's.


    Best Regards

    Robert Hedblom

    MVP DPM


    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Tuesday, May 3, 2011 1:31 PM
    Moderator
  • Hi

    First of, a data source if a protected memeber that is a member of a protection group. This could be for example a volume, share, SQL database etc.

    If you protect a SharePoint farm every content database will be represented as a data source as far as I understand. So to answer your question in your example above it would be 100 datasources.

    I hope this answers your question.


    Best Regards

    Robert Hedblom

    MVP DPM


    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Tuesday, May 3, 2011 7:16 PM
    Moderator

All replies

  • There is a limit to the number of volumes, but it's something like 600.  Since DPM uses two volumes per protected data source (one replica and one recovery point volume) this means you can protect about 300 data sources.  If you use colocation (DPM 2010 feature) you can protect many SQL databases using a single set of volumes.

    You don't have anything to worry about - you have very few volumes compared to some of the servers I manage (probably approaching 400 volumes).

    There is one thing you everyone should keep in mind if you are running DPM on a 2008 server (not 2008 R2).  There's an important hotfix that prevents possible loss of all dynamic volumes when you have 100+ volumes.  I was bit by this bug - not pleasant.  http://blogs.technet.com/b/dpm/archive/2010/02/18/dynamic-disk-hotfix.aspx

    • Marked as answer by MSDN Student Wednesday, May 4, 2011 1:43 PM
    Tuesday, May 3, 2011 1:09 PM
  • Thanks for the reply. This really helps me.

     

    I create two protection groups one for Sharepoint one for SQL Server. and in my powershell code I say

    Set-PolicyObjective -ColocateDataSources $true -ProtectionGroup $mpg

    Then I should see only 4 volumes. 2 for Sharepoint and 2 for SQL (every database should be included in the coloated data source).

    then why am I seeing so many volumes?

    Is the powershell not really colocating the data sources? (specially the SQL ones).

     

    Tuesday, May 3, 2011 1:21 PM
  • Hi

    Sharepoint data can't be co-located only "pure" SQL databases.

    The difference is that your protecting SQL databases through SharePoint (this is the way you should do it) and not directley as a SQL database.

    Regarding your picture of the disk-management, this is allright. As the former answer you can have up to 300 datasources. DPM uses GUID's.


    Best Regards

    Robert Hedblom

    MVP DPM


    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Tuesday, May 3, 2011 1:31 PM
    Moderator
  • One last question Robert.

    If a SharePoint Farm has 100 content databases. Is this considered one data source or 300 Data soruce

    SharePoint is protected as SharePoint and not as SQL.

    Some databases which are custom databases or SharePoint Service Application Configuration databases are protected as SQL databases. because these are not protected as sharepoint protection by DPM.


    Tuesday, May 3, 2011 2:23 PM
  • Hi

    First of, a data source if a protected memeber that is a member of a protection group. This could be for example a volume, share, SQL database etc.

    If you protect a SharePoint farm every content database will be represented as a data source as far as I understand. So to answer your question in your example above it would be 100 datasources.

    I hope this answers your question.


    Best Regards

    Robert Hedblom

    MVP DPM


    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Tuesday, May 3, 2011 7:16 PM
    Moderator