HI Thomas,

Thanks here with me, more simplification for my issue understanding, Suppose i have a tape in which almost 10 backups have been backed-up successfully rest of last one "giving mount request" as below:

Status               Backups     Protection         Data Type      Size

Completed      1stbackup    Permanent          full                10GB
Completed     2ndbackup   not protected      incr               1GB
Completed     3rdbackup    not protected      incr               1GB
Completed     4thbackup    not protected      incr               1GB
Completed     5thbackup    not protected      incr               1GB
Completed     6thbackup    Permanent          full                14GB
Completed     7thbackup    not protected      incr               1GB
Completed     8thbackup    not protected      incr               1GB
Completed     9thbackup    not protected      incr               1GB
aborted          10thbackup   permanent          full                5GB

aborted session because of asking mount request. Tape has been full.
Now how can i just remove this aborted session & 6thbackup to get back this 5GB & 14GB occupied space so that my tape can be reuse for next incr jobs.

After updating to Data Protector 9.x environments using the NDMP integration in a clustered configuration may
experience the following behavior:

 [Critical] From: UMA@ma-host.domain.com "LTO4_NETAPP"  Time: 3/21/2017 1:01:30 PM
 [90:59]   mc0
    Cannot open exchanger control device (Device type mismatch)

This is a know issue and is documented in QCCR2A73173. Please contact the support organization to
receive a fix if you are experiencing this issue.

HA!!!!! Had a new client added, Wintel removed DP so we had them resinstall...same version, patches and now we're getting this error.

# omnicheck -patches -host kaci-pwvsql-29
Patch level Patch description
===========================================
DPWIN_00790 Core Component
DPWIN_00790 Core of Integrations component
DPWIN_00792 Disk Agent
DPWIN_00794 User Interface
DPWIN_00657(BDL703) MS SQL Integration
Number of patches found: 5.

Automated delete_unprotected_media does not run since upgrading to 9.08 b113

This is a known issue QCCR2A72426 and is fixed in DP 9.09. 

The workaround in the mean time is to set DeleteUnprotectedMediaParallelism=100 in the global file.

Hi Everyone,

I have a little issue with my tape even after the all backups in the tape has now been "not protected" but still DP is not going to reuse this tape without recycling. Case is as below:

Status               Backups     Protection         Data Type      Size

Completed      1stbackup    not protected      full                10GB
Completed     2ndbackup   not protected      incr               1GB
Completed     3rdbackup    not protected      incr               1GB
Completed     4thbackup    not protected      incr               1GB
Completed     5thbackup    not protected      incr               1GB

Now the tape has been full but not able to overwrite or reuse. How can i do that without recycling the tape?

Hi All,

I restore a image from a server that using DP 7.00 patch 107.

but now our cell manager is DP 7.00 patch 72.

The problem is, when I uninstall windows client(Disk Agent) that using DP 7.00 patch 107 and reinstall a new DP 7.00 patch 72 to windows client.

After reinstall I cannot import this windows client into cell manager.

Cell manager can telnet to windows client 5555 and when install windows client it can receive respont from cell manager.

Cell manager: HP-UX 

How can I solve this problem?

Thanks a lot

Have you tried without fiddling with patches? Often, Data Protector works just fine with differences in patches. In fact, sometimes major version can differ. Just give it a try.

If it still does not work: we do not have crystal balls: we generally cannot solve a problem based on "it does not work". If you ask a general question, you can only receive a general answer. Try to be specific, tell us what your sort of troubleshooting you did etc etc. Paste output of commands/error messages. The exact command and the exact error message would be very helpful.

if all objects on the media are marked as "not protected" what does the media report? Is protection NONE or EXPIRED?

If you have other tapes in the pool or free pool, DP is likely to use others first before using this one.

What allocation policy do you have set? loose?

provide screenshots/attachments to help.

I'm using Data Protector 8.16 (Windows 2008 environment) with Virtual Environment Integration (VMware integration) but vCenter server is changed so I add the new vServer node and I reconfigured VEI.

Problem is to modify the Vmware backup tasks (about 100 ! ) of virtual machines because every task si referencing to old vcenter so I must to create all tasks with the new vcenter reference!

Is there way to replace the old vcenter with the new one inside every task? For example changing some the configuration file specific for every task,

Hello,

that is not possible. You can only use this tape again if all sessions are unprotected.

You need two types of Mediapools. One for the permanent backups, and another one for the incrementel backups which expire after a few days. For that you need two backupjobs with different protection time and mediapools.

Thomas

Hi,

Thank you for sharing. This issue is a general issue, affecting all the environments? The housekeeping job is failing?

When updating DP 6/7 to DP 8/9, these file names are not converted from the old IDB files to the new DCBF files of version 2.
The DP code is able to read these old files, although the old database engine is not installed anymore.
So we have a fully functional IDB after the update and detail file browsing for restore is possible.

omnimigrate.pl -start_catalog_migration

omnimigrate.pl -stop_catalog_migration

omnimigrate.pl -report_catalog_migration_progress

omnimigrate.pl -report_old_catalog

omnimigrate.pl -cleanup

omnimigrate.pl -remove_old_catalog

---

TobiasPätz wrote:

Hi,

The error comes already at the beginning of the start of the backint up:

(ERR: Error starting backup/restore (BMA cannot be started or similar).)

- What error is showing in the session of DP?

- Does a simple file backup of this server works?

- Tried reinstall the DP client software (agents)?

---

I am getting the same error.

 [Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 3/30/2017 1:37:11 PM
 Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

[Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11  Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

[Critical] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11  Failed to start backup of object BSN.-1. Error: Details unknown.

[Critical] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11
 Failed to start backup of object BSN.-1. Error: Details unknown.
Cannot create backup set "Catalog not loaded, message #7583 in set 11"

[Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11  Aborting connection to BSM. Abort code -17.

[Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11
 Aborting connection to BSM. Abort code -17.

Simple File System backup works fine.  Tried uninstalling and reinstalling as well.

It is an HP-UX11.31 client and I am running DP9.08

Hello,

I do not know if all environments will suffer this issue, I do know of two environments that experienced it and I was able to reproduce the issue in my test environment.  Another workaround is to run omnimm -delete_unprotected_media -all

I hope this helps.

SQL BACKUP failing continously. Could any one please help here ,Please check below backup session logs..

[Normal] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:10 AM
Backup session 2017/03/31-39 started.

[Normal] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:11 AM
OB2BAR application on "saldwprd01.salindia.ad" successfully started.

[Normal] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:13 AM

Hewlett-Packard Data Protector Backup and Restore Agent for Microsoft SQL Server

connected to SQL Server version 12.0 on machine DWPRD

Microsoft SQL Server 2014 - 12.0.4100.1 (X64)
Apr 20 2015 17:29:27
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

[Normal] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:13 AM
Character set: Latin1-General
Sort order : case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data

[Normal] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:13 AM
Direct mode is disabled.

[Normal] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:13 AM

Pre-backup database information:

Database name ........: Columnar_DWH
Requested backup type.: transaction log (incremental)
Log backup possible ..: YES
Approx. backup size ..: 1945880 kB
Concurrency ..........: 1

Database name ........: FA_PLUS_ENTERPRISE_DWH
Requested backup type.: transaction log (incremental)
Log backup possible ..: NO
Approx. backup size ..: 843888 kB
Concurrency ..........: 1

Database name ........: FA_PLUS_ENTERPRISE_STAGING
Requested backup type.: transaction log (incremental)
Log backup possible ..: NO
Approx. backup size ..: 216128 kB
Concurrency ..........: 1

Database name ........: bods_repo
Requested backup type.: transaction log (incremental)
Log backup possible ..: YES
Approx. backup size ..: 195256 kB
Concurrency ..........: 1

Database name ........: CMSDB_IPS
Requested backup type.: transaction log (incremental)
Log backup possible ..: YES
Approx. backup size ..: 150800 kB
Concurrency ..........: 1

Database name ........: AUDDB_IPS
Requested backup type.: transaction log (incremental)
Log backup possible ..: YES
Approx. backup size ..: 63232 kB
Concurrency ..........: 1

Database name ........: ReportServer$DWPRD
Requested backup type.: transaction log (incremental)
Log backup possible ..: YES
Approx. backup size ..: 1336 kB
Concurrency ..........: 1

Database name ........: ReportServer$DWPRDTempDB
Requested backup type.: transaction log (incremental)
Log backup possible ..: NO
Approx. backup size ..: 464 kB
Concurrency ..........: 1

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:14 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: BMA@saldwprd01.salindia.ad "B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]" Time: 3/31/2017 1:01:18 AM
STARTING Media Agent "B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]"

[Normal] From: BMA@saldwprd01.salindia.ad "B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]" Time: 3/31/2017 1:01:19 AM
Loading medium from slot \\10.23.250.93\STORE_WIN_SQL\5bfa170a_58dd5d07_04e0_3869 to device B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]

[Normal] From: OB2BAR_Columnar_DWH_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:22 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/Columnar_DWH/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:21 AM
[61:3003] Lost connection to OB2BAR Backup DA named "DWPRD"
on host saldwprd01.salindia.ad.
Ipc subsystem reports: "IPC Read Error
System error: [10053] Software caused connection abort
"

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:22 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_FA_PLUS_ENTERPRISE_DWH_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:24 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/FA_PLUS_ENTERPRISE_DWH/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:23 AM
[61:1005] Got unexpected close from OB2BAR Backup DA on saldwprd01.salindia.ad.

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:24 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_FA_PLUS_ENTERPRISE_STAGING_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:26 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/FA_PLUS_ENTERPRISE_STAGING/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:25 AM
[61:3003] Lost connection to OB2BAR Backup DA named "DWPRD"
on host saldwprd01.salindia.ad.
Ipc subsystem reports: "IPC Read Error
System error: [10053] Software caused connection abort
"

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:26 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_bods_repo_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:28 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/bods_repo/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:27 AM
[61:3003] Lost connection to OB2BAR Backup DA named "DWPRD"
on host saldwprd01.salindia.ad.
Ipc subsystem reports: "IPC Read Error
System error: [10053] Software caused connection abort
"

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:28 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_CMSDB_IPS_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:29 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/CMSDB_IPS/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:29 AM
[61:1005] Got unexpected close from OB2BAR Backup DA on saldwprd01.salindia.ad.

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:30 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_AUDDB_IPS_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:31 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/AUDDB_IPS/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:30 AM
[61:1005] Got unexpected close from OB2BAR Backup DA on saldwprd01.salindia.ad.

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:31 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_ReportServer$DWPRD_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:32 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/ReportServer$DWPRD/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:32 AM
[61:1005] Got unexpected close from OB2BAR Backup DA on saldwprd01.salindia.ad.

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:33 AM
Error has occurred while starting threads.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_ReportServer$DWPRDTempDB_0@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:34 AM
Starting OB2BAR Backup: saldwprd01.salindia.ad:/DWPRD/ReportServer$DWPRDTempDB/0 "MSSQL"

[Major] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:34 AM
[61:1005] Got unexpected close from OB2BAR Backup DA on saldwprd01.salindia.ad.

[Minor] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:35 AM
Thread returned error.
See Data Protector debug.log and SQL Server error log for details.

[Normal] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:35 AM

Database statistics:

--------------------------------------------------------------
--------------------------------------------------------------
[Major] From: OB2BAR_SQLBAR@saldwprd01.salindia.ad "DWPRD" Time: 3/31/2017 1:01:35 AM
Aborting connection to BSM. Abort code -12.

[Normal] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:35 AM
OB2BAR application on "saldwprd01.salindia.ad" disconnected.

[Normal] From: BMA@saldwprd01.salindia.ad "B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]" Time: 3/31/2017 1:01:44 AM
Unloading medium to slot \\10.23.250.93\STORE_WIN_SQL\5bfa170a_58dd5d07_04e0_3869 from device B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]

[Normal] From: BMA@saldwprd01.salindia.ad "B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]" Time: 3/31/2017 1:01:44 AM
ABORTED Media Agent "B2D_WIN_SQL_gw2_SALDWPRD01 [GW 78464:0:4639893430883622270]"

[Critical] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:43 AM
None of the Disk Agents completed successfully.
Session has failed.

[Normal] From: BSM@sapdpprd01.salindia.ad "DWPRD_TRANSLOG_BACKUP_DAILY" Time: 3/31/2017 1:01:43 AM

Backup Statistics:

Session Queuing Time (hours) 0.00
-------------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 8
Aborted Disk Agents .......... 0
-------------------------------------------
Disk Agents Total ........... 8
===========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 1
Aborted Media Agents ......... 0
-------------------------------------------
Media Agents Total .......... 1
===========================================
Throttled Gateways ........... 0
Gateways Total ............... 1
===========================================
Overall Deduplication Ratio .. -
===========================================
Mbytes Total ................. 0 MB
Used Media Total ............. 1
Disk Agent Errors Total ...... 0

I do not think the patch level has something to do with this failure.

Most of the times I have seen this problem it is due to:

1. Another service running on port 5555 on the client. You can check this with netstat -an | strfind 5555. 

If there is such service the telnet will still return HPE INET, but the import will fail. 

In other words: telnet localhost 5555, telnet <Other host> 5555 executed from both CM and clinet should return HPE INET. This is a proof the service is running and listenning on the port.

2. Hostname resolution - DP is very sensitive to this. Check if the CM and the client resolve each other by FQDN - from both execute: ping <FQDN of other host>. If the ping does not work put a record in the hosts file in the following order: <IP> <FQDN> <Short name>. Even if the hosts are resolved with DNS server DP will check the hosts file if the DNS resolution does not work. 

3. It is not clear if this is the only Windows host in the cell, but if you have a Windows Installation Server, try to "Add" instead of "Import". Adding will run an installation session with messages and will give you some idea about the error. Import does not print any messages.

4. Finally DP keeps the name of the Cell Manager in the registry and you can check if it properly put. Very often I have seen the Error: Client is already member of another cell due to the hostname resolution (cell manager resolved by shortname instead of  FQDN). On the CM execute: omnidbutil -show_cell_name and make sure it is the same on the client in: regedit - HKEY_LOCAL_MACHINE - SOFTWARE - Hewlet-Packard- OpenView - OmniBackII - Site.

What I would do is to uninstall the DP from the client and install the client locally. During the installation process you can put the name of the CM and check if it responds. But hostname resolution should work and it is the reason for such failure in 99% of the time.

If nothing helps you can try to check the debugs yourself: execute: omnicc -import_host <HostnameOfClient> -debug 1-500 import.txt

Check the debug directory which is by defaul - for UNIX /tmp and for Win Program Data\Omniback\tmp (I do not think there will be something on the client, but check it anyway).

Search the debugs for the error you are getting and scroll up a bit to hopefully find the reason.

DP 7.xx is not supported for a long time now so swithing to 9.xx will be a good idea.

Good luck.

Sorry for my late answer! I think it works!

thank you!!!!

Hi all!

I would like to ask some help!

We have Data Protector 9.08 with tape library and StoreOnce...

We have lot of VTLs what were created on StoreOnce. Everything worked well untill last week, when i should have created some new connection (on HPUX) to these. I ran an autodiscover for that server, after zoning, but the DP GUI frozen, and must close and restart. I thought the zoning was not proper. I ran another discover on one of server (HPUX) what has already vtls, but the DP cannot find any device. It surprised me because the backups run well, all of VTL what where zoned and connected earlier works. So now i cant change anything, i cant modify any path, but the VTLs works. These servers use the same VTL groups.

I was curious and ran a discover on other server (Win server 2008 R2), what use a different VTL group and it was successfull, all of VTL appeared, backups works.

What could be the problem? What should i check? Could it be OS problem?

I think StoreOnce and its FCs works well!

Thank you!

waht ouput do you get when you rung "devbra -dev" on that hpux host, and also how long does it take to complete? 

ARS synced data to a secondary cell manager is being counted from a license perspective, when it shouldnt be.

Function used to calculated protected data in IDB cannot distinguish replicated objects from foreign cell. 

There is a hotfix QCCR2A73053 available, it adds additional flag for such objects.  Once it's installed any new replicated obects from foreign source cell manager will not be counted towards total protected data in destination cell manager.