Ctrl P - The Data Protection Manager Blog! : Powershell Scripts

CLI Script: Script to generate DPM configuration report

dpm — Wed, 29 Apr 2009 15:54:00 GMT

The attached script generates a report of the mapping between each Exchange Server, the backup Protection Groups and its associated SGs.

Krishna Mangipudi

CLI Script: DPM status report

dpm — Wed, 29 Apr 2009 15:50:00 GMT

The following script generates a comprehensive report of failures and the storage utilization for each Exchange Server that is protected by DPM on a per SG basis.

CLI Script: To generate status reports

dpm — Wed, 29 Apr 2009 15:42:00 GMT

The attached script generates a comprehensive report of the status of all backups and the storage utilization for each Exchange Server that is protected by DPM on a per SG basis.

DPM CLI Tips 'n Tricks: Powershell Basics - Part II

dpm — Mon, 30 Jun 2008 17:32:00 GMT

Tab Completion

The most fascinating part of DPM Management Shell is Tab Completion of cmdlets. By learning the common verbs in Powershell (like Get, Set, Start etc.), a Windows or an Exchange admin can easily use that knowledge and learn the DPM cmdlets. This is because the same verbs are used in DPM Management Shell too.

For example: To get the list of protected servers backed-up by a DPM server, one needs to just type Get-P and keep pressing tab. This would result in Powershell suggesting the various cmdlets, and you can choose the right one needed. The ones that you would see in this example are - Get-Process, Get-ProductionCluster, Get-ProductionServer etc.

In addition, if you can also tab complete the various parameter names too in the same way, by typing a “-“ after the cmdlet name and pressing tab.

Examples of cmdlet usage(Get-Help <cmdlet> -example)

Getting directly to the example usage of a cmdlet can be done easily with optional parameters in Get-Help - Get-help <cmdletname> -example. This will directly print only the example usages of the cmdlet:

For example:

PS D:\> Get-help Get-ProtectionGroup -example

NAME

Get-ProtectionGroup

SYNOPSIS

Retrieves the list of protection groups on the DPM server.

EXAMPLE 1

Get-ProtectionGroup -DPMServerName TestingServer

This command returns the protection group on a DPM server.

Getting only the cmdlet syntax (Get-Command <cmdlet> -syntax)

Another quick help about the syntax of cmdlet would be get by typing

PS D:\> Get-Command Get-Datasource -syntax

Get-Datasource [-DPMServerName] <String> [-Inactive] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

Get-Datasource [-ProductionServer] <ProductionServer> [-Async] [-Inquire] [-Replica] [-Tag <Object>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

Get-Datasource [-ProtectionGroup] <ProtectionGroup> [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

Get-Datasource [-DPMServerName] <String> [-SearchPath] <String> [[-ProductionServerName] <String>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

Using the object member properties (Get-Member)

With the help of get-member you can verify/set the property of the object.

PS D:\> $pg = Get-ProtectionGroup “MyDPMServerName”

PS D:\> $pg | get-member

TypeName: Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ProtectionGroup

Name MemberType Definition

---- ---------- ----------

AddProtectableObject Method System.Void AddProtecta...

AddProtectionOptions Method System.Void AddProtecti...

FriendlyName Property System.String FriendlyN...

InitializationType Property Microsoft.Internal.Ente...

Now these properties can be used to filter and get a specific PG.

For Example:

$clipg = Get-ProtectionGroup $dpmname | where { $_.FriendlyName -eq $pgname }

CLI Help Updates and Errata

Any additional help information or errata gets updated per cmdlet and is available at http://go.microsoft.com/fwlink/?LinkId=95130.

- Mukul Shekhawat, Balaji Hariharan

DPM CLI: Quick reference help

dpm — Mon, 30 Jun 2008 10:15:00 GMT

While using the DPM Management Shell, one would like to have a list of all cmdlets and its short help for quick reference. Also, we heard it would be useful to group the various cmdlets by the function they do – e.g. Library, Disk, Recovery or Protection related etc. Keeping this in mind, we have published this quick reference for you based on DPM 2007 Management Shell. You could take a print out of this and keep it handy while creating scripts. Btw, new cmdlets or parameters may be introduced in future versions or service packs of DPM, so you might want to update this list manually.

- Mukul Shekhawat, Balaji Hariharan

CLI Script: Auto re-running consistency checks

dpm — Tue, 24 Jun 2008 09:11:00 GMT

Some customers had non-DPM issues, like network issues because of which consistency check (CC) jobs failed too often. For the benefit of them, we have added a script that would re-try CC until it succeeds. Note: In some cases, CC would impact the protected computer’s performance and hence use this script appropriately.

- Vikash Jain

DPM CLI Tips 'n Tricks: Powershell Basics

dpm — Wed, 18 Jun 2008 20:47:00 GMT

The scripts posted in this blog require knowledge of Powershell and DPM cmdlets. So we thought we would present some tips ‘n tricks to become power users!

Introduction

The first difference between any normal Command Line Interface (CLI) (typically, Windows cmd.exe based environment) & Powershell is that, Powershell is a full blown .Net environment and is object oriented. In other words, it treats all input/output parameters as objects and when you pipe one command to another, objects flow instead of plain text as in old shells. Similarly, DPM Management Shell also takes inputs in the form of objects – for example, DPM, Protection Group, Datasource, Library, Tape, Tape Drive, Disk etc. are all .Net objects. Let’s now move on to more interesting stuff.

Finding cmdLets (Get-Command or gcm)

For knowing all the cmdLets present in the Powershell instance, use Get-Command (or gcm in short). When run, the output will be something like this:

PS D:\ > Get-command

CommandType Name Definition

----------- ---- ----------

Cmdlet Add-Content Add-Content [-Path] <String[...

Cmdlet Add-DPMDisk Add-DPMDisk [-DPMDisk] <Disk...

Cmdlet Add-History Add-History [[-InputObject] ...

Cmdlet Add-Member Add-Member [-MemberType]

Cmdlet Add-PSSnapin Add-PSSnapin [-Name] <String...

Cmdlet Add-Tape Add-Tape [-DPMLibrary] <Libr...

Cmdlet Clear-Content Clear-Content [-Path] <Strin...

Finding DPM cmdLets (Get-DPMCommand)

Similarly for getting all the cmdLets belonging to only DPM, use the Get-DPMCommand.

PS D:\ > Get-DPMCommand

CommandType Name Definition

----------- ---- ----------

Cmdlet Add-DPMDisk Add-DPMDisk [-DPMDisk] <Disk...

Cmdlet Add-Tape Add-Tape [-DPMLibrary] <Libr...

Cmdlet Connect-DPMServer Connect-DPMServer [-DPMServe...

Cmdlet Disable-DPMLibrary Disable-DPMLibrary [-DPMLibr...

Cmdlet Disable-TapeDrive Disable-TapeDrive [-TapeDriv...

How to use a cmdlet?

1. Understanding the cmdlet parameters (Get-Command and Format-List)

There are two parts to understanding a cmdlet. First, to look at the various input parameters and various usages, you can use the Get-Command itself on a specific cmdlet, in the following fashion – Get-Command <cmdlet> | format-list (or gcm <cmdlet> | fl, in short).

PS C:\> gcm Set-Alias | fl

Name : Set-Alias

CommandType : Cmdlet

Definition : Set-Alias [-Name] <String> [-Value] <String> [-Description <String>] [-Option <ScopedItemOptions>] [-PassThru] [-Scope <String>] [-Force] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>] [-WhatIf] [-Confirm]

2. Reading Help documentation for a cmdlet (Get-Help or help)

For reading the Help documentation for any cmdlet use the following (Get-Help or help)

Get-Help <cmdlet>

For example:

PS D:\ > Get-Help Add-Tape

NAME

Add-Tape

SYNOPSIS

Adds a tape to a DPM library.

SYNTAX

Add-Tape [-DPMLibrary] <Library> [-Async] [-JobStateChangedEventHandler <Jo

bStateChangedEventHandler>] [<CommonParameters>]

…..

3. Getting detailed help, and seeing sample scripts

For seeing additional information on each of the cmdLets, you can use the –Full or –Detailed parameters in Get-Help.

e.g. Get-Help Add-Tape –Detailed

Get-Help Add-Tape –Full

DPM Object Properties (Get-Member or gm)

The DPM cmdlets are logically divided in three groups Protection (Backup), Recovery and Management related (Library & Disk). All the tasks that can be done from the DPM UI in these areas, can be done from the cmdLets in these areas. Infact, the CLI provides additional features than the UI, in some scenarios.

You can get the member properties of any object by pipelining the output to Get-Member:

For example:

$lib = Get-DPMLibrary -DPMServerName “Testing Server Name”

$lib | Get-Member

Will give all the members of $lib (Library object).

PS D:\ > $lib | get-member

TypeName: Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.LibraryMan

agement.Library

Name MemberType Definition

---- ---------- ---------

ClearCache Method System.Void ClearCache()

Dispose Method System.Void Dispose()

We hope this was useful, feel free to add comments as feedback to this post. And in the next version, we can add more tricks!

- Mukul Shekawat, Balaji Hariharan

CLI Script: To recover a DPM replica volume from data stored in tape

dpm — Wed, 18 Jun 2008 20:39:00 GMT

When a disaster occurs, and you lose your replica volume for any datasource, you could re-seed the replica from the backed-up data you have in tape. This little script initializes replica from a tape recovery point. The parameters have to be customized for your environment first as given below.

Save the attached file as a .ps1 file and invoke through the DPM Management Shell.

- Madhan S

CLI Script: To remove all datasources in inactive protection state

dpm — Wed, 11 Jun 2008 16:51:00 GMT

The attached script removes all inactive datasources under a given DPM server. It provides options to remove inactive datasources on disk/tape/both. Save this as a .ps1 file and invoke it from inside the DPM Management Shell. Please contact us if you need any further assistance in running the script or face any issues.

- Madhan S

DPM PowerShell Script -- invoking a Consistency Check

JasonBuffington — Thu, 10 Apr 2008 20:23:55 GMT

By design, DPM 2007 should be ‘fire and forget’ – meaning that after initial replication, data changes will automatically and routinely replicate.

However, due to a variety of external factors, the data set may become inconsistent. Usually, DPM will correct itself within a replication cycle. Depending on how often you have configured replication, this may not be soon enough. One resolution to this is to have one’s management solution (e.g. System Center Operations Manager) see the alert that a data set is inconsistent and then automatically run this ‘consistency check’ to revalidate the data in a more timely manner.

Attached is a sample PowerShell script to invoke a consistency check of on a DPM data source.

# This script do a consistency check on the file system data source. The parameters have to be initialized first as given below. Please give the values of parameters as appropriate for your environment. You can customize this easily as per your needs. Save the attached file as a .ps1 file and invoke through the DPM Management Shell.

$dpmname = "DPM Server Name";
$pgname = "My PG";
$dsname = "G:\";

function StartDatasourceConsistencyCheck
{
    param($dpmname, $pgname, $dsname, $isheavyweight)

    write-host "Start consistency check on $dsname "

    trap{"Error in execution... $_";break}
    &{
        write-host "Getting protection group $pgname in $dpmname..."
        $clipg = Get-ProtectionGroup $dpmname | where { $_.FriendlyName -eq $pgname }

         if($clipg -eq $abc)
          {
              Throw "No PG found"
          }

        write-host "Getting $dsname from PG $pgname..."
        $ds = Get-Datasource $clipg | where { $_.logicalpath -eq $dsname }

        if($ds -eq $abc)
         {
              Throw "No Data Source found"
         }

        if( $isheavyweight -ne "true")
        {
            write-host "Starting light weight consistency check..."
            $j = Start-DatasourceConsistencyCheck -Datasource $ds
            $jobtype = $j.jobtype
            if(("Validation") -notcontains $jobtype)
                {
                    Throw "Shadow Copy job not triggered"
                }
            while (! $j.hascompleted ){ write-host "Waiting for $jobtype job to complete..."; start-sleep 5}
            if($j.Status -ne "Succeeded") {write-host "Job $jobtype failed..." }
            Write-host "$jobtype job completed..."
        }
        else
        {
            write-host "Starting Heavy weight consistency check..."
            $j = Start-DatasourceConsistencyCheck -Datasource $ds -HeavyWeight
            $jobtype = $j.jobtype
            if(("Validation") -notcontains $jobtype)
                {
                    Throw "Shadow Copy job not triggered"
                }
            while (! $j.hascompleted ){ write-host "Waiting for $jobtype job to complete..."; start-sleep 5}
            if($j.Status -ne "Succeeded") {write-host "Job $jobtype failed..." }
            Write-host "$jobtype job completed..."
        }

    }
}

#Example for usage

StartDatasourceConsistencyCheck $dpmname $pgname $dsname "false"
StartDatasourceConsistencyCheck $dpmname $pgname $dsname "true"

-- Mukul

CLI script: Create protection groups for Disk based backups

dpm — Tue, 18 Mar 2008 12:29:00 GMT

The following script creates a protection group with disk based protection, for a simple folder. It can be easily extended to add more data sources of different kinds – like Microsoft Exchange, SQL, Sharepoint, System state or Virtual Servers. The Synchronization frequency and retention ranges etc. can be easily modified to suit your needs. Also, since we are protecting a sub-folder in a volume, we are using the CalculateSize parameter in Get-DataSourceDiskAllocation, which would calculate the exact size needed for all the items in that folder. This is not needed when protecting an application like Exchange/SQL or protection the entire File system volume.

---------------------------------------------- Start of Script ---------------------------------------------------

# To D2D create PG and do the initial replication

# This script is for creating Disk to Disk PG for File System

# For details contact mukuls[at]microsoft[dot]com

# Create a .ps1 file with this script and run under DPM Management Shell

# Customize these values as per your environment

$dpmname = "DPMServername.somedomain.com"

$psname = "PSservername.somedomain.com"

$dsname = "G:\"

$poname = "G:\ProtectableFolder"

$pgname = "MyCLIPG"

function CreatePG

{

param($dpmname, $psname, $dsname, $poname, $pgname)

write-host "Creating a D->D PG --> $pgname..."

trap{"Error in execution... ";break}

Write-Host "Getting PS: $psname from DPM: $dpmname"

$ps = Get-ProductionServer -DPMServerName $dpmname | where { ($_.machinename,$_.name) -contains $psname }

Write-Host "Running Inquiry on PS: $psname for datasource $dsname"

$ds = Get-Datasource -ProductionServer $ps -Inquire | where { ($_.logicalpath,$_.name) -contains $dsname }

Write-Host "Getting Child-datasource $poname from datasource $dsname"

$po = Get-ChildDatasource -ChildDatasource $ds -Inquire | where { ($_.logicalpath,$_.name) -contains $poname }

write-host "Create New PG ..."

$pg = New-ProtectionGroup -DPMServerName $dpmname -Name $pgname

write-host "Adding child datasource..."

Add-childDatasource -ProtectionGroup $pg -ChildDatasource $po

write-host "Setting Protection Type..."

Set-ProtectionType -ProtectionGroup $pg -ShortTerm disk

write-host "Setting Policy Objective...retention range - 10Days, synchronizationFrequency 15"

Set-PolicyObjective -ProtectionGroup $pg -RetentionRangeInDays 10 -SynchronizationFrequency 15

write-host "Setting Policy Schedules ..."

$ShadowCopysch = Get-PolicySchedule -ProtectionGroup $pg -ShortTerm| where { $_.JobType -eq "ShadowCopy" }

Set-PolicySchedule -ProtectionGroup $pg -Schedule $ShadowCopysch -DaysOfWeek mo -TimesOfDay 02:00

write-host "Setting Disk Allocation, with optimization (will take a few minutes to complete)"

Get-DatasourceDiskAllocation -Datasource $ds -Calculatesize

Set-DatasourceDiskAllocation -Datasource $ds -ProtectionGroup $pg

write-host "Setting Replica Creation Method ..."

Set-ReplicaCreationMethod -ProtectionGroup $pg -NOW

write-host "Commiting PG"

Set-protectiongroup $pg

}

function waitforIRtoComplete

{

param($waittime)

write-host "Wait for IR to complete"

$val = $waittime/30

while($val -gt 0)

{

Write-host "Wait for IR to complete... $val"

start-sleep 30

$val--

}

Connect-DPMServer -DPMServerName $dpmname;

createPG $dpmname $psname $dsname $poname $pgname;

waitforIRtoComplete 120;

---------------------------------------------- End of Script ----------------------------------------------

- Mukul Singh Shekhawat, Balaji Hariharan

CLI: Create new Recovery points on tape for all datasources in a PG

dpm — Mon, 14 Jan 2008 14:10:00 GMT

This is a sample script that will automatically create new recovery points for the entire Data source’s in a Protection Group. You can customize this easily to change script file to create recovery points on disk. Save the attached file as a .ps1 file and invoke through the DPM Management Shell.

--------------------- Start of Script ---------------------

param([string] $dpmname, [string] $pgname, [string] $backupoption)

if(!$dpmname)
{
    $dpmname = read-host "DPMName:"
}
if(!$pgname)
{
    $pgname = read-host "pgName:"
}
if(!$backupoption)
{
    $backupoption = read-host "BackOption:"
}

write-Output "Creating $backupoption Recovery Point"

trap{"Error in execution... $_";break}
&{
write-Output "Getting protection group $pgname in $dpmname..."
$clipg = Get-ProtectionGroup $dpmname | where { $_.FriendlyName -eq $pgname}

if($clipg -eq $abc)
{
Throw "No PG found"
}

write-Output "Getting DS from PG $pgname..."
$backupds = @(Get-Datasource $clipg)

foreach ($ds in $backupds)
{
  write-Output "Creating Recovery point for $ds..."
  $j = New-RecoveryPoint -Datasource $ds -Tape -ProtectionType $backupoption
  $jobtype = $j.jobtype
  Write-Output "$jobtype Job has been triggerred..."
}



}

--------------------- End of Script ------------------------

- Mukul Singh Shekhawat

Script: Auto-add new SQL DBs for protection

dpm — Tue, 20 Nov 2007 02:00:00 GMT

This is a sample script that will automatically add all the newly available SQL DBs in all instances for protection. You can customize this easily to change the protection policy. Save the attached file as a .ps1 file and invoke through the DPM Management Shell. The script can also be added to the Windows scheduler and run on a scheduled basis.

- Kapil, Hitesh, Balaji

CLI Script: Job object fundamentals

dpm — Tue, 04 Sep 2007 21:35:00 GMT

In DPM, Jobs are objects that encapsulate the notion of a (typically) long running operation. Unfortunately though DPM v2 does not have cmdlets to directly monitor jobs, still a large number of cmdlets output jobs and it is useful to be able to interact with them.

The most commonly desired interaction is to be able to track the progress of a triggered job. If you see the anatomy of a Job object, it has properties that can be monitored to view the status of a job.

Let's start a relatively short running job and analyze the object.

>$j = Start-DPMLibraryRescan mydpmserver

>$j | gm -MemberType property

The ones we are interested in are 'HasCompleted' which is a boolean and 'Status' which is an enum. As the name says 'HasCompleted' tells whether the job has run to completion or not whereas the current state of a job is given by the 'Status' property.

The possible values of Status are -

· Scheduled - the job is scheduled to run but is not currently running, either because it is set to run at a later time or is waiting for availability of required resources.

· InProgress - The job is currently running.

· Cancelling - The job is being cancelled either because the user manually cancelled the execution or DPM decided so. NOTE: You can manually cancel a running job by calling the Cancel() method on it.

· Failed - The job has completed and was unsuccessful due to some error (or cancellation).

· Warning - The job has completed and one or more (but not all) sub-operations in the job failed.

· Succeeded - The job has completed successfully.

'HasCompleted' will be true when the Status is either 'Failed', 'Warning' or 'Succeeded'. So, typically the pattern to track the progress of a job is -

### Begin code

$job = <Some DPM cmdlet that returns a job>

while (!$job.HasCompleted)

{

Write-Host "Job status: $($job.Status)"

sleep 5

}

Write-Host "Job has completed. Final status: $($job.Status)"

### End code

There are 2 variations of monitoring when multiple jobs are triggered through a script. Either the jobs are to be run sequentially or they need to be all triggered without waiting for the others to finish and then all of them need to be tracked together.

The first intent is easy to achieve using the above mentioned steps. Trigger jobs in a loop and have the while loop inside to monitor the triggered job. Then a new job will not be triggered until the previous finishes. For the second one, triggering several jobs in parallel is easy, keep calling cmdlet(s) that trigger jobs without waiting for the completion of others. For tracking all of the triggered jobs, you can use the following -

It is easier to explain using a real example, so consider the problem of running consistency check on all datasources that are being actively protected.

### begin code

$jobList = @() # Create an empty array to store information about all the triggered jobs.

foreach ($datasource in @(Get-Datasource -DPMServerName $DPMServerName | ? {$_.Protected -and $_.State -eq "Invalid"})) # Find all the actively protected datasources which are not valid.

{

# Create a hash table that has a key named Job which contains the triggered consistency check job and a key named Datasource which contains the name of the datasource on which the consistency check job is triggered. Then add this hash table as an element of the array.

$jobList += @{Job = Start-DatasourceConsistencyCheck -Datasource $datasource; Datasource = $($datasource.LogicalPath)}

}

At this point we have an array of hashtables with each hash table having the triggered job and the name of the datasource.

Now we can track all the jobs and print out useful progress messages (this is the reason we stored useful information (name of the datasource) about the job). The following block prints the progress of all the jobs every 5 seconds and stops when all the jobs have run to completion.

$completedJobsCount = 0

while ($completedJobsCount -ne $jobList.Length)

{

$completedJobsCount = 0

Write-Host ""

foreach ($jobHT in $jobList)

{

if ($jobHT.Job.HasCompleted)

{

Write-Host "Consistency check on $($jobHT.Datasource) completed. Status: $(($jobHT.Job).Status)"

$completedJobsCount += 1

}

else

{

Write-Host "Runnning consistency check on $($jobHT.Datasource)..."

}

sleep 5

}

- Mohit Chakraborty

CLI Script: Copy latest point in time of SQL DB to a folder

dpm — Tue, 04 Sep 2007 21:33:00 GMT

This script copies the latest recovery point of the specified SQL databases to the destination folder on a production server. Save this script as a .ps1 file and run it. Usage and examples of scripts can be found by calling them with ‘-?’ or ‘-help’ from inside DPM Management Shell.

--------------------------------- Start of Script -------------------------------------

param ([string] $DPMServerName, [string[]] $DatabaseList, [string] $DestinationServerName, [string] $DestinationLocation)

if(("-?","-help") -contains $args[0])
{
    Write-Host "Description: This script copies the latest recovery point of the specified SQL databases to the destination folder on a production server."
    Write-Host "Usage: Restore-SqlDatabase.ps1 [-DPMServerName] <Name of the DPM server> [-DatabaseList] <Array of SQL databases to restore> [-DestinationServerName <Name of the server to copy the database files to>] [-DestinationLocation] <Location on the destination server>"
    Write-Host "Example: Restore-SqlDatabase.ps1 mohitc02 `"mohitc04\* db`", `"mohitc04\reportservertempdb`" mohitc04 `"d:\recoverdir`""

exit 0
}

if (!$DPMServerName)
{
$DPMServerName = Read-Host "DPM server name"

    if (!$DPMServerName)
    {
        Write-Error "Dpm server name not specified."
        exit 1
    }
}

if (!$DatabaseList)
{
$DatabaseList = Read-Host "SQL database to recover"

    if (!$DatabaseList)
    {
        Write-Error "SQL database(s) not specified."
        exit 1
    }
}

if (!$DestinationServerName)
{
$DestinationServerName = Read-Host "Destination server"

    if (!$DestinationServerName)
    {
        Write-Error "Destination server not specified."
        exit 1
    }
}

if (!$DestinationLocation)
{
$DestinationLocation = Read-Host "Location on the destination server"

    if (!$DestinationLocation)
    {
        Write-Error "Destination location not specified"
        exit 1
    }
}

if (!(Connect-DPMServer $DPMServerName))
{
Write-Error "Failed to connect To DPM server $DPMServerName"
exit 1
}

$datasourceList = @()
Get-ProtectionGroup $DPMServerName | % {Get-Datasource $_} | % {if ($DatabaseList -contains $_.LogicalPath) {$datasourceList += $_}}

# Show all the SQL databases that could not be found as protected datasources.
foreach ($datasourceName in $DatabaseList)
{
    if (@($datasourceList | ? {$_.LogicalPath -ieq $datasourceName}).Length -eq 0)
    {
        Write-Error "Could not find datasource $datasourceName"
    }
}

# Restore the latest recovery point of each SQL datasource.
foreach ($datasource in $datasourceList)
{
    # Select the latest recovery point that exists on disk and trigger the restore job.
    foreach ($rp in @(Get-RecoveryPoint -Datasource $datasource | sort -Property RepresentedPointInTime -Descending))
    {
        foreach ($rsl in $rp.RecoverySourceLocations)
        {
            if ($rsl -is [Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ReplicaDataset])
            {
                $recoveryOption = New-RecoveryOption -TargetServer $DestinationServerName -TargetLocation $DestinationLocation -RecoveryLocation CopyToFolder -SQL -RecoveryType Restore
                $restoreJob = Recover-RecoverableItem -RecoverableItem $rp -RecoveryOption $recoveryOption -RecoveryPointLocation $rsl

                break
            }
        }

        if ($restoreJob)
        {
            break
        }
    }

    if ($restoreJob)
    {
        Write-Host "`nRunning restore of $($datasource.LogicalPath) from $($rp.RepresentedPointInTime) to $DestinationServerName\$DestinationLocation"

        # Comment out the next 7 lines to not wait for one restore job to finish before triggering the next one.
        while (!$restoreJob.HasCompleted)
        {
            Write-Host "." -NoNewLine
            sleep 3
        }

        Write-Host "`nJob status: $($restoreJob.Status)"
    }
    else
    {
        Write-Error "Could not find a recovery point on disk for $($datasource.LogicalPath)"
    }
}

---------------------------- End of Script --------------------------

- Mohit Chakraborty