bpbkar log on the client should tell you what it's getting hung on. Also
have a look at Event Viewer Application log.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of smehta
Sent: 22 December 2008 17:42
To:
Hi,
Sound like Spaldam is on to something here. If open file option is not setup
you want to check that.
Problem not using open file option on windows client is that unless it's able
to read the file time out settings will be used.
After xxx sec setup in client properties netbackup will seem to
you are correct, it was a problem with a directory that the backup was getting
hung on. Ran a defrag and the backup completed successfully. Thanks for your
help
smehta wrote:
Hi,
I have a Windows 2003 client with 6.5.1 NBU client pkg installed on it. My
master server is a Solaris 10,
Earlier this year, I replaced the master server cluster at a previous
employer. We went with the same vendor, namely Sun, but while the old
servers were still in operation I built the new servers in a cluster.
According to Veritas support, even the node names of the nodes in the new
cluster
Only thing I can say is use the remote admin console for windows ( not the java
console) as it does NOT have that option on the right-click.
-Original Message-
From: Kurian K Oommen [mailto:ko.kur...@in.ibm.com]
Sent: Monday, December 22, 2008 10:28 PM
To: Judy Hinchcliffe
Cc:
Guys we have a strange upgrade predicament i could do with running by
the scene. I am splitting this into 2 threads to find pros/cons of 2
solutions im thinking about. Also to try and keep the mail shorter.
Current Situation :-
Sun E220R (running Solaris 8) Netbackup Server with attached L1000
Guys we have a strange upgrade predicament i could do with running by
the scene. I am splitting this into 2 threads to find pros/cons of 2
solutions im thinking about. Also to try and keep the mail shorter.
Current Situation :-
Sun E220R (running Solaris 8) Netbackup Server with attached L1000
Roed, as you've been told several times, the media is being detected as DLT in
your SL500 environment because you have a barcode rule (or the lack of one and
a default set to DLT) in that environment that is telling NetBackup to do that.
You need to add or modify a barcode rule that tells
//We were faced with something similar here when upgrading from 4.5/5.1
and SDLT to 6.0 and LTO and more or less went with your Option #2. What
we decided was to build an entirely new environment on new hardware to
migrate backups to leaving the old environments intact. 90% of our data
is kept
It looks to me like you're both right. If I may paraphrase:
Ed: snapshots are handy for immediate user-initiated file recovery
Curtis: in the described configuration, those snapshots will likely
consume lots of space
Maybe I'm missing some subtext here but I agree with, and see no
Sun E220R (running Solaris 8) Netbackup Server with attached
L1000 tape unit + 4 x DLT drives. Netbackup 5.0MP7.
Hardware is beyond old but customer is reluctant to upgrade.
We have told them we cannot support the L1000 unit and their
backups are at risk. It has gone EOSL and parts are
I've got a set of policies that follow a pattern of:
Monthly - Full
Weekly - Cumulative Incremental
Daily - Differential Incremental
If it's been 20 days from the last full, then what I need is the full
backup from 20 days ago, then a big skip to the previous cumulative
the incrementals from
12 matches
Mail list logo
