To improve the user experience when browsing for articles on data-protector.org, you now can use a shortcut for the domain when entering in your favorite browser. When entering dp.tips into the browser you will be forwarded to https://www.data-protector.org/wordpress. So, you no longer have to enter the long name, you can use the shortcut instead.
On 2016/04/08 Hewlett Packard Enterprise released patch bundle 9.06 for Linux, HP-UX and Windows, it includes important changes and new features. For a complete list, please refer to the patch description.
Some new features:
- VMware GRE Agent in cluster environments
- Support for 3PAR InForm OS version 3.2.2 and updated SMI-S agent
- Improved total data protection calculation
- Support for Storage Optimizer 5.2
- Introduction of Telemetry (collect additional information regarding host OS, DP components and versions, devices and media, schedules, and licenses
- Support for VDDK 6.0.2 and SAN transport mode
It is strongly recommended to read the full description of the bundle.
If you own a valid support contract you can download the patches from https://softwaresupport.hpe.com. For login you need the HPE Passport account.
Did you know? When you received a hotfix for a previous Data Protector (minor) version, you should make sure the hotfix is included in the patch bundle before applying the patch bundle. This is recommended for customers which may have received the hotfix right before the release of the patch bundle. If your hotfix is not included in the patch bundle open a software case and ask for assistance.
With friendly permission of HPE under https://www.data-protector.org/wordpress/whitepaper Data Protector whitepapers are listed. For some whitepaper a Passport Account may required.
Update 2016-04-04: added 2 new whitepaper.
It is often found during the backup of virtual machines that performance of a backup job is disappointing. This is not necessarily a Data Protector issue, usually it is a sign for bottle necks in the IT environment you want to fix. At this point HPE can support with the so called Cloud Optimizer solution.
HPE Cloud Optimizer 3.0 (formerly known as Virtualization Performance Viewer / vPV) is the ideal solution for performance monitoring of business services in a virtualized environment, private cloud or hybrid environments. HPE Cloud Optimizer detects and corrects performance issues in virtualized and physical environments. Moreover Cloud Optimizer helps you in planning and optimizing VM capacity.
This solution has been continuously extended, from a pure monitoring tool to a feature-rich solution addressing virtual and cloud environments, offering “what-if” analysis capabilities and supporting optimization of IT environment for new and existing workloads.
HPE Cloud Optimizer can be integrated with other solutions such as e.g .: HPE Cloud Service Automation (CSA HPE), HPE OneView and HPE Operations Manager i (HPE OMi).
Interested in HPE Cloud Optimizer?
For a first impression check: https://www.youtube.com/watch?v=nSTVC-4eozE
A 60-day trial version is available via the following link: https://saas.hpe.com/buy/cloud-optimizer?utm_source=hp.com&utm_medium=referral&utm_term=vpv&utm_content=buy_flow&utm_campaign=hp.com_redirects%20
If you are interested in some additional information regarding HPE VM Explorer, please find below some articles and the download link.
Links to VM Explorer:
On 2016/02/29 Hewlett Packard Enterprise released the latest patch for Backup Navigator 9.30. Hence, the new version 9.31 includes important changes and new features. As requirement you need to have version 9.30 installed. For a complete list please refer to the description. HPE Backup Navigator is the reporting tool for HPE Data Protector.
Information regarding the new version and the patch can be downloaded here https://softwaresupport.hp.com. For login you need the HP Passport account.
A new great article from Jim regarding HPE Data Protector and Granular Recovery Extension for VMware 6. A really good howto, worth to read.
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 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.
By definition a Smart Cache is as follows:
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:
- NAS share (CIFS and NFS)
- Disk (SAN, iSCSI, local) formatted with file system
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.
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.
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.
You will be prompted to verify are you sure you want to do this, you would type “Y” for yes as in the screen shot below.
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
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
Once you have the device created you simply run your VM integrated backup with this device as your target.
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.
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
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.
The restore session will look something like the screen shot below
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.
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).
This post was prepared and documented by Geoff Rennie. Geoff is a Presales colleague in HPE Software – AMS region. Thanks for sharing this content.
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
These are noted in the figure below highlighted in yellow
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.
Now that you have an idea of how this works, let’s 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:
- HPE 3PAR VSS Agent
- HPE P6000 /HPE 3PAR SMI-S agent
- MS Volume Shadow Copy Integration
- Disk Agent
- Media Agent especially on the Backup System
Comment: The Application system and Backup system should NOT be the same server, also they both must be running the same OS.
How to setup the environment and commands to run to get the system ready
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.
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.
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 “see” the array.
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’s alias MUST be the FQDN of its self (see screen shot below).
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.
Now 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.
Now 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.
[Minor] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:29:55 AM [236:9210] A SMI-S call to the array did not behave as expected. Failed volume: DP-2015.11.20-10-056503991 Returned message: Error retrieving StorageID = HBA WWN of host sut74.atlpss.hp.net. [Normal] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:29:55 AM Starting drive scan. [Normal] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:26 AM Drive scan has completed. [Major] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:26 AM [236:51] Failed to resolve a storage volume on the host. Storage volume: DP-2015.11.20-10-056503991 [Critical] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:26 AM There are no valid objects left. [Critical] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:26 AM Some or all storage volumes cannot be backed up. Session will abort. [Critical] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:27 AM There are no valid objects left. [Normal] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:27 AM The HPE P6000 EVA / HPE 3PAR SMI-S agent enabled automatic mounting of new volumes on the operating system. [Minor] From: SMISA@sut74.atlpss.hp.net "SMISA" Time: 11/21/2015 4:30:31 AM Preparation of the backup system failed.
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.
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’s and its password. We will be using two command to accomplish this.
The first command will be the
omnidbsmis and the
omnidbzdb and will give you examples of the syntax of each.
Our 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:
omnidbsmis -ompasswd -add < ip address of storage array > -user < user name of SMI-S array Provider >
omnidbsmis -ompasswd -add 10.10.253.134 -user administrator
Administrator is typically the default user, names that are user accounts that are part of a domain should be entered in the format username@domain.
You can run the following command to verify what you added worked correctly (the output will look like the below):
omnidbsmis -ompasswd -list
User Host Port Ssl ---------------+--------------------+-----+----- email@example.com (firstname.lastname@example.org) dp9.atlpss.hp.net 5988 No administrator sut64.atlpss.hp.net 5988 No
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).
The syntax you will use looks like the following:
omnidbzdb --diskarray 3PAR --ompasswd --add < ip address of the storage array > --user < userid of userid with proper premissions > --passwd < password for that user >
omnidbzdb --diskarray 3PAR --ompasswd --add 10.10.253.134 --user 3paradm --passwd 3pardata
To verify you run the following command:
omnidbzdb --diskarray 3PAR --ompasswd --list
User Host Port Ssl ----------------+--------------------+-----+----- 3paradm 10.10.253.166 5988 No
Once that has been completed you are ready to configure your file system backup in Data Protector using VSS with the 3PAR array.
This post was prepared and documented by Geoff Rennie. Geoff is a Presales colleague in HPE Software – AMS region. Thanks for sharing this content.
On 2016/02/29 HPE released new patches for Linux, Windows and HP-UX (build 106). This is not the patch bundle 9.06. As a requirement you need to have Patch Bundle 9.05 installed. It is strongly recommended to read the full description of each patch.
If you own a valid support contract you can download the patch from https://softwaresupport.hp.com. For login you need the HP Passport account. Please keep in mind to install the patches in correct order – see https://www.data-protector.org/wordpress/2013/06/basics-installation-order-patches/
Another article on how cross cell replication is working in HPE Data Protector. Jim wrote and posted this nice document.
With version 9.04 a new feature was introduced in HPE Data Protector – cross cell replication – the replication of catalyst objects between different cells and HPE StoreOnce appliances (including VSA). A practical demo on how it works and what to configure can be found in the video.
Searching for the current HPE Data Protector Support Matrices? Sometimes you need to access the Support Matrices to check whether a particular operating system or integration is supported in HPE Data Protector.
The matrices are updated every month and you can find the latest versions using “Product Information” –> “Matrices” on Software Support – https://softwaresupport.hpe.com.
To access the Support Matrices, you need a Passport Account, the direct links are listed below.
On 2016/01/29 HPE released new patches for Linux, Windows and HP-UX. As a requirement you need to have Patch Bundle 7.03 installed. It is strongly recommended to read the full description of each patch.
If you own a valid support contract you can download the patch from https://softwaresupport.hp.com. For login you need the HP Passport account. Please keep in mind to install the patches in correct order – see https://www.data-protector.org/wordpress/2013/06/basics-installation-order-patches/.
As Data Protector 7.0X will become “End-of-Live” this summer, please consider to plan for a migration to current version.