Your disk may be full of logs. When /opt is at 100% you can get errors like
the ones you've pasted and try the below command
/usr/openv/db/bin/NB_dbsrv
if you get an output like this,
ld.so.1: dbsrv9: fatal: libdbserv9_r.so: open failed: No such file or
directory
Below link will fix your
Rusty
How many machines are you backing up at the same time, as I seem to be reading
that only 4 are recommended at a time?
Does anyone have an environment with 100+ VM's?
Simon
From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com]
Sent: Tuesday,
I'm at a DR exercise. I've installed, patched, configured NBU and
successfully imported a catalog. I'm in Backup, Archive Restore and
using the Directory Structure pane to drill down to the files I want
to restore. I'm restoring files to an alternate server than the one
where the original files
What is the OS of the Master and Media server(s)?
Is DNS working flawlessly?
Thank you,
Joseph A. Infantino II
BackUp/Recovery Administrator
HARRIS IT Services
Assured Infrastructure Management
Office: 321-724-3011 | Fax: 321-724-3392
Email: joseph.infant...@harris.com
-Original
My apologies, I should have added that.
In my live environment, I have two servers:
ziggurat - Master/Media RHEL4
obelisk - media RHEL4
For DNS I'm just relying on the /etc/hosts file as I'm only trying
to recover 5 systems. The source system that I'm restoring from is not
here, not have we
Hmm ... relying on could be a problem. Are the systems configured to use DNS
first ... a DNS that is not there? Every host name resolve has to wait while a
DNS request or two (secondaries) times out? If DNS server is not available,
remove resolv.conf and check the hosts: line of
It also sounds like a name resolution problem.
You could put an entry for Server-A pointing to the recovery server's IP
address in hosts. Probably would be easier to just fix the name resolution
issue as when you go to the next server you will most likely have the same
problem. Good luck!
Another thought:
If this is version 7.0.1, there is a hostname caching 'feature' now in
NetBackup (Which I do NOT like, Symantec!!!). It caches the IP for each
host configured in NBU and sometimes this can result in the incorrect IP
being tied to the hostname. The default TTL for this cached
Definitely sounds like hostname resolution problems to me too. If all of the
hosts you want to talk to are in your /etc/hosts, removing DNS completely
sounds like a good option. The NBU GUI still seems to want to chatter with
every host it knows about, so if you remove DNS from resolv.conf, or
You can keep the Java UI from trying to reach out to all hosts when you
hit Host PropertiesClients by changing or adding the following parameter
in the setconf.bat file:
SET FORCE_IPADDR_LOOKUP=0
I'm not sure what, if any, setting there is for the Win Admin Console.
Rusty Major, MCSE, BCFP,
On Wed, Feb 9, 2011 at 6:10 PM, rusty.ma...@sungard.com wrote:
If this is version 7.0.1, there is a hostname caching 'feature' now in
NetBackup (Which I do NOT like, Symantec!!!). It caches the IP for each host
configured in NBU and sometimes this can result in the incorrect IP being
tied to
Hi all,
My employer is requesting I evaluate PureDisk and DataDomain for
de-duplication. While I can setup a demo of each and get the numbers, and
ask the sales guys what makes them great and why their competitors aren't, I
can't trust that is nothing more than sales drivel. So, I ask you expert
12 matches
Mail list logo
