none
CopyBackupEnabled Regkey for DPM2010 also ? RRS feed

  • Question

  • Hi !

     

    I found this in an DPM 2007 forum post:

     

    To configure DPM 2007 to perform VSS copy backup, add the following CopyBackupEnabled registry value under the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0

    Registry value: CopyBackupEnabled
    Type: REG_DWORD
    Value Data: 1

     

    Does this still work for DPM2010 ?

     

    Ah, and does this require a restart of the DPM Server or the Production Server ?

     

    Thanks,

    Alex

     



    Sunday, June 20, 2010 8:58 PM

Answers

  • No the above key do not help in stopping the log truncation if you protect SQL by DPM server itself. If you are using SQL native backup then you can configure SQL to take Copy backups always, while DPM continue to take incremental as well as Full backups.
    Thanks, Praveen D [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, June 22, 2010 12:09 PM

All replies

  • What are you looking for using this key? This key is only for DPM not to truncate other application logs(like exchange/SQL) when they are not protected by DPM but other applications (like system state/BMR/VM backup) on the same volume are protected. But DPM never does a Copy backup for Exchange/SQL when this key is specified. But with DPM 2010 please find more options on how Copy backup can be enabled for Exchange 2010 with its documentation. Here is one post that can help how one can specify DAG database to be backed-up to have Copybackup at: http://blogs.technet.com/b/ilvancri/archive/2010/05/10/using-dpm-2010-to-backup-exchange-2010-dag.aspx
    Thanks, Praveen D [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, June 21, 2010 1:32 PM
  • Hi !

     

    I am trying to prevent DPM2010 from truncating SQL logfiles of databases on an SQL 2008 server since the databases are also protected by a management plan on that SQL Server. We are currently testing DPM2010 in that environment so until DPM2010 is live we have those databases protected by two backup solutions and we want to avoid both truncating logfiles.

     

    So does the above registry key prevent DPM2010 from truncating logfiles on SQL databases ?

     

    bye,

    Alex

    Monday, June 21, 2010 7:24 PM
  • No the above key do not help in stopping the log truncation if you protect SQL by DPM server itself. If you are using SQL native backup then you can configure SQL to take Copy backups always, while DPM continue to take incremental as well as Full backups.
    Thanks, Praveen D [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, June 22, 2010 12:09 PM
  • Hi Praveen,

     

    that is not good. Currently we are having problems with the DPM Server because the LUN of the backupdevice is not reliable. So we need to rely on the native SQL backup and not DPM server. Shouldn´t there be an option in the GUI or at least powershell/regkey to enable CopyBackup for SQL and Exchange Databases ? Since you added this to DPM2007 it should naturally be available for DPM2010 also.

     

    Thanks,
    Alex

     

    Thursday, June 24, 2010 7:36 AM