Monthly archives: January 2011

Timothy

Microsoft Data Protection Manager: Start a Consistency Check on all Inconsistent Replicas with PowerShell

I'm a big fan of MS DPM and have been using it for years.  The one place where it really suffers, though, is the management console.  Even in DPM 2010, there are very few things you can do in a batch sequence, which is a common need for DPM administrators.

From time to time, your server may get a large amount of inconsistent replicas.  This is usually due to something outside of DPM's control.  For example, one DPM server I manage is a VM.  If the host server suspends the VM, then resumes and the target server it was backing up before suspend is suddenly offline (such as during a reboot cycle from updates), you can get inconsistent replicas.  There are numerous other scenarios, but you get the drift.  When this happens, the management console forces you to right click on every single alert individually and select "Run a synchronization job with consistent check."  (You can also just wait for the next automatic consistency check interval, but that's not always ideal.)

Luckily, PowerShell provides a better way to kick off a manual consistency check.  Behold!  Here is my DPM PowerShell script that kicks off a consistency check on every inconsistent replica.  This is tested with DPM 2010, but should also work with DPM 2007.

$pg = Get-ProtectionGroup
foreach ($pgi in $pg) { $ds = get-datasource $pgi; foreach ($dsi in $ds) { if ($dsi.State -eq 'Invalid') { Start-DatasourceConsistencyCheck $dsi | out-null; $dsi.ProductionServerName + " :: " + $dsi.DisplayPath } } }

Enjoy!

Blog

Search Posts

Recent Comments

  1. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Brian: Thank you so much Edward! :-)

  2. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Tom: Thank you Edward! After beating my head against a wall for days, tried your suggestion out and lo and...

  3. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Mike: DPM 2016 setup will fail if you have SQL Server Management Studio (SSMS) V17.x installed. Re-Install...

  4. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Rob: Edward, thanks man! you were a lifesaver. My scenario was Win Server 2016 from scratch, SQL 2016 (N...

  5. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Edward: It also crashes with the 4387 error if you have the SQL Management Studio 17 tools installed. Installing...

  6. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Ram: Hi - I followed richsmif instruction and was able to successfully install DPM 2016 on SQL 2016. Completed...

  7. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    Neighborgeek: Thanks for the post, this is exactly the issue I am running into. I'm disappointed to see that you didn...

  8. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    richsmif: I have DPM 16 working with SQL 16. Install SQL 16 first, don't touch, install DPM 16 , upgrade to ...

  9. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    ptbNPA: That should have been *ID 810*, not 820

  10. Re: DPM 2016 + SQL 2016 and "An unexpected error occurred during the installation" ID: 4387
    ptbNPA: For anyone else coming across this in the future and have an ID 820 error: For some strange reason...

Archive

Tag Cloud