Hi Jeff,
I've just started using dnsmasq on Red Hat Linux which acts as a dns
forwarder but allows me to override certain IP addresses. It's easy to
configure and will get around this problem.
Other than that is it out of the question to use a slightly different
name for client interface that
We actually do that for most clients but this is a MS Exchange cluster
name and we didn't need to use a separate name for this cluster in
6.5.4. To me this seems like a bug in the NetBackup tools since I can
demonstrate OS level tools resolve the expected IP and it is only the
NetBackup tools
Have you tried running bptestbpcd -client client name -verbose -debug from
the media server? What are the results? Does bpgetconfig -M client name
work?
Regards,
Patrick Whelan
VERITAS Certified NetBackup Support Engineer for UNIX.
VERITAS Certified NetBackup Support Engineer for Windows.
Hello,
How has everyone's 7.1 experience been?
Any gotchas or things to look out for?
Justin.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Hi,
I noticed it starts up a lot of services with 7.1
# rc.d/init.d/netbackup start
NetBackup Authentication daemon not started.
NetBackup network daemon started.
NetBackup client daemon started.
NetBackup SAN Client Fibre Transport daemon started.
NetBackup Bare Metal Restore Boot Server daemon
There appear to be differences in where fully qualified domain names
need to be used.
We have moved most of our environment to 7.1 but do have a few
outstanding issues:
Can't backup SQL 2000 on MS 2000 (not supported - we put the NBU 6.5.4
client on this server since there isn't a 7.1 version.
On Fri, 29 Apr 2011, Lightner, Jeff wrote:
There appear to be differences in where fully qualified domain names
need to be used.
We have moved most of our environment to 7.1 but do have a few
outstanding issues:
Can't backup SQL 2000 on MS 2000 (not supported - we put the NBU 6.5.4
Hello,
Has anyone seen this?
Windows 2008 clients:
CLIENT:
ALL_LOCAL_DRIVES
On the client,
EXCLUDE C:\
INCLUDE D:\
For the C:\ backup it will get the following error:
Apr 29, 2011 10:09:22 AM - mounting TAPE01
Apr 29, 2011 10:09:24 AM - connecting
Apr 29, 2011 10:09:24 AM - connected;
Why would you do that?! Are you trying to see how many errors you can cause
by using non-sense combinations? Either
ALL_LOCAL_DRIVES and exclude C: \
or
specify D: only in the file section.
You are including the D:\ drive which should be included when you said
ALL_LOCAL_DRIVES.
Regards,
NetBackup was locked up and certain parts of the Linux OS weren't
working. (e.g. I couldn't run ps -ef and get full output - it would
hang). If I ran cat /proc/stat I would see process_blocked was
showing 5 or higher whereas without these big things running it is
typically at 0 or 1.
At
Hi Jeff,
Thank you for your feedback, it is very useful. I will have to do more
load testing from your feedback.
Justin.
On Fri, 29 Apr 2011, Lightner, Jeff wrote:
NetBackup was locked up and certain parts of the Linux OS weren't
working. (e.g. I couldn't run ps -ef and get full output -
That doesn't make any sense to me... why not just use all local drives and
exclude C:\ from that... Having and exception to the exclude list of D:\
doesn't make sense... D:\ isn't part of C:\...
I would just use all local drives and exclude C:\...
Scott Chapman
Senior Technical Specialist
Hi,
Please disregard, the actual example is:
Exclude Lists:
C:\
D:\
Include Lists:\
D:\Mydata
Where mydata is the only path we want to backup and nothing else on D:\
(potentially TB of live DB, where, we only want the dumps, for example).
Justin.
On Fri, 29 Apr 2011, Chapman, Scott wrote:
How has everyone's 7.1 experience been?
It runs filesystem backups well in the lab.
Any gotchas or things to look out for?
Things you would expect to be found in FA and to be in LBN before you
discover it the hard way, including
- upgrade of a solaris master with windows clients fails/takes
Hello Justin
Had the same issue to just after upgrading to 7.0, a workaround that worked
for was to exclude drive:\*.*
Regards
Michael
2011/4/29 Justin Piszcz jpis...@lucidpixels.com
Hello,
Has anyone seen this?
Windows 2008 clients:
CLIENT:
ALL_LOCAL_DRIVES
On the client,
EXCLUDE
Hello Michael,
I've tested this and I've confirmed you are correct it fixes the problem,
under 7.0.1 as well!
Thank you!
Justin.
On Fri, 29 Apr 2011, Michael Graff Andersen wrote:
Hello Justin
Had the same issue to just after upgrading to 7.0, a workaround that worked
for was to exclude
Do you have Windows Master Server?
We ran upgrade on a standalone Windows Master Server and it went well. However,
hot catalog backup failed with status code 2 on Windows Master.
Had to download n install patch from Symantec's website which replaced
bpbrm.exe and that solved the problem.
Hi,
Not sure who this was directed to, using Linux here, but good to know
about that issue, thanks.
Justin.
On Fri, 29 Apr 2011, sandesh wrote:
Do you have Windows Master Server?
We ran upgrade on a standalone Windows Master Server and it went well.
However, hot catalog backup failed
18 matches
Mail list logo
