Quantcast
Channel: All Data Protector Practitioners Forum posts
Viewing all 10494 articles
Browse latest View live

Re: Data Protector backup impossible with error 61:1005

$
0
0

You really haven't given us much to go on here.  What type of backup are you doing?  For example is it a File system backup, and Applications Integration backup, a VMware backup, something else?  What is teh full text of the error?  You can edit it to take out specific machine names

 

The snippet you included indicated a segmentation fault, which means a Core file was probably created.  It is coming from the VBDA (Disk  Agent) module.  I did find one lab case with the 'libc-2.12.so' error, but that was for DP 7.0 and was coming from the Media Agent.  This was resolved by getting current with patches

 

I found a fix when doing a VMware backup which was implemented in the 6.21 patch bundle.  There were a lot of fixes made in this patch bundle, and, if you are oly on 6.20, I would recommend that you upgrade to 6.21, and install subsequent patches

 

I suggest that, if you are not on 6.21, to download the patch bundle from

 

http://support.openview.hp.com/selfsolve/patches

 

You will need to have a UNIX-based (HPUX, Linux or Solaris) Installation server to download this patch bundle.  Get teh bundle installed, and also download the subsequent patches that you will find on the same site.  For this issue, I recommand that you download and install at least the Core and Disk Agent patches


Re: There is no more space available in any of the Detail Catalog directories.

Re: Data Protector backup impossible with error 61:1005

$
0
0

Hi Bob,

 

Sorry for too poor information from me.

It is a File system backup in incremental (incr).

 

 

This is the session output :

===

[Normal] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:00:05
Backup session 2014/04/03-3 started.
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:00:10
STARTING Media Agent "LTO4_2"
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:00:15
Par : UMA@bkpinst.domain.com@Changer0:0:1:1
Loading medium from slot 68 to device Tape1:0:1:0C
 
[Normal] From: VBDA@myhost.domain.com "/exports/home"  Time: 2014-04-03 01:01:35
STARTING Disk Agent for myhost.domain.com:/exports/home "/exports/home".
 
[Major] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:02:07
[61:1005]   Got unexpected close from VBDA on myhost.domain.com.
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:05:12
Tape1:0:1:0C
Medium header verification completed, 0 errors found.
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:05:32
Par : UMA@bkpinst.domain.com@Changer0:0:1:1
Unloading medium to slot 68 from device Tape1:0:1:0C
 
[Normal] From: BMA@bkpinst.domain.com "LTO4_2"  Time: 2014-04-03 01:05:52
COMPLETED Media Agent "LTO4_2"
 
[Critical] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:05:52
None of the Disk Agents completed successfully.
Session has failed.
 
[Normal] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:05:52
 
Backup Statistics:
          
Session Queuing Time (hours)         0.00        
-------------------------------------------      
Completed Disk Agents ........          0          
Failed Disk Agents ...........          1          
Aborted Disk Agents ..........          0          
-------------------------------------------      
Disk Agents Total  ...........          1          
===========================================      
Completed Media Agents .......          1          
Failed Media Agents ..........          0          
Aborted Media Agents .........          0          
-------------------------------------------      
Media Agents Total  ..........          1          
===========================================      
Mbytes Total .................       0 MB        
Used Media Total .............          0          
Disk Agent Errors Total ......          0    
===
 
 
 
 
This is the 61:1005 error description
===
[Major] From: BSM@bkpinst.domain.com "homes"  Time: 2014-04-03 01:02:07
[61:1005]      Got unexpected close from VBDA on myhost.domain.com.
 
The agent or monitor did not properly terminate. There are 
several probable causes. First is, that the process was killed by user 
or administrator of the machine, second, that there was not enough memory 
for the agent to complete the backup. 
===
 
 
Ok, I try patches.
Thanks for your help.

Re: Data Protector backup impossible with error 61:1005

$
0
0

Before you apply patches, check the Disk Agent server 'myhost.domain.com', and run a 'ps -ef | grep omni' to see if there are any hanging 'vbda' processes (or any other process for that matter, the 'ps -ef' should return only the 'grep').  If you find any, go ahead and kill them, you may need to use 'kill -9'

DP - Support Tip - StoreOnce Error

$
0
0

When attempting to backup to StoreOnce device, getting error

 

[Major] From: RMA@mysys.local"D2D_File_gw3 [GW 3348:0:2642608089]" Time: 7/10/2013 10:18:14 AM

[90:54] \\172.xx.yy.40\FileSystems\7e6011ac_51d73b17_0a54_0003
Cannot open device (JSONizer error: Device read failure)

 

A test binary QCIM2A47037 was installed, and the error changed to

 

RMA: Bad catalog access for message #48 in set 90

 

When this was interpreted by 'omnigetmsg', it translates out to

 

[90:48] Medium is corrupted, trying to reconstruct


This was caused by the fact that there was a StoreOnce error in the Backup that corrupted the StoreOnce media

 

The media in question was 1411476966 KB (approximate 1.4 TB), and after the message

        [90:48] Medium is corrupted, trying to reconstruct.

 

the backup job appears to hang.  This is not really the case.  The media is being reconstructed at a rate of about 20GB/hr, so, in this case, the process took about 70 hours to complete

 

The session had been terminated, and the Restore was planned to allow time for this to finish, and to stop 'omnitrig' from starting any more backups.  Eventually, it finished, the media was recontructed, and the Restore was done successfully

Data Protector 8.1 for Online VM Backup in RHEV 3.1

$
0
0

Hi,
Is possible to use Data Protector 8.1 for Online VM Backup in RHEV 3.1?

Thanks

DP 6.11 + LTO5 Drive/Tapes [90:6109] Medium does not support encryption,

$
0
0

Hi there,

I have this problem and is imperative for me to solve it quick.

 

Win2003 +DP6.11 + IBM TS3200 library with LTO5 ULT3580-HH5 drives. Every thing looks ok and works fine without drive based encryption.

Now is required to make encrypted backups.

I have enabled Application controlled encryption on the IBM TS3200 library.

I remove the device and added again to DP using autoconfigure device. Drive based encryption can be selected on drive properties>Settings>Advanced.

I have configured global to use same key for all backups. Key was generated using omnikeytool.

I use LTO5 tapes. 

When I try to make an drive based encrypted backup I receive following error:

[90:6109] Medium does not support encryption, please use encryption supported medium.

 

Is imperative to have encryption on these backups.

 

Same type of library and drives, connected to a Windows 2008R2 + DP 8.1(evaluation) can make drive based encryption backups.

I cannot use that configuration because I do not know when my DP8.1 licenses will arrive.

 

 

Any suggestion is welcome.

 

Thank you  

 

Re: Data Protector 8.1 for Online VM Backup in RHEV 3.1


Re: DP 6.11 + LTO5 Drive/Tapes [90:6109] Medium does not support encryption,

$
0
0

According to the DP 6.1x device support matrix

 

http://support.openview.hp.com/selfsolve/document/KM718727

 

pg 42

 

AES encryption is not supported for the TS3200 tape library

 

I looked at IBM drives individually, pp 9-11, and it appears that only these drives support AES encryption

 

IBM Ultrium TS1040 Ultrium-4 with AES Encryption Support
IBM TS2240 Half Height LTO Gen 4 Tape Drive (SAS) with AES Encryption Support
IBM Ultrium TS2340 Ultrium 4 with AES Encryption Support

 

as you can see, no mention of Ultrium 5

 

DP 6.11 is also well out of support

Re: VEPA backup issues with DP 7.0

$
0
0

Hi DennisBSE,

 

It is not true what you were saying, CBT should be working and it's fully supported by DP7.01, in fact, there is a 7.03 patch bundle on the streets allready.

 

In my envoronment it works flawlessly, CBT enabled took only used space, doesn't matter if my VMs has thin, thick or whatever kind of vdisk.

 

Let me know if you have any questions I could help

 

Regards

Re: Schedule Job via DP runs into Timeout. But which timeout?

$
0
0

Thank you for your answer.

I´ve implemented the script as post script.

Means DP will backup nothing, just execut the script.

 

But one question. Some of our DB´s are bigger than 2 TB. The Validation Job runs 10 hours and more.

Does this mean, i have to set the ScriptOutputTimeout to 600 and more?

Does this timeout ignore the output of my script:"in progress" ?

I thought the timeout will check the output every 10 minutes and will reverse the timeout?

 

 

Recover lost backup session

$
0
0

I am trying to find a backup session that I had run in Jan month.

But when I got to Internal Database, the session could be found.

Wat could be the reason ? How can I recover it /

Re: Recover lost backup session

$
0
0

can you see older sessions or are all sessions older than 3 months not visible in the restore? how are you doing the restore. in dp gui under restore, do you browse it within "restore objects" or "restore session". Because if you use restore objects per default it shows only versions from the last 3 months. you can change that in the dropdown "search interval"

 

if you just cant see just this one restore session, maybe the catalog protection was set not long enough or the session was manually removed. then you have to re-import the media from the corresponding backup session

Re: Schedule Job via DP runs into Timeout. But which timeout?

$
0
0

The ScriptOutputTimeout is a one-time, finite value.  You can set this to be as high as you need it, but, if the script does not conclude in that time period, you will get the timeout error.  There is no periodic checking

 

If you are running this as a Post-exec script, the actual backup should have completed before it starts, but the sessin will show as 'In Progress' until the Post-exec script finishes

Re: Recover lost backup session

$
0
0

First, check how you have Properties set for viewing Sessions in the Internal Database.  In the IDB context, right-click on Sessions, and pick Properties, and make sure that these fields are set

Created In:  <All Sessions>

From Type:  <All Sessions>

 

I got caught by this once before I know what it was all about, drove me crazy

 

If the Properties are set correctly, then use the command line to find out if the session is there

 

   omnidb -session -type backup -since [date] -until [date]    Do not include teh [   ] marks

 

For '-since', I would use the day before the backup, and for until, I would use the day after the backup, so, for example

 

  omnidb -session -type backup -since 2014/03/20 -until 2014/03/22

 

You can also use the 'omnirpt' command

 

  omnirpt -report list_sessions -timeframe 2014/03/20 00:01 2014/03/22 23:59

 

and, if you know the name of the backup specification, you can filter the results to include only these backups

 

  omnirpt -report list_sessions -datalist "[backup job name]" -timeframe 2014/03/20 00:01 2014/03/22 23:59

 

If neither of these finds your session, then, I would say that there is a fair chance that the media was ever-written, and the original backup is gone.

 

You can also examine the 'media.log' file (you didn't specify what OS your cell manager is on, so, I can't be more specific), find the daye the backup was made, each line should include the name of the Backup specification.  This will identify what media was used for thsi backup.  If you can find the media, it can be imported into the IDB, restoring your session information


Image backups of SQL db servers

$
0
0

Hi all,

 

I had a conversation this morning with an infrastructure colleague who's opinion was that it can be damaging to sql db, ie cause corruption, for data protector image backups (or any image backups I assume) to be run on an sql server.

 

Has anyone here got any experience or evidence of this?

 

I'd be very interested to find out,

 

cheers all,

 

Steven

Federated deduplication not working

$
0
0

I'm using HP Data protector 7.0.3 with StoreOnce VSA appliance and I've created two Catalyst Stores within VSA, and mapped them to B2D devices in HPDP.

 

I backed up data to one of the B2D devices and then created a post execution copy operation on the backup specifications to copy data from one device to the other. Based on the VSA documentation, the replication between these devices should be federated, which means it should copy data without rehydratation.

 

The problem is, I looked at the copy job statistics in the VSA management GUI and I'm not sure if the copy is being federated. The statistics says the "Source Item Copy Size" and "Data Size" are the same. It appears the Source Item Copy Size is the actual size of data without deduplication, and that is fine, but i believe the "Data Size" value should be smaller than the Source Item Copy Size so that it would copy data without rehydratation. Is there any way to confirm if the federated deduplication is really occuring? How can i determine this based on the copy job statistics? If it's really not happening, how can I resolve this problem?

hpdp-as not starting - Cell manager Linux 6.3 server

$
0
0

I created a cell manager on Red Hat 6.3 using DP 8.1.

I am running in 2 issues and will appreciate any help:

 

1. the hpdp-as process is not starting (attached)

2. I am using my Windows 7 systemas client to access the DP Cell manager and getting the insufficient permission message. I modified the UserList file to open access for everything (*)

 

Thnx

Re: hpdp-as not starting - Cell manager Linux 6.3 server

$
0
0

Problem #2 first

 

To fix customer case, there might be many, follow the following procedure:

  • Find in /etc/opt/omni/client/components/webservice.properties the keystore password
  • cd to /opt/omni/sbin directory
  • regenerate the certificate using the following command:
  • perl omnigencert.pl –server_id <FQDN of your server> -user_id hpdp -store_password <Your keystore password> -cert_expire <number of days less than 24 * 365>
  • omnisv stop
  • omnisv start

Alternatively, for now, just search the perl script 'omnigencert.pl'  for '24 * 365' and replace it with '10 * 365'.

 

There is going to be a corrected version of  'omnigencert.pl '

 

================

 

Problem #1 was found in quite a few lab cases.  Mostly, they provided no eal information, but, there were some suggestions to remove DP from thei server, delete all the DP directories, and reload.  I don't know what your situation is with your Configuration directory or the IDB, I can send the instructions if you want, but, I am really not liking this possibility

 

On the bright side, I found at least one instance where the fix for #2, also fixes to eproblem for #1

 

Re: hpdp-as not starting - Cell manager Linux 6.3 server

$
0
0

Hi Bob,

Thanks for reply. It is a test environment.

1. I m using my laptop as client where I installed the client from DP81 Windows image, it trye to connect the cell manager, first it asks for the login name and password, I used root and hpdp as user and then after few seconds I get the 'insufficient previledge ' message

 

2. I will try your recommendation for the second issue. do you think I need 8.11 patches?

 

Can i contact you at Lync?

 

Saeed Hashmi

Viewing all 10494 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>