{"id":2948,"date":"2016-03-08T08:00:44","date_gmt":"2016-03-08T07:00:44","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=2948"},"modified":"2016-06-10T16:10:07","modified_gmt":"2016-06-10T15:10:07","slug":"set-data-protector-smart-cache-power-live-migrate","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2016\/03\/set-data-protector-smart-cache-power-live-migrate\/","title":{"rendered":"How to set up Data Protector to use Smart Cache for Power On and Live Migrate"},"content":{"rendered":"<p>With HPE Data Protector you have advance VM recovery functionality when backing up using either a 3Par or Smart Cache device.<\/p>\n<p>To give you some background on why this is the supported method is due to the flow\/process that Data Protector uses when doing this type of recovery.<\/p>\n<p>Once the restore job has been created as a Power On or Live Migrate, Data Protector will create a NFS share from the Smart Cache device and present and mount it to the ESXi server, sounds simple enough and it is since Data Protector does all of this for you. The reason your Smart Cache device cannot use NAS mount points is due to limitations of NAS in that you cannot do a double mount on a shared volume. What is a double mount you ask? When you create a NAS share (CIFS or NFS) that counts as one share, as explained above that Data Protector process is to create a NFS share to present to the ESXi server, if attempted on a NAS share that would count as the second share which is the part that is not supported.<\/p>\n<p>By definition a Smart Cache is as follows:<\/p>\n<p><b>Smart Cache:<\/b><\/p>\n<p>The Smart Cache is a backup to disk device that enables non-staged recovery from VMware backups. The Smart Cache device can operate on one of the following mount points:<\/p>\n<ul>\n<li>NAS share (CIFS and NFS)<\/li>\n<li>Disk (SAN, iSCSI, local) formatted with file system<\/li>\n<\/ul>\n<p>However it needs to be noted that in order to do Power on or Live Migrate the Smart Cache device can NOT use NAS share as a mount point, only SAN, iSCSI and Local disk are supported.<\/p>\n<p>To get started select which server will be used as the Smart Cache client with the above mentioned storage type, set your storage up as you normally would a typical file system, create a directory on the file system.<\/p>\n<p>Once that has been done you will need to run the following commands from the Powershell Admin console, this enables the server to run remotely signed executable jobs that Data Protector will run to create a NFS share from the Smart Cache device.  The second command just verifies that the server is configured correctly.<\/p>\n<p><code>Set-ExecutionPolicy remotesigned<\/code><br \/>\nYou will be prompted to verify are you sure you want to do this, you would type \u201cY\u201d for yes as in the screen shot below.<br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart1.png\" alt=\"smart1\"\/>\n<\/p>\n<p>Next you will need to run the following command from the c:\\Program Files\\Omniback\\bin directory if you are using windows. As shown in the screen shot below<br \/>\n<code>.\\nfsServiceCheck.ps1<\/code><br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart2.png\" alt=\"smart2\"\/>\n<\/p>\n<p>Once this has been done you just simply create a new Backup to Disk device using the client you configured above as seen in the screen shot below<br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart3.png\" alt=\"smart3\"\/>\n<\/p>\n<p>Once you have the device created you simply run your VM integrated backup with this device as your target.<\/p>\n<p>When you are ready to do a Power On or Live Migrate restore you will select the recovery version that used the Smart Cache device and select the Power On or Live Migrate from the VM options drop down as highlighted below.<br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart4.png\" alt=\"smart4\"\/>\n<\/p>\n<p>Then you set the destination from the destination tab and hit the Power On button at the bottom as highlighted in the screen shot below<br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart5.png\" alt=\"smart5\"\/>\n<\/p>\n<p>Then the restore process will begin. Just as a reminder when a Power On is the restore type selected it will power on the restored VM with networking disabled as not to interfere with the already running VM with the same name.<\/p>\n<p>The restore session will look something like the screen shot below<br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart6.png\" alt=\"smart6\"\/>\n<\/p>\n<p>You will note on the vCenter server that it creates a new VM using the session id as part of the name, and again it is powered on with its Networking disabled.<br \/>\n<img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/smart7.png\" alt=\"smart7\"\/>\n<\/p>\n<p>Once you have finished your testing, Twenty-Four hours later Data Protector will automatically delete the mounted VM from the vCenter server (does not apply for live migrated machines).<\/p>\n<p>This post was prepared and documented by <b>Geoff Rennie<\/b>. Geoff is a Presales colleague in HPE Software &#8211; AMS region. Thanks for sharing this content.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>With HPE Data Protector you have advance VM recovery functionality when backing up using either a 3Par or Smart Cache device. To give you some background on why this is the supported method is due to the flow\/process that Data Protector uses when doing this type of recovery. Once the restore job has been created [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-Ly","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":2363,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/08\/data-protector-patch-bundle-9-04-features\/","url_meta":{"origin":2948,"position":0},"title":"Data Protector 9 &#8211; Patch Bundle 9.04 (Build 104)","date":"5. August 2015","format":false,"excerpt":"{:en}On 2015\/08\/06 HP released patch bundle 9.04 for Linux, HP-UX and Windows, it includes 494 changes for Windows and 439 changes for Linux. With the new bundle some new and important features were introduced (complete list - see patch description): Power-On a VMware virtual machine from 3PAR snapshot or from\u2026","rel":"","context":"In &quot;DP A.09.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3097,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/06\/hpe-data-protector-7-0x-8-0x-eol\/","url_meta":{"origin":2948,"position":1},"title":"HPE Data Protector 7.0X and 8.0X &#8211; EOL","date":"3. June 2016","format":false,"excerpt":"{:en} The time has come, this month the support for Data Protector 7.0x and 8.0x Data Protector will end. Support for version 8.1x will end 30\/06\/2017. Of course, all customers with an active maintenance contract can upgrade to the current Data Protector version 9.0x. Data Protector 9.0x includes enhancements like:\u2026","rel":"","context":"In &quot;Data Protector Links&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/06\/eol.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1478,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/write-device-parameter-incorrect\/","url_meta":{"origin":2948,"position":2},"title":"Cannot write to device &#8211; the parameter is incorrect","date":"5. July 2013","format":false,"excerpt":"{:en}When using the wrong block size for the tape devices, you may get the error message Cannot write to device ([87] The Parameter is incorrect.) during the backup or while formatting media. This error may occur if as SAS library, attached to the controller P212-ZM is used. When you try\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1480,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/data-protector-8-00-cifs-share-backup\/","url_meta":{"origin":2948,"position":3},"title":"Data Protector 8.00 and CIFS Share Backup","date":"5. July 2013","format":false,"excerpt":"{:en}When using Data Protector 8.00 to backup a CIFS share (Network Share Backup), no matter if it is a Windows share or NetApp Filer, it could happen that the job does not backup any data from the share. In more detail, when selecting to backup all folders for the share\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":388,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/03\/savedevices-omnidownload\/","url_meta":{"origin":2948,"position":4},"title":"SaveDevices &#8211; omnidownload","date":"16. March 2011","format":false,"excerpt":"{:de}Im Rahmen des Disaster Recovery f\u00fcr den Cell Server empfiehlt es sich neben der obrindex.dat - siehe Recover Cell Server auch die Libraries und Devices herunterzuladen, um sie im Bedarfsfall wieder schnell generieren zu k\u00f6nnen. Daf\u00fcr habe ich das kleine Tool SaveDevices geschrieben, welches die Konfiguration in Text Dateien ablegt.\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":313,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/01\/eadr-mit-windows-2008-r2\/","url_meta":{"origin":2948,"position":5},"title":"EADR with Windows 2008 R2","date":"21. January 2011","format":false,"excerpt":"{:de}In einen fr\u00fcheren Artikel hatte ich \u00fcber die Wiederherstellung eines Windows 2003 Servers mit Data Protector berichtet. Nachdem Windows 2008 auch immer mehr in Rechenzentren betrieben wird zeige ich nachfolgend die Wiederherstellung eines Windows 2008 R2 Servers mit Data Protector und der Enhanced Automated Disaster Recovery Funktion. Vorbereitung: In der\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2948"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=2948"}],"version-history":[{"count":6,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2948\/revisions"}],"predecessor-version":[{"id":2954,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2948\/revisions\/2954"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=2948"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=2948"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=2948"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}