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

Virtual Tape Ejected, unable to find it

$
0
0

Dear forum members,

I've configured HP Data Protector 9 with AWS (Amazon Web Services).

In AWS I created two tapes.

When I finished to configured HP Data Protector, I could see both tapes in my slots.

But I clicked on one tape, and right button -> Eject.

The tape was gone, and althougt I select Instert, It did not find the tape.

 

I receive this message from Data Protector:

[Warning] From: UMA@bckcentos01 "bckcentos01" Time: 15/12/2016 13:06:31

Mailslot(s) is (are) empty. Waiting for mailslot(s) to get filled.

 

 

But I do not know how to find and move the tape.

Do not kow where it goes.....

 

Could you help me?

Many thanks in advance,

 

 


Re: Virtual Tape Ejected, unable to find it

$
0
0

I do not know AWS. But eject basically means you're ejecting it out of the slot. So, the way to get it back is either to import it from a mailslot, but assuming AWS may not provide that, you would need to put it back into the slot from the AWS side.

Making sense?

Koen

HP DP 9 - SAN backup of vmware - Enable MPIO for fiber channel to LUNs?

$
0
0

In a LAN-Free backup of a windows box, the storeonce isnt detected as an MPIO device.

I am setting up a backup proxy for SAN backups of vmware. The prox will see the LUNs on the 3PAR and see multiple paths. Do I install and configure MPIO or will the data protector agents handle multipathing?

AIX 7.1 HP DP A.09.0x Data Protector Client Installation - How to add client to a cell

$
0
0

Hi,

i have the task to install the HP DP client for AIX 7.1 systems. We have the aim to install the client software in one step and in a second step adding the client to its corresponding HP Cell.

Meaning: In the first step we just install the software like:

./LOCAL_INSTALL/omnisetup.sh -install da,cc

and in a second step the node will be added to the HP DP Cell like:

/usr/omni/bin/omnicc -import_host <MyBackupName>

 

Problem: How do i let the HP DP client know which Backup Server it shell use ?  Do i have to run a

./LOCAL_INSTALL/omnisetup.sh -server MyBackupServer

beforehand ?

 

tia

Hajo

AIX 7.1 HP DP A.09.0x Client Installation - some generic questions

$
0
0

Hi

Some generic questions regardings the installation of the HP DP A.09.0x client

  1. As far as i have found on this forum, patching from a nfs mounted share is not supported ? Is this still correct ?
  2. What are the at least components to install on a client ? ( da or da + cc )  ( minimum installation ) and how do i add components afterwards.
  3. Does anybody has got the man pages working on AIX ?

tia

Hajo

Re: AIX 7.1 HP DP A.09.0x Data Protector Client Installation - How to add client to a cell

$
0
0

unfortunately there isnt a command to add the client to a particular cell manager.

A possible way is this....

echo cellmanager.domain.org > /etc/opt/omni/client/cell_server

omnicc -import_host localhost.domain.org

that could work.....

Re: AIX 7.1 HP DP A.09.0x Client Installation - some generic questions

$
0
0

I will try and answer your questions....

1. if you are patching a client directly (ie. not from the cell mgr via an installation server) then you can "cd" to the NFS mount and run the omnisetup.sh against a bundle patch or install an individual DPLNX patch with rpm

2. least component install is DA. To add more components later, best to do so via cell manager and installation server. omnisetup.sh could be used but it might moan about patching levels as you've already install DA and patched it.

3. see the commandline reference doc file which comes with DP....

Re: AIX 7.1 HP DP A.09.0x Data Protector Client Installation - How to add client to a cell

$
0
0

sorry you can use omnisetup.sh....

# omnisetup.sh -server cellmanager.domain.org -install da


(DP) Support Tip Exchange DAG integration fails with topology error message

$
0
0

Trying to integrate DAG Exchange environemnt error message is received.

Unable to browse instance.  Didn't found server node1.local.com in existing topology.

[ 99] 2016-12-09 15:12:43.998 ("$PATH: integ/exch2010/ExchangeAgent.cpp $ $Rev: 50245 $ $Date:: 2015-10-10 13:15:02 -040":1720)
[ 99] <<=== (3) } /* CExchangeAgent::ReportGetTopObject */
[ 99]
[ 30] [CExchangeAgent::ReportExchangeTopology] Didn't found server node1.local.com in existing topology.

[ 4] 2016-12-09 15:12:43.998 ("integ/exch2010/ExchangeAgent.cpp $ $Rev: 50245 $ $Date:: 2015-10-10 13:15:02 -040":723)
[ 4] [MARK 2] in CExchangeAgent::ReportExchangeTopology:723
Code: 8102

It is due Exchange nodes are resolving itself by TCP V6 instead TCP V4

Pinging node1.local.com [fe80::6177:8893:2ff0:c827%12] with 32 bytes of
data:
Reply from fe80::6177:8893:2ff0:c827%12: time<1ms
Reply from fe80::6177:8893:2ff0:c827%12: time<1ms
Reply from fe80::6177:8893:2ff0:c827%12: time<1ms
Reply from fe80::6177:8893:2ff0:c827%12: time<1ms

For to resolve issue disable TCP V6 or add entry into host file for to use TCP V4

Best Regards

Re: Data Protector 9.08 Digital signiature problems during upgrade of windows 2003,2008

$
0
0

I am seeing this issue with a Windows 2008 R2 box as well.  Same errors...

[Critical]<test> [70:32] Digital Signature verification of the install kit failed.

[Critical]<test> [70:32] Digital Signature verification of the install kit failed.

[Critical]<test> Cannot start setup process from the Data Protector share on

your Installation Server, system error:

[87] The parameter is incorrect.

(System error should give description of the problem.)

In general:

* Make sure that Data Protector share on your Installation Server is visible on the network

(in MS-DOS prompt on client type: dir \\<IS_COMPUTER_NAME>\OmniBack)

* Make sure that Data Protector Inet process is not running under a user account, which does

not have access to the Data Protector share on the Installation Server computer

(usually this is local account) 

[Critical]<test> [110:1026] Lost connection to client test1:

Details unknown.

 

Backup for "/CONFIGURATION" of almost all the clients in a cell manager failing with VBDA timeout.

$
0
0

Hello everyone

In a cell manager, backup of "/CONFIGURATION"  of all clients failing with VBDA timeout error:

[Major] From: BSM@XXXXX  "XXXXX" Time: 12/15/2016 1:00:46 AM
[61:1002] The VBDA named "XXXXX [/CONFIGURATION]" on host XXXX
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown.

I suspect that there might be some issue from cell manager side because this error is coming for all the clients., please correct me if I am wrong.

If anyone else faced this issue before, please suggest how to fix it.

Cheers!!

Re: Backup for "/CONFIGURATION" of almost all the clients in cell manager failing with VBDA timeout.

$
0
0

Hi All

I have tried below things:

1) Rebooted cell manager.

2)Restarted inet/VSS on clients.

3) Killed hung VBDAs on client

In the backup session initialy some data is written and then it is idle for some time. At last it fails with same VBDA timeout error.

It would be great help if someone could suggest some solution.

Response awaited!!

Re: Backup for "/CONFIGURATION" of almost all the clients in a cell manager failing with V

$
0
0

Hello

Please let us to know DP version an list of pacthes installed.

Best Regards

Re: Virtual Tape Ejected, unable to find it

$
0
0

Thanks, thats right.

 I've found the solution.

I did the eject yesterday, and I did not see any change in my AWS Gateway.
It shows two tapes.

I've entered my AWS Gateway just before to post this message, and I could see that I have only one tape.
I went to tape tab, and I could see my two tapes.

I retreive it, and I have this message:
You have successfully initiated retrieval of the tape AMNZ617DC4.

It takes about 24 hours for the retrieval to complete.

 

So, I think that all will be fine tomorrow.
Sorry and many thanks.

Re: Backup for "/CONFIGURATION" of almost all the clients in a cell manager failing with V

$
0
0

Hi 

Thank you for the response. Below are the requested details:

DP Version:

[root@XXX tmp]# omnidbcheck -version
HP Data Protector A.08.10: OMNIDBCHECK, internal build 206, built on Wed 10 Dec 2014 08:57:54 PM CST
DONE!

Patches:

[root@XXXX tmp]# omnicheck -patches
[12:1604] Cannot reach the CRS on the Cell Manager system.
CRS on the Cell Manager host is not reachable or is not up and running.
System error: [104] Connection reset by peer

Dont know why it is showing that CRS down, all the DP services are up and running!!!!!

[root@XXXX tmp]# omnisv -status
ProcName Status [PID]
===============================
crs : Active [31053]
mmd : Active [31051]
kms : Active [31052]
hpdp-idb : Active [30948]
hpdp-idb-cp : Active [31027]
hpdp-as : Active [31141]
omnitrig : Active
Sending of traps disabled.
===============================
Status: All Data Protector processes/services up and running.

This is really weird as the server was rebooted 4 hours back and services are up and running fine.

Any help is highly appreicated!


Issue configuring Drive in HP Data Protector 9

$
0
0

Dear Forum members,

I do not really know if this is a serious issue, but I'm configuring my HP Data Protector against AWS (Amazon Web Services).

Configuration of the Device is ok.

And when I go to configure the Drive, it seems that all is fine:

 

 

 

Drive_Config.JPG

(Well, I'm not really sure of this list which one I should select).

But, when I finnish the configuration, and I entered the drive properties I cuold see:

Drive_Config_2.JPG

 

Do not know why they are shown with this red x.

 

And if I try to make an scan, this is the result:

 

[Normal] From: MSM@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:40

Media session 2016/12/16-3 started.

 

[Normal] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:40

STARTING Media Agent "Drive_LT_Ultrium"

 

[Normal] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:40

=> UMA@bckcentos01@/dev/sg10

Loading medium from slot 1 to device /dev/nst5

 

[Warning] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:43

The device "Drive_LT_Ultrium" could not be opened("Serial number has changed")

 

[Normal] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:43

Starting the device path discovery process.

 

[Critical] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:43

[90:1004] Device address not found.

 

[Normal] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:43

Device path discovery process finished.

 

[Major] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:43

[90:54] /dev/nst5

Cannot open device (Invalid device file type.)

 

[Normal] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:43

=> UMA@bckcentos01@/dev/sg10

Unloading medium to slot 1 from device /dev/nst5

 

[Normal] From: MMA@bckcentos01 "Drive_LT_Ultrium" Time: 16/12/2016 10:02:46

ABORTED Media Agent "Drive_LT_Ultrium"

 

 

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

0 media out of 6 successfully scanned.

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

 

Do you have any clue on this?

Many thanks in advance

 

 

Re: Data Protector 9.08 Digital signiature problems during upgrade of windows 2003,2008

$
0
0

we had a similar error and solved it by changing the following registry entry.....

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot\

change DisableRootAuth to ZERO, not 0x000000001

hope that helps!

Re: Backup for "/CONFIGURATION" of almost all the clients in a cell manager failing with V

$
0
0

I would run a backup in debug mode and also check AUTODR.log on a client.

Are you using firewalls? If not I would assume all ports are open?

Does a normal backup work of say C: drive ? exclude CONFIGURATION as a test...

DP9.07 - Cached GRE Linux issue

$
0
0

Have DP9.07 installed. Linux VM cell manager. Using catalyst stores with a storeonce 4700.

Cached GRE is not working for Linux VMs. Use the cell manager as the media server / mount proxy.

I get to the point in the vsphere web client where I can drill down each scsi0:0 partition....it sits there then fails with this:

"Error while trying to get mountpoint for LVM....Something went wrong while searching for logical volumes"

I ran debug mode and could only find this in the dpfs debug file.....

Getxattr:: lgetattr failed, errno:61

On the cell manager I see dpfs starts but cant work out while it wont work. Whole VM is just one scsi disk so cant be missing volumes.... Is it because I'm using the cell manager as the proxy????

help would be appreciated especially as this customer uses Veeam and I want to get DP working well with vmware integration and GRE.....

 

Final question, can I do a non-cached GRE of linux when using catalyst or will it only use cached???

Re: Backup for "/CONFIGURATION" of almost all the clients in a cell manager failing with V

$
0
0

Hi

Restarted the xinetd service and now patch details are visible, also the GUI is accessible now:

[root@XXXXX tmp]# omnicheck -patches
Patch level Patch description
===========================================
DPUX_00042/DPLNX_00330(BDL813) Core Component
DPUX_00042/DPLNX_00330(BDL813) Core of Integrations component
DPUX_00061/DPLNX_00349 Cell Manager Component
DPUX_00043/DPLNX_00331(BDL813) Disk Agent
DPUX_00064/DPLNX_00352 General Media Agent
DPUX_00063/DPLNX_00351 User Interface
DPUX_00047/DPLNX_00335(BDL813) Virtual Environment Integration
DPUX_00046/DPLNX_00334(BDL813) English Documentation (Guides, Help)
DPUX_00042/DPLNX_00330(BDL813) Core Technology Stack
DPUX_00061/DPLNX_00349 Cell Server Technology Stack
DPUX_00061/DPLNX_00349 Application Server Technology Stack
DPUX_00061/DPLNX_00349 Web Services
DPUX_00061/DPLNX_00349 Java Runtime Environment Technology Stack
DPUX_00061/DPLNX_00349 Job Control Engine Service Dispatcher
DPUX_00061/DPLNX_00349 Job Control Engine Service Registry
Number of patches found: 15.
[root@XXXXX tmp]#

Triggered some SQL backups and they completed successsfully but backup of /CONFIGURATION is still failing with same issue. It writes data for few minutes and then gets stuck, eventually it fails with VBDA timeout error.

Additinally all the hung sessions are cleared now.

Please suggest what further steps can be taken to fix this.

 

Viewing all 10494 articles
Browse latest View live


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