CLI: Grow your replica and shadow copy volume sizes automatically!

re: CLI: Grow your replica and shadow copy volume sizes automatically!

virtuworks — Mon, 09 Nov 2009 01:41:37 GMT

I cant seem to get this to work on system state datasources, works on file based. Is there something special that needs to be done to get system states to work?

Creating DPM PowerShell Tasks in Operations Manager

David Allen - OpsMgr MVP — Thu, 04 Jun 2009 12:07:32 GMT

Performing general administrative DPM tasks can be quite time consuming so why not get Operations Manager

re: CLI: Grow your replica and shadow copy volume sizes automatically!

ben.hebert@ophrp.state.ny.us — Mon, 05 Jan 2009 21:45:45 GMT

When running I receive the following Error:

Set-DatasourceDiskAllocation : Missing an argument for parameter 'ShadowCopyAre

a'. Specify a parameter of type 'System.Int64' and try again.

At C:\Program Files\Microsoft DPM\DPM\bin\extend_DPM_disk.ps1:53 char:95

+ Set-DatasourceDiskAllocation -Manual -Datasource $ds -ProtectionGroup $MP

G -ShadowCopyArea <<<<

8178892800

re: CLI: Grow your replica and shadow copy volume sizes automatically!

cleej9 — Wed, 05 Nov 2008 17:15:55 GMT

Check out this article for more detail on running DPM scripts outside of the DPM management shell and scheduling them to run:

http://0direction.com/blog/index.php/2008/10/31/running-dpm-scripts-outside-of-the-dpm-management-shell/

re: CLI: Grow your replica and shadow copy volume sizes automatically!

cleej9 — Mon, 27 Oct 2008 18:49:05 GMT

That is because you are calling the powershell console without the DPM PS snapin loaded. I use the following code in the beginning of all of my DPM scripts so i can run them through the standard PS console:

if (!(Get-PSSnapin microsoft.dataprotectionmanager.powershell))

{

write-host "Adding PS Snapin for DPM..." -Fore Green

add-PSSnapin Microsoft.DataProtectionManager.PowerShell}

This will check to see if the snapin is loaded, and if not, load it.

re: CLI: Grow your replica and shadow copy volume sizes automatically!

rtuck — Thu, 23 Oct 2008 03:37:13 GMT

It works from within Powershell (IF I remove the '&' in front of the hostname), but when I schedule a task to run it as:

C:\WINDOWS\system32\WINDOW~2\v1.0\powershell.exe -command "& 'GrowRPVs.ps1'"

I get this:

"The term 'Connect-DPMServer' is not recognized as a cmdlet, function, operable

program, or script file. Verify the term and try again.

At C:\Program Files\Microsoft DPM\DPM\bin\GrowRPVs.ps1:17 char:29

+ $dpmserver=Connect-DPMServer <<<< $dpmservername"

re: CLI: Grow your replica and shadow copy volume sizes automatically!

GradonSilverton — Fri, 28 Mar 2008 22:57:55 GMT

Appears that there is a error in the Script if you copy it as above.

This Line:

"Set-DatasourceDiskAllocation -Manual -Datasource $ds -ProtectionGroup $MPG -ReplicaArea

$NewReplicaSize"

Needs to Read:

"Set-DatasourceDiskAllocation -Manual -Datasource $ds -ProtectionGroup $MPG -ReplicaArea $NewReplicaSize"

The Extra space caused the script to error out.

re: CLI: Grow your replica and shadow copy volume sizes automatically!

TechNet Archive — Fri, 20 Jul 2007 14:29:49 GMT

Hi Kapil,

I understand that the script blindfoldedly increases the Allocated Replica Size and Allocated Shadow copy area size if it doesn't meet the threshold value. Have you tested for the senarios where the disk space available doesn't meeet the requirements for allocating extra space ? In such cases,are there any issues with Save-ProtectionGroup and Modify-ProtectionGroup ??

With regards,

Mohd Abubakr.

re: CLI: Grow your replica and shadow copy volume sizes automatically!

Ruud Baars [MSFT] — Tue, 10 Jul 2007 15:27:48 GMT

Hi,

Very cool but I like to place 1 remark;

This is perfect as a guard but should not be encouraged as a 'daily thin provisioning' strategy rather than appropriate sizing up-front.

Cheers

Ruud