This applies to upgrades from Data Protector 6.x and 7.x to 8.x and 9.x.
It seems that today is my debugging day… Yesterday I performed a Data Protector update from 7.03 to 8.13. During this update, the Data Protector IDB is migrated to another database format. Last night the backups went smoothly, but today I noticed that two old Detail Catalog Binary File (DCBF) directories were still referenced in the HP Data Protector IDB.
Sometimes the easy jobs seems to be the hardest. Especially if you have to deal with high-quality software… As part of a project I had to install and configure a HP StoreOnce 4500 appliance in combination with HP Data Protector 8.12 and a StoreEver MSL2024 G3 tape-library. No big deal - until I hit the part, when I had to install HP StoreOnce Enterprise Manager v1.3 (SEM) on the new backup server.
The recovery of an Exchange mailbox using a recovery database is usually no big deal. Simply restore the database, create a recovery database and recover the mailbox or items from the mailbox. Sometimes you have the luck that the customer has licensed the Data Protector Exchange 2010 Granular Recovery for Exchange (GRE). This was unfortunately not true in my case. Okay, so let’s do it the old way. The needed tape was available in the library and luckily it was a full backup.
HP StoreOnce Catalyst is an enterprise-wide deduplication algorithm which is used in HP StoreOnce appliances, HP StoreOnce VSA and HP Data Protector. With StoreOnce Catalyst, deduplicated data can be moved between Catalyst capable devices without the need to rehydrate the data. Think about the backup in your remote location. You can move the deduplicated data to your central StoreOnce appliance in your HQ without rehydrating the data. This saves bandwidth and time.
HP StoreOnce Appliances or VSA offers three different types of backup destinations:
Virtual Tape Library (VTL) NAS (CIFS or NFS) StoreOnce Catalyst If you use Veeam Backup & Replication, the NAS feature is possibly worth a try. Using the NAS feature, the StoreOnce appliance or VSA offers a CIFS or NFS share, which can be used as a backup destionation. Today I want to show you how you can use a NAS share of a StoreOnce VSA with Veeam Backup & Replication.
In part I of this series I showed you the download and the deployment of the HP StoreOnce VSA. Part II showed you the configuration of two libraries and the connection of the backup server to this two tape libraries. Part III of this series covers the configuration of devices and meda pools in HP Data Protector 8.1. This article will not show the installation of HP Data Protector 8.1.
The HP StoreOnce VSA is a virtual storage appliance, that is designed for backups between 1 TB and 10 TB and it’s based on HPs StoreOnce technology. I wrote a short overview about the HP StoreOnce VSA some weeks ago. Take a look at this blog posting if you are not familiar with HP StoreOnce VSA. This article is focuses on the deployment of the HP StoreOnce VSA in a VMware vSphere environment.
In part I of this series I showed you the download and the deployment of the HP StoreOnce VSA. But without further configuration, it’s only a VM that has 4 vCPUs, 16 GB memory and ~ 1,5 TB of disk space. Pretty much for a VM that can’t do anything for you. ;)
Creating a library Open a browser and open the StoreOnce Management Console.
Username: Admin Password: admin
Patrick Terlisten/ vcloudnine.
A side effect of data growth is the growth of the amount of data that must be backed up. The path of least resistance is buying more disks and/ or tapes. Another possible solution is data deplucation. With data deduplication you can’t reduce the amount of data that must be backed up, but you can reduce the amount of data that must be stored. HP StoreOnce Backup is HPs solution to address this problem.
Sometimes it’s necessary to backup system, that are behind a firewall. A good example for this are servers in a DMZ. When using HP Data Protector there are some things to know and consider, before you can backup systems behind a firewall. Lets start with some basics.
The components Cell Manager: The Cell Manager (CM) is the backup server itself. It controls the whole enviroments, stores the licenses, clients, media, devices, backup specifications etc.
