tag:blogger.com,1999:blog-1850520466090207324.post5846086957963832049..comments2022-03-27T07:21:39.770-05:00Comments on The Network Guy: Automating a DPM RecoveryRick Estradahttp://www.blogger.com/profile/17078030992783921914noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1850520466090207324.post-4082602648594271562017-05-02T16:22:17.679-05:002017-05-02T16:22:17.679-05:00Thanks for posting this.
Will give this a tryThanks for posting this.<br /><br />Will give this a tryirfnhttps://www.blogger.com/profile/12841011149798514780noreply@blogger.comtag:blogger.com,1999:blog-1850520466090207324.post-4866835424494264392009-09-04T12:19:34.445-05:002009-09-04T12:19:34.445-05:00First thanks for this. I would never have figured...First thanks for this. I would never have figured it out. <br /><br />I am having problems when trying to recover a Hyper-V Item. I get the the search and specifiy what I believe is the correct "location" information. The #so looks good.<br /><br />But when I try to Get-RecoverableItem, powershell terminates and closes itself.<br /><br />The location is "\Backup Using Saved State\MalibuEX2010" and that does exist.<br /><br />Any ideas? I have gotten normal dadtasets to recover with no problems so I think I have th general idea.<br /><br />Thanks.<br /><br />DougAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-1850520466090207324.post-30953828746584789422009-03-12T15:05:00.000-05:002009-03-12T15:05:00.000-05:00I was glad to stumble across this - I had been fig...I was glad to stumble across this - I had been fighting with something similar for a while.<BR/><BR/>I had used a different technique to execute the powershell script than you... I had come up with something different when scripting a different task (automatically adding dbs to a protection group, a la a script on the ctrl p blog).. anyway, instead of creating a batch file and running it from the task scheduler, I set up my task with this horribly complex command line.<BR/><BR/>C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\Microsoft DPM\DPM\bin\dpmshell.psc1" -command ".'C:\Program Files\Microsoft DPM\scripts\myScript.ps1' param1 'parameter 2'"<BR/><BR/>note that param1 has no whitespace, but parameter 2 does (in my script, parameter 2 is a file path containing white space).<BR/><BR/>If you are interested, the reason I need to create a scheduled recovery is so I can store a copy of the DPM database backup file produced by running dpmbackup -db. I created a protection job to protect the output file (located on the DPM server), and wanted to stash a copy on another server, to aid in the event that my DPM server dies... I don't want to have to recover the catalog from tape.<BR/><BR/>Thanks for the post!Anonymousnoreply@blogger.com