All,
I have been facing strange issues with some of the oracle database backups.
Some days backup run successfully and some days its either long running or
fails with error 54 or 6.
We had a theory that it could be because all the tape drives were busy thats
why backups were long running but
Sushil
Status 54 means NetBackup could not communicate with the client. (In
most cases timed out connecting to the client).
As for 6, I see them when doing redo logs - If there is nothing to
backup it fails with this code.
In your case, I am not sure. bpbkar and backint logging should be
Another Off Topic question:
In a big SSO environment with mixed O/S media servers attached to tape
and disk (via different HBA's) - who dictates what driver/firmware
versions should be used on tape drives, hba's, switches?
The NBU hardware compatibility list is very basic and list
I don't see that at all - the switches and HBAs are SAN/Network
technology that deal with the transport of data and aren't directly
addressed by NetBackup per se. NetBackup compatibility should have to
do with what OS they'll run on and what storage medium they'll work on -
it should be up to the
Netbackup 6.5.4 on master server. Server connected to an I2K robot. Robot went
down and was replaced with a new one. All the tapes were transferred over to
the new robot. Drive and robot configuration deleted on Netbackup master server
and rescan was done. Robot and drives were picked up. All
You just needed to go to the existing VG and do a mass move to
standalone. Then inventory the new robot.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Johan
Redelinghuys
Sent: Wednesday, May 12, 2010 8:37 AM
To:
Hello all,
We plan to move a 6.5.4 Master server from Solaris 2.8 to Linux RedHat
5.3 MP3 and regarding Document ID #337970 it looks that :
catalog backups from other UNIX and Linux distributions should not be
restored to a NetBackup 6.5.x master server running Red Hat Linux. This
Thanks Jeff
Hoping to get as many responses as possible.
We were asked by a customer in a (fairly) large environment to provide
recommended firmware and driver info. I am merely prepared to give what
is in the Compatibility List. There are separate teams for everything -
SAN, O/S
On Wed, May 12, 2010 at 6:54 AM, Marianne Van Den Berg
mvdb...@stortech.co.za wrote:
In a big SSO environment with mixed O/S media servers attached to tape
and disk (via different HBA’s) – who dictates what driver/firmware versions
should be used on tape drives, hba’s, switches?
The NBU
As you said your first robot0 died I bet you did not get to eject the tapes
from it.
So NB still thought the tapes were in that library (look at media in gui and
see it is assigned to a robot and a slot)
What you needed to do is move all the tapes to standalone (media right click
choose
Warning vltrun TCB1:duplicate.log.1_en. failed batch dup: 16:09:05
INF - Duplicate of backup id x_1272848045 failed, failed accessing
daemon lock file (158)
While running a vault duplicate in preparation for an eject I receive
the above error around %65 of job completion. Vault appears hung
Ich werde ab 12.05.2010 nicht im Büro sein. Ich kehre zurück am
16.05.2010.
Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
Another thing which i noticed in logs there were many jobs which were in queued
state but only 4 drives out 0f 8 were utilised. I can not find the reason why
the jobs were queued if the tape drives were available. Strange enough those
queued jobs became active after 2 hours.
I have no idea
First in the gui add the column to your view state details
That will tell you why a job is not running.
Could be you have on your storage unit, max drives, or max jobs and if those
have been met then the job will queue.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
I have been working with tape libraries for 20 years at many organisations
in Australia, and have never run across a Quantum library. I was told a few
years ago that the company has NO support or engineering staff in Australia
at all. Maintenance is outsourced to a third party. For this reason, I
A little bit of background. Data was lost over the weekend and we tried doing a
full recovery of all the lost data. Unfortunately, an improper start date was
used and only half of the data we needed was recovered. We must now go back
through the first couple of days and restore the rest of the
I'm not familiar with the latest versions of NetBackup, but I don't
think you can set these types of rules. If you have enough disk space
to hold what you wanted to restore, I would create a new directory, do
your restore there, then script something to put the files back the
way you want them.
On Wed, May 12, 2010 at 03:03:55PM -0400, gbkyle wrote:
I have listed below our current scenarios and actions we would like to take
in the event of this scenario. I was wondering if this is possible with
NetBackup, or possibly even an existing tool or script.
Scenario \ Action
Thank you for the replies.
+--
|This was sent by kyle.mul...@cdillc.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
Good Evening,
You can generate a list of files to restore in a file and pass that file as
input to the netbackup restore command.
I believe this feature as listed below is basically the tsm -ifnewer option .
I wonder if the netbackup folks would accept this new feature requrest.
len
20 matches
Mail list logo
