none
DPM 2012 SP1 - How to protect a single SQL instance with more than 3000 Databases ? RRS feed

  • Question

  • I want to protect a SQL Server 2008 R2 failover cluster, one instance and more than 3000 databases.

    DPM  2012 have some limitations: 4200 Ful Express Backup / week, 30  backup / volume, 600 volumes max...

    Any idea on how to bypass this limits ?  Or do i need to use a different method ? ( protect SQL Backup file .bck, etc.)

    Wednesday, February 20, 2013 8:05 AM

All replies

  • Hi Vincent,

    You should see these two links:

    Selecting the Number of DPM Servers

    http://social.technet.microsoft.com/Forums/en-US/dpmsqlbackup/thread/3c8769cd-3625-455a-ab76-35eba857664b

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Wednesday, February 20, 2013 9:43 PM
  • Hi,

    This is a pro-active warning Alert raised by DPM to let the user know that he has either 1) Protected too many SQL data sources belonging to the same PS per DPM server, or 2) has set the EF frequency too high, or 3) a combination of both; and that DPM has not been tested to complete this many EFs on time for “typical” databases to ensure that the SLA you have in mind will be met.
     
    So take 4200/7 = 600 express full backups that can be done per SQL server per day and not get the alert.  
     
    If the user ignores this alert, DPM should just continue to work, however there can be two possible outcomes. First, if the individual databases are very small and have little churn, the backups will work just fine. Second, if the databases are larger and have a lot of churn, some EF backups may fail with errors stating that other backups are in progress...  If you wait for a week and monitor the failure rate of jobs you will have a good idea about whether you should do something about this alert or just ignore it.
     
    You can add these values manually as a dword value. The value of 4200 can be overridden in the registry:

     "Software\Microsoft\Microsoft Data Protection Manager\ScaleConfig\SQLExpressFullPerPSLimit" 
     "Software\Microsoft\Microsoft Data Protection Manager\ScaleConfig\SQLExpressFullLimit"
     
    Add both of these registry values (SQLExpressFullPerPSLimit and SQLExpressFullLimit) on the DPM server itself. The former defines how many Express Full backups you can create per protected server and the latter defines how many you can create in total from that DPM server.  

    Once added, you must go through the modify protection group wizard for the protection group protecting the SQL DB's without making changes.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, February 20, 2013 10:22 PM
    Moderator