How to delete a HP Data Protector StoreOnce Software Deduplication store

In one of my earlier blogposts, I mentioned what you could do when you are confronted with a “corrupted” HP Data Protector software StoreOnce store. Today, we decided to delete the deduplication store to free up the diskspace.

Before a “HP Data Protector StoreOnce Software Deduplication Store” can be deleted, the media retained within needs to be exported. Please note, deleting the store in DataProtector does not mean the Store is deleted in StoreOnceSoftware.

The deletion required a set of steps to be executed. The plan of approach we followed, can be found below.

Continue reading

Recovering a corrupted HP Data Protector software StoreOnce store

In one of the remote sites, the customer is running an HP Data Protector 9.02 environment in combination with a software-based HP Data Protector StoreOnce deduplication store based on a Windows Server 2012.

Unfortunately during the initial installation, the consultant did not implement any anti-virus exclusions causing the software deduplication store to get corrupted last week. Files which got deleted were from the type: “$StoreRoot\**\containerData_*\*.js“.

Magically we were still able to bring the store back online in read-only mode and restore data from it! Thumbs up!

Continue reading

Data Protector report the following error message when executing a barcode scan: “Bad catalog access for message #193 in set 65″

Today we received the following error message in the Data Protector GUI when we performed a barcode scan on a physical tape library: “Bad catalog access for message #193 in set 65“. Yesterday I found some Data Protector foreign tapes which we tried to format, logically we thought these were the root cause of this error message. After exporting them out of the library, we noticed the error stayed.

Eventually we found out this error was caused by a miscommunication between the Cell Manager and the client which has the HP Data Protector GUI installed. These error messages can appear when there is a discrepancy in the Data Protector versions installed.

In our situation, we had the HP Data Protector Cell Manager running on version 9.04 and we were using a Data Protector Console of version 9.02. After patching the console, the error disappeared and we were able to successfully manage the cell again.

Lingo Explained: Block Padding (with HP Data Protector)

The term Block Padding is used in backup to tape environments when there is a need for tape copy and backup mirroring. Tape still remains a sequential medium, using different tracks to store data. Therefore, there are slight variations in the overall capacity of individual tapes. This can pose a significant challenge when attempting to make an exact copy from a tape which is slightly larger than the destination tape. Planning for this eventual issue must be done before the initial tape initialization.

HP Data Protector uses a parameter called “OB2BLKPADDING” in the omnirc file on each system (media agent) connected with a tape device. The parameters’ value defines the number of empty blocks to be added on the specific tape. This empty space allows tape content to be copied to another tape of the same type without any problem as the empty space is not copied from the source.

Continue reading

HP Data Protector Version Discontuance

Today HP announced the discontuance of some HP Data Protector versions. Hereby a table of the last versions and it’s End-Of-Support dates.

Oct 31, 2009 End Of Product Support for HP Data Protector 5.5
Oct 31, 2011 End Of Self-Support for HP Data Protector 5.5
Dec 31, 2014 End Of Product Support for HP Data Protector 6.2x
Dec 31, 2016 End Of Self-Support for HP Data Protector 7.0 & 8.0x
Dec 31, 2014 End Of Product Support for HP Data Protector 6.2x
Dec 31, 2016 End Of Self-Support for HP Data Protector 7.0 & 8.0x
June 30, 2016 End Of Product Support for HP Data Protector 7.0 & 8.0x
June 30, 2017 End Of Product Support for HP Data Protector 8.1x
Dec 31, 2017 End of Committed Support for HP Data Protector 9.0x
June 30, 2018 End Of Self-Help Support for HP Data Protector 7.0 & 8.0x
June 30, 2019 End Of Self-Help Support for HP Data Protector 8.1x
Dec 31, 2019 End of Extended Support for HP Data Protector 9.0x
Dec 31, 2023 End of Self-Help Support with Rights to New Versions for HP Data Protector 9.0x

HP Data Protector: “Cannot connect to the SCM (Service Control Manager) on client: [5] Access Denied

I encountered the following error notification when adding a new client (the first one) to a freshly installed HP Data Protector Cell: “[Critical] [110:1022] Cannot connect to the SCM (Service Control Manager) on client RRE-AD01.testlab.local: [5] Access Denied“.

At first I thought the Data Protector Cell Manager was unable to connect to the client. Eventually I disabled the firewall on both machines, ensured the network connectivity between both systems could be properly established and if the user credentials are correct. Everything matched as expected!

Continue reading

Data Protector backup job throws “Fallback to legacy filesystem backup was not allowed”

Wheb backing-up a Windows Client, sometimes the error “Fallback to legacy filesystem backup was not allowed” occurs. In most cases this is related to the CONFIGURATION object, but recently I noticed this also on the D-drive of a (SQL) server.

[Critical] From: VBDA@client “fqdnoftheclient [/D]” Time: 3/25/2014 8:16:09 AM
Fallback to legacy filesystem backup was not allowed. Aborting the backup.
[Critical] From: VBDA@client “fqdnoftheclient [/D]” Time: 3/25/2014 8:16:09 AM
[81:52] /D Not a valid mount point => aborting.

The software tries to start a backup by using the VSS integration and when this fails it fallbacks to the legacy method. If this is not defined in the backupjob properties, the backupjob will fail with the error mentioned above.

Continue reading

Reset Data Protector Poor Medium

In some cases, a tape can be falsely identified as a poor medium. This can happen if the backupjob was killed by a server reboot or a kill of the BSM.exe process. The poor state withholds Data Protector to use the tape.

The command below gives you the ability to reset the poor medium back to the original state.
omnimm -reset_poor_medium "Medium"

As a best practice note the media identifier (the label) down together with the date when the tape was “reinitialized”.
The purpose is to have a trace-back to see if a certain tape throws this error multiple times. In that situation it’s advised to remove the tape from the library.

Abort an unresponsive Data Protector job

Sometimes aborting a job by using the Data Protector Manager Console does not succeed.
In those situation, follow this procedure:

  • Go to the Data Protector Manager console > Monitor > Session-Id and take a not of the start time.
    [Normal] From: BSM@CellManager.lab.local “FILE_DAILY” Time: 5/23/2013 4:15:05 AM
    Backup session 2013/05/23-13 started.
  • Open a PowerShell Window and execute the following command: “get-process b* | sort-object StartTime | format-table Name,Id,StartTime”
    Name Id StartTime
    —- — ———
    bsm 8532 18/05/2013 4:15:07
    bsm 8996 19/05/2013 5:15:05
    bsm 11672 23/05/2013 4:15:05
  • Execute the following command to kill the process: “stop-process 8532“.

Execute the command “omnistat” or “get-process b* | sort-object StartTime | format-table Name,Id,StartTime” to verify the operation. Restart the Data Protector Management console to clear the monitor in the GUI.

Backup, Restore and/or Migrate HP Data Protector’s Internal Database

There are two ways allowing a backup and restore of the Data Protector Internal Database. The procedures described below can also be used for performing migrations. The internal database is located in the DB40 folder within the installation directory.

The first way is relatively easy: create a backup job in the Data Protector Manager Console and select the Internal Database in the selection tree. The downside of this method is the lack of control where the database is stored (on a tape, but which one? on disk, in a bunch of files!) and how fast can it be restored in case of disaster. If you did not implement any fallback mechanisms, a catalog operation will be required! Needless to say it will take some time to complete.

Dumping the data to disk can come in very handy as a safety copy during maintenance operation such as upgrades, patchings, etc.

Continue reading