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

Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 2:00 am
$
0
0

Hi guys

 

I'm in dilemma.

 

The particular server suddenly failing to backups.

 

So here's the information:

 

3 servers in the same segment, 2 able to backup and 1 failed:

 

[Critical]

[61:12500] Cannot connect to inet for getting filesystem list
on host"fqdn".

 

[Warning]

Cannot get the list of filesystems on host "fqdn".
Backup of this host will be retried at end of session.

 

[Warning]

[61:2013] Some of the backup devices are occupied. Session is waiting
for all the devices to get free.

 

We are using port 5555 for the communication.

 

All servers are able to telnet port 5555 to the cell server.

Cell server able to telnet all servers accept the one failing, on port 5555.

 

What I've done, verified firewall port is open from cell to failed server - OK

Verified that local firewall on failed server is turned of - OK

Verified that port 5555 is listening on failed server - OK

Verified that cell server can telnet to port RDP 3389 to the failed server - OK

Reinstalled DP agent on the failed server, for about 5 times - Services OK

Removed server from Cell server, and re-added. - Not OK

 

I know this sound like firewall issue but the network team has confirmed the port is open.

 

Anyone has experienced this and how should I move forward???

 

Thank you so much in advance.

 

PS: DP agent version is 6.10, same across all 3 servers

↧
Search

Re: HP DP 8.0 omniofflr IDB autorecover error

March 21, 2014, 2:18 am
$
0
0

Hi ,

 

This is Lunux bob.

Pls suggest resolution for linux cell manager.

↧
↧

Re: HP DP 8.0 omniofflr IDB autorecover error

March 21, 2014, 2:25 am
$
0
0
Its still showing the same error when ran with session ID & -force option.

omnidbrestore.pl is obseleted & advised to used omniofflr.
↧

Re: Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 2:47 am
$
0
0

hmm strange

 

after uninstalling the clinet, did you verify that no omniback folder or registry key was left?

 

i suggest you to uninstall client agent again, check that no omniback folder is left. if it is, delete it. check that serivce is removed.

 

reinstall agent again. if you install it localy then start setup with "run as administrator"

 

try disable antivirus if it is present on the client, maybe it causes troubles

↧

Re: Upgrading 6.20 on a W2K3 32-bit CM to 7 (or 8.1)

March 21, 2014, 4:03 am
$
0
0

Hi Bob,

 

Thanks for the advice - looks like an IDB restore or file migration might be the way to go alright.

 

I've had to transplant a database before, to a test environment, so I might give that a go before a tape-based recovery.

 

My plan in such a case would be to:

 

  • Run a full maintenance of my IDB, including a writedb / readdb;
  • Back it up;
  • Take a copy of \db40, leaving services stopped;
  • On the W2K8 cluster, stop services and copy the \db40 files to a safe location;
  • Copy in the files from the 32-bit instance;
  • Start the W2K8 services;
  • Convert the files for 64-bit operation (would this be the correct point?)
  • Check operation.

This will be my first upgrade to a new platform - in previous instances I've simply upgraded in place - so I'm wondering if I'll need to worry about things like IP addresses or the cluster and Cell Manager ID?

 

If it was to be a direct upgrade, in place, the names and IP addresses would be retained; however in this instance my IPs will definitely change, and importing the old IDB will bring the 32-bit Cell Manager's identity with it, will it not?

 

Looks like it's going to take some careful planning...

 

Regards,

 

Bob

 

↧
↧

Re: Upgrading 6.20 on a W2K3 32-bit CM to 7 (or 8.1)

March 21, 2014, 4:54 am
$
0
0

your plan should work, but do not start dp services on the w2k8 box until you did run the winomnimigrate command. -> you need to convert idb first from x86 to x64, then start the dp services on the new  host.

 

you could also have a look at the install paper. there the migration scenario is also described

↧

Re: OV Omniback/Data Protector

March 21, 2014, 6:13 am
$
0
0

Hi,

 

 

old post,.. but same problem.

 

How to solve this?

 

Thanks & Regards,

Tom

↧

Re: Windows Disk Backup

March 21, 2014, 6:32 am
$
0
0

Finally it worked for me. since i had wind2008 R2 hence i used 2nd lnk...thanks to all.

But now I am tryng to create ISO image for A linx server RHEL5.10. and when I try to create ISO image. EADR is greyed out and SRD file update is selected .

I get error:

disatser recovery wizard was unable to find boot:object/drive backed up. this object is required to update the disaster recovery information

 

↧
Search

Re: HP DP encryption

March 21, 2014, 6:44 am
$
0
0

I get error: Medium is already in the database. no need to import.

↧
↧

Re: Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 6:53 am
$
0
0

Hi,

 

The port 5555 is only used as a communication between the Cell Manager and client to initiate sessions. As far as I know, the actual traffic will use a random port assignment.

 

So if you have port 5555 open you will be able to see the client and telnet to it. You can probably also run a 'Clients\Check Installation...' successfully, yes?

 

What you might need to do is to set the following parameters in omnirc on your CM and MA:

 

OB2PORTRANGESPEC=xMA-NET:18000-18025;xSM:20100-20199
#    Default: no ranges specified (i.e. use any available port)
#    This variable limits the range of port numbers that specific
#    Data Protector processes use when assigning listen ports dynamically.
#    This option is typically set on the Cell Manager system and/or the
#    Media Agent system when components of the cell are located on both sides
#    of a firewall.
#    Note that the firewall needs to be configured separately.
#    Refer to "Firewall Support" in HP OpenView Storage Data Protector
#    Administrator's Guide or in online help for additional information.

 

You'll also need to set up firewall rules to reflect these port ranges.

 

I hope I've understood your problem correctly, and that this helps in some way...

 

Cheers,

 

Bob

↧

Re: Upgrading 6.20 on a W2K3 32-bit CM to 7 (or 8.1)

March 21, 2014, 6:55 am
$
0
0

Hi Andre - thanks, the 32- to 64-bit conversion part was a concern.

 

I'll plan accordingly...

 

Cheers,

 

Bob

↧

Re: HP DP 8.0 omniofflr IDB autorecover error

March 21, 2014, 7:11 am
$
0
0

Sorry, the fact that this was Linux was not clear, but, I should have known this by this path

 

/var/opt/omni/server/db80/logfiles/rlog/obrindex.dat

 

This is apparently a known problem, and a test binary was released earlier this week.  Open a case with the response center, make reference to QCIM2A50676

 

To get ahead of this, please run the following command on your cell manager

 

omniofflr -idb -autorecover -save /tmp/restjob.txt -skiprestore

 

This will produce a file /tmp/restjob.txt.  When you open the case, be prepared to provide this file and the 'obrindex.dat' file (see path above), and make sure that you  identify what version of DP you are running

 

 

↧

Re: Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 7:36 am
$
0
0

I'm not sure that the error is an indication of a firewall issue.  You did not indicate the type of server, so I can't be ral specific, but, it looks more to me like the INET service is not running on the client system

 

Windows

   -  Go to Services, find the Data Protector INET service, make sure that it is started

HPUX

   -  Run

          ps -ef | grep inetd

and see if the 'inetd' daemon is running.  If it is not, run 'inetd' to start it.  Also, check /etc/services to be sure that there is a line, most likely, the last line in the file

         omni   5555/tcp

and check the file /etc/inetd.conf to be sure that there is a line

        

omni stream tcp6 nowait root /opt/omni/lbin/inet inet –log /var/opt/omni/log/inet.log

 

Linux:

   -  Run

         ps aux | grep [xi]netd

to see if the inetd process is running.  If not, run

         

/etc/init.d/xinetd reload

/etc/init.d/xinetd restart

 

From the command prompt on the cell manager, check to see if DP will connect through port 5555

 

       telnet [client hostname] 5555       Do not include the [   ] marks

↧
↧

Re: MSSQL DB backup integration

March 21, 2014, 8:32 am
$
0
0

It is still isnt working. I am not sure why it cant tkae the instance name. verytiem I try to configure it screen would hang.

any license constraint ?

↧

Re: 12:8019 Integration cannot be configured.

March 21, 2014, 8:39 am
$
0
0

I found a lab case with the same error, but for DP 6.2, so I checked with someone in Engineering to see if it has any validity for your issue.  It is his recommendation that you open a case, and have the problem debugged because with DP 8, many things have changed

↧
Search

Re: Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 9:08 am
$
0
0

hmm

 

I didn't verify that when reinstalling.. Will try the option you suggested, looks simple but always being missed.. I'll update on this one.. thanks for the suggestion

↧

Re: Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 9:11 am
$
0
0
yes the port 5555 is being used..

though the backup team did verified that from cell server, it can't telnet to the failed server on port 5555, although the firewall team has confirmed the port has already configured to allow..

the problem here is confirmed to be on the 5555, as I have 2 other servers within the same range that are able to telnet to this port and working fine..
↧
↧

Re: Backup Failed, Cannot connect to inet for getting filesystem list

March 21, 2014, 9:12 am
$
0
0
my apologize

this is windows and I can confirm that DP inet service is running fine, before and after reinstallation.. prior to that, service has been restarted successfully but still no difference
↧

Re: HP DP 8.0 omniofflr IDB autorecover error

March 22, 2014, 8:06 am
$
0
0

Hi ,

 

When i removed -dev_Serial & ioctl_serial & executed all paramters manually in output file , its going forward in preview. 

 

Or else running command manually

 

./omniofflr -idb -name "HP:Ultrium 5-SCSI_1_testapp" -policy 10 -type 13 -library "HP:1x8 G2 AUTOLDR_testapp" -dev /dev/nst0 1 -blk 256 -barcode -ioctl /dev/sg20 -mahost testapp.bakhashab.com -maid 0100007f:5280ac0f:7244:0001 -slot " 7:-1" -position 1141:0 -daid 1392303619 1392303618 1392303617 1392303620 1392303613 1392303614 1392303616 1392303615 1392303610 1392303609 1392303612 1392303611 1392303608 1392303606 1392303607 1392303602 1392303604 1392303603 1392303605 -preview

↧

Backup data encryption in DP7

March 22, 2014, 9:16 am
$
0
0

Hello Expert,

 

Need advice from you experts on my current DP setup.

 

I am using Dp 7.01 with cell manager on windows 2008 R2 64bit. All the clients in the enviornments are winodws only and total clients we have is around 30. During this year auditing the auditor has raised the concerned for backup data encryption. Currently I am using MSL2024 with ultrium 3 drive at production site and standalone tape drive with ultrium 3 on DR site.

 

Now as per auditor I need to encrypt my backup data. I belive I have 2 options here

1. Drive based encryption

2. Software based encryption

 

My concerned over here is what are the limitations of drive based encryption and software based encryption. I hears there are performance issue in software based encryption so I don't want to go for that. Hence my option will be drive based encryption only.

 

Can anyone suggest what are the limitations of drive based encryption? Also I need to upgrade the ultrium 3 to minimum of ultrium 4 to use drive based encryption. Do I need to upgrade this drive to both site production and DR as I am restoring my production backup at DR regularly for testing.

 

Also if I take increment backup can I be able to restore it at DR since at DR I have standalone tape drive?

 

Please excuse me if I am not very clear.

Many thanksfor any help in advance.

 

Regards,

 

 

↧
Viewing all 10494 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>