Tag Archive: Tricks

Aug 19

Tape drive performance with MTWEOFI on Linux

Physical tape drives are a precious resource in today’s fast growing data centers. If you’re running backups or copies to physical tape drives performance is key. I did some research on this topic based on a customer request. They reported that backups on Windows clients where much faster compared to Linux clients when writing directly …

Continue reading »

Feb 28

Resolve Cell Manager installation failures on RHEL7

Starting with Data Protector A.09.05 Red Hat Enterprise Linux 7.0 and 7.1 is now a supported Cell Manager platform. But running the regular installation procedure on a fresh RHEL 7.1 system does not work, even with all requirements met. [root@linux ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.1 (Maipo) [root@linux ~]# uname -a Linux jetlnx01.godyo.int …

Continue reading »

Jun 11

List non-migrated DCBFs

If you need to deal with non-migrated DCBFs after an upgrade to Data Protector 8 or later, you might find this SQL query useful. It will display all non-migrated DCBFs (dcbf_version = -1) with references in the IDB. Don’t remove the old catalog using perl omnimigrate.pl -remove_old_catalog before all v1 DCBFs have been successfully migrated to v2. The migration …

Continue reading »

May 10

Clean up after Data Protector IDB restore

IDB restore with Data Protector 8 and later is really straight forward. It allows a much more granular recovery than in previous versions, since it’s done using a fully featured module instead of a file system hot-backup. You’re able to restore the IDB (PostgreSQL database) including log file recovery, DCBF files and configuration files individually or all together …

Continue reading »

May 09

Re-initialize Data Protector IDB (PostgreSQL)

This post will show you how to re-initialize the Internal Database of Data Protector 8 or later to start from scratch without the need for re-installation. This was quite simple on previous versions and needs to be adjusted for the new PostgreSQL database and JBoss application server. These instructions will work on Linux and HP-UX. If I find a proper …

Continue reading »

Apr 25

Delete db40\dcbf folder after migration to DP 8.x

If you migrate from a previous version to Data Protector A.08.00 or later on Windows, you might come across an issue where you’re unable to remove the old db40\dcbf directories using GUI or omnidbutil -remove_dcdir. This is most likely caused by the used path separator inside the Internal Database. Since version 8 the path separator …

Continue reading »

Aug 03

Restore from NDMP device mirror

I just came across an issue at customer site where Data Protector Device Mirror was used to duplicate NDMP backups. In general this is a great way to reduce the amount of time it takes to create separate sets of media at backup time. The worse thing is, this feature is not supported in Data …

Continue reading »

Jul 22

Patch Data Protector standalone client

There are cases in with you need to apply GA patches to a UNIX client and you don’t have an Data Protector UNIX IS (Installation Server) available. This is worse, because the patches are designed to update an installation server only. The following procedure will help you out. Instead of applying the patches to an …

Continue reading »

Jul 21

Data Protector requirements for Linux CM / revised

Here are some required, but not well documented requirements for Data Protector Cell Manager (Cell Server) installation on the Linux platform. Update: This information has been revised for SLES11. These steps are not intended to replace the Installation and Licensing documentation shipped with the media kit. Rather they should help you to bring things up …

Continue reading »

Jan 01

Investigating NDMP performance

I spend some time on the Data Protector NDMP Integration, especially to compare it to CIFS/NFS backups available with the regular Disk Agent. Luckily an older EMC Celerra NS20 was available and I was able start immediately. A quick look at the NDMP support matrix revealed no restrictions since the unit was running T5.6.50.203. To …

Continue reading »

Older posts «