These are noted in the figure below highlighted in yellow
\n![\"ZDBVSS1\"\/](\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/zdbvss1.png\")
\n<\/p>\n
Once you have created the backup job (we will cover later) the command to have the array create the snapshot of the volume you wish to backup is made to the application server which then passes that command to the 3Par so the hardware array does the heavy lifting and it creates a snapshot on the array. At that point the snapshot is then presented to the Backup Server and mounted on the backup server so the data flows from the snapshot on the array to the backup server then off to your backup target. See figure below.
\n![\"ZDBVSS2\"\/](\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/zdbvss2.png\")
\n<\/p>\n
Now that you have an idea of how this works, let\u2019s discuss what you need install on each component and what commands that you need to run. First you will need to install on the Application server and the Backup Server the following:<\/p>\n
- \n
- HPE 3PAR VSS Agent<\/li>\n
- HPE P6000 \/HPE 3PAR SMI-S agent<\/li>\n
- MS Volume Shadow Copy Integration<\/li>\n
- Disk Agent<\/li>\n
- Media Agent especially on the Backup System<\/li>\n<\/ul>\n
Comment:<\/b> The Application system and Backup system should NOT be the same server, also they both must be running the same OS.<\/i><\/p>\n
How to setup the environment and commands to run to get the system ready<\/b><\/b><\/p>\n
We have already discussed the components that need to be installed onto the Application system and the Backup system but now you need to verify that you have the hardware configured correctly to see the storage.<\/p>\n
First you need to make sure that someone has configured a volume on the 3PAR and exported it to the application server and the application server can see its new file system and can read and write files to it.<\/p>\n
Next you need to make sure that the Backup system has also been zoned into the 3PAR so it has connectivity to the array. It does not need to have the Application servers volume presented to it but will need to have the ability to at least \u201csee\u201d the array.<\/p>\n
Now the trick here is that on the 3PAR array it works off the WWN of the host attaching to it and you can give the host name an alias of whatever you wish to call it, you create the volumes that you want\/need to assign to the hosts attached to the 3PAR. The 3PAR will take care of the rest, when you export the volumes to the hosts. However, take note here when working with Data Protector the Backup System\u2019s alias MUST be the FQDN of its self (see screen shot below).<\/i><\/p>\n
As you can see from the screen shot below showing the host, if you look under the name at the highlighted one you can see that the name can be whatever naming convention you want to set up, again which is no problem. But if you look at the highlighted host in the second screen shot you will see that it is in FQDN form, this is the application server.
\n![\"ZDBVSS3\"\/](\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/zdbvss3.png\")
\n
\n![\"ZDBVSS4\"\/](\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/zdbvss4.png\")
\n<\/p>\nNow if you look at the screenshot below of the exported volumes which they can also be whatever naming convention you wish to use. If you look at the highlighted volume and look at the far right side of the screen you can see that it has been exported to the FQDN of the application server.
\n![\"ZDBVSS5\"\/](\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/03\/zdbvss5.png\")
\n<\/p>\nNow you may ask yourself why is it important for the application server to be required to be in FQDN form, well that is because when Data Protector ZDB is in action and it uses the application server it is trying to us the FQDN as it is defined in the client list of Data Protector, so if it is not defined in the 3PAR the same way. You will experience an error that will look somewhat like the error below. In the beginning (not shown) everything will look normal but then you will get the following error.<\/p>\n
\n
\r\n[Minor] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:29:55 AM\r\n[236:9210] \tA SMI-S call to the array did not behave as expected.\r\n\t\tFailed volume:\tDP-2015.11.20-10-056503991 \r\n\t\tReturned message:\tError retrieving StorageID = HBA WWN of host sut74.atlpss.hp.net.\r\n\r\n[Normal] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:29:55 AM\r\n\tStarting drive scan. \r\n\r\n[Normal] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:26 AM\r\n\tDrive scan has completed.\r\n\r\n[Major] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:26 AM\r\n[236:51] \tFailed to resolve a storage volume on the host.\r\n\tStorage volume: DP-2015.11.20-10-056503991\r\n\r\n[Critical] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:26 AM\r\n\tThere are no valid objects left.\r\n\r\n[Critical] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:26 AM\r\n\tSome or all storage volumes cannot be backed up. Session will abort.\r\n\r\n[Critical] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:27 AM\r\n\tThere are no valid objects left.\r\n\r\n[Normal] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:27 AM\r\n\tThe HPE P6000 EVA \/ HPE 3PAR SMI-S agent enabled\r\n\tautomatic mounting of new volumes on the operating system.\r\n\r\n[Minor] From: SMISA@sut74.atlpss.hp.net \"SMISA\" Time: 11\/21\/2015 4:30:31 AM\r\n\tPreparation of the backup system failed.\r\n<\/pre>\n<\/blockquote>\n
What this is telling you is that it cannot find the host sut74.atlpss.hp.net which is our backup system in our example here in this write-up. This is why you MUST have the backup system listed is in FQDN form in the 3PAR.<\/p>\n
Ok, now we have gotten through a few of the housekeeping steps and explained why they needed to be there we have just a couple of more things that we must do to finish this out so everything will work. The only thing left now is to tell Data Protector what 3PAR system to connect to, the userid has the proper permission\u2019s and its password. We will be using two command to accomplish this.<\/p>\n
The first command will be the
omnidbsmis<\/code> and theomnidbzdb<\/code> and will give you examples of the syntax of each.<\/p>\nOur first command we will run is the omnidbsmis, this stores the login information for SMI-S of the storage array provider running on the management system. The syntax is:
\nomnidbsmis -ompasswd -add < ip address of storage array > -user < user name of SMI-S array Provider ><\/code>
\nExample:
\nomnidbsmis -ompasswd -add 10.10.253.134 -user administrator<\/code>
\nAdministrator is typically the default user, names that are user accounts that are part of a domain should be entered in the format username@domain.\n<\/p>\nYou can run the following command to verify what you added worked correctly (the output will look like the below):
\nomnidbsmis -ompasswd -list<\/code><\/p>\n\n
\r\n \t User Host Port Ssl\r\n---------------+--------------------+-----+-----\r\nadministrator@atlpss.hp.net (administrator@atlpss.hp.net) dp9.atlpss.hp.net 5988 No\r\nadministrator sut64.atlpss.hp.net 5988 No\r\n<\/pre>\n<\/blockquote>\n
The next command you will run omnidbzdb and tells the system to execute the administrative task on the 3PAR array, and manages the configuration data of the agents used to connect to the CIMOM providers or to the storage system (this command is available on clients with the Data Protector User Interface installed, so just run it on the cell manager).<\/p>\n
The syntax you will use looks like the following:
\nomnidbzdb --diskarray 3PAR --ompasswd --add < ip address of the storage array > --user < userid of userid with proper premissions > --passwd < password for that user ><\/code>
\nExample:
\nomnidbzdb --diskarray 3PAR --ompasswd --add 10.10.253.134 --user 3paradm --passwd 3pardata<\/code>\n<\/p>\nTo verify you run the following command:
\nomnidbzdb --diskarray 3PAR --ompasswd --list<\/code><\/p>\n\n
\r\n \t User Host Port Ssl\r\n----------------+--------------------+-----+-----\r\n3paradm 10.10.253.166 5988 No\r\n<\/pre>\n<\/blockquote>\n
Once that has been completed you are ready to configure your file system backup in Data Protector using VSS with the 3PAR array.<\/p>\n
This post was prepared and documented by Geoff Rennie<\/b>. Geoff is a Presales colleague in HPE Software – AMS region. Thanks for sharing this content.<\/p>\n","protected":false},"excerpt":{"rendered":"
Setting up a File System backup using ZDB on 3Par is fairly simple, however there are a couple of challenges that you should be aware of, but we will address those later. ZDB backups are made up of basically three machines: Your application server where the file system resides The backup system\/server The 3Par array […]<\/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":[1],"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-L0","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":2914,"position":0},"title":"Data Protector 9 – 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 "DP A.09.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2381,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/09\/step-step-poweron-migrate-from-3par-snapshots\/","url_meta":{"origin":2914,"position":1},"title":"Step by Step: Power On and Live Migrate from 3PAR Snapshots","date":"9. September 2015","format":false,"excerpt":"{:de}Nachdem ich den Artikel https:\/\/www.data-protector.org\/wordpress\/2015\/08\/tested-poweronrun-live-migrate-3par-snapshots-smartcache\/ ver\u00f6ffentlicht hatte, haben einige Leser den Wunsch ge\u00e4u\u00dfert eine etwas ausf\u00fchrlichere Anleitung f\u00fcr die im Data Protector 9.04 eingef\u00fchrte Funktion Power On und Live Migrate von 3PAR Snapshots oder Smartcache zu erhalten. Daf\u00fcr und f\u00fcr die grunds\u00e4tzlichen Konzepte zu Zero Downtime Backup stehen die Guides\u2026","rel":"","context":"In "HowTo"","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":2914,"position":2},"title":"HPE Data Protector 7.0X and 8.0X – 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 "Data Protector Links"","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":500,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/05\/cannot-connect-to-the-scm-omniinetpasswd\/","url_meta":{"origin":2914,"position":3},"title":"Cannot connect to the SCM – omniinetpasswd","date":"9. May 2011","format":false,"excerpt":"{:en}During a push installation of the Data Protector Client to a Windows 2008 box, you may receive following error. In the internet or in the documentation of Data Protector you'll find the needed steps to address this error message. To be complete... it is also posted here. Cannot connect to\u2026","rel":"","context":"In "HowTo"","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":2914,"position":4},"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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1328,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/04\/vmware-backup-nbd-san\/","url_meta":{"origin":2914,"position":5},"title":"VMware backup done over NBD instead of SAN","date":"11. April 2013","format":false,"excerpt":"{:en}Problem: The backup of some virtual machines is done using transport mode NBD instead of SAN, even if it is configured for the virtual machine or a vApp container. There might be other virtual machines on the same SAN disk, which are able to do the backup over SAN. The\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2914"}],"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=2914"}],"version-history":[{"count":21,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2914\/revisions"}],"predecessor-version":[{"id":2940,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2914\/revisions\/2940"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=2914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=2914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=2914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}