Thanks.
When I do my restore test, I will let you know.
For now it is going to be 3 - FullVM and File for Incrementals
Cheers
MK
--- On Tue, 1/6/09, bob944 wrote:
> From: bob944
> Subject: Re: [Veritas-bu] NBU 6.5.3 on Windows and VMWARE Backups
> To: veritas-bu@mailman.eng.auburn.edu
> Cc
On Wed, Jan 07, 2009 at 07:16:26PM +0200, Asiye Yigit wrote:
> We have duplicated some tapes using catalog backup. After duplication,
> when we search the images from the original copy,
>
> It says skipping media id xx it has already two copies.
What do you mean by "search the images"? What
We're running 6.5.1 and not having this issue.
Also FYI - Upgrade from 6.5.1 to 6.5.3 would not be as painful as the
one you just went through. From 5.1 to 6.0 there was a major change in
the way things were done. We upgraded from 6.0 to 6.5 with no real
issues.
-Original Message-
Fro
On Wed, Jan 7, 2009 at 11:09 AM, smehta
wrote:
> Thanks for the update. I did open a call with Symantec and they came back
> with the same solution. Upgrade to 6.5.3. However, we just completed the
> upgrade to 6.5.1. from 5.1 and have all the clients at 6.5.1. Upgrade was
> painful and so don't
Hello,
We have duplicated some tapes using catalog backup. After duplication,
when we search the images from the original copy,
It says skipping media id xx it has already two copies.
What is the reason? Duplication process can expire the images on the
primary copy?
Regards,
David McMullin wrote:
> Regarding the error you are getting you might want to open a trouble ticket
> with Symantec.
>
> For the error:
> Caught CORBA SystemException from SSmgrOperations: system exception, ID
> 'IDL:omg.org/CORBA/NO_PERMISSION:1.0'
> OMG minor code (0), described as '*u
On Wed, Jan 7, 2009 at 10:48 AM, Stump, Bob A wrote:
> The government requires that tapes be smelt
Sounds fishy to me :-)
http://en.wikipedia.org/wiki/Smelt
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewi...@ewilts.org
___
Veritas-bu maillis
I wondered what they did with the leftovers. I just never got into the
details. Was told they were deposed of in the proper way. I have seen
the claw thing that breaks/shreds/crushes the tapes into small bits.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:v
The government requires that tapes be smelt
but I don't know what they are supposed to smell like :-)
Bob Stump
Fidelity National Information Services
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf O
I use a company to do it.
Was Media Recovery - Now known as dataSPAN.
1) They will degauss onsite before the tapes leave your building
2) They may buy the tapes from you after that (they clean and sell them
as used - because they are degaussed before they leave your site they
are good to go)
3) Th
Regarding the error you are getting - you might want to open a trouble ticket
with Symantec.
For the error:
"Caught CORBA SystemException from SSmgrOperations: system exception, ID
'IDL:omg.org/CORBA/NO_PERMISSION:1.0'
OMG minor code (0), described as '*unknown description*', completed = N
You might want to degauss even before sending out to such a company.
At least one poster on this list noted how he had gotten "used" tapes
that were supposedly wiped but on checking he found other people's data.
As for us we degauss any bad tapes after images have expired in NBU. We
don't destro
On Wed, Jan 7, 2009 at 8:43 AM, Justin Piszcz wrote:
>
> 1. How do you handle it?
> 2. You can send tapes off-site to Iron Mountain, degauss them before you
> send them off-site, that is one option.
Iron Mountain also offers a tape destruction service. For a fee, of
course.
> 3. How much are
I the past when I have had to get rid of a bunch of old media. I did
some net searching and found a company that specifically dealt with this
as well as equipment recycling.
They agreed a price for the amount of tapes that I had; collected them
and then they were confidentially destroyed. I b
Had a few questions.
1. How do you handle it?
2. You can send tapes off-site to Iron Mountain, degauss them before you
send them off-site, that is one option.
3. How much are the machines that "securely" and physically destroy the
tape media?
4. If they're physically destroyed, how do you deal w
If the clients are UNIX or Linux you can try doing login from the master
to the client then doing a check to see from which IP or hostname the
login appears on the client. If it shows IP instead of hostname it
might be a sign the IP isn't recognized as the master's hostname.
-Original Message
Hi,
Thanks fr the reply bt we have not made any change in the n/w but all
the bkps except the catalog are failing fr all clients.The customer is
saying tht they have not done any chnge to their n/w bt from last week
the bkp is failing.I can tell you tht it is running with NBU version 5.0
and solar
The Oracle Agent has not been updated: http://support.veritas.com/docs/315028
"Oracle Agent: No Release Update at this time.
The latest Release Update (NB_ORA_6.5.2.tar)"
+--
|This was sent by fr...@schindelasch.de via Backup
On Wed, 7 Jan 2009, Justin Piszcz wrote:
> Anyone ever seen this before?
>
> I have 4 servers, 2 old and 2 new, all run 6.5.2a, now 6.5.3 as of this
> morning. I see this error occur in the logs a few moments after midnight,
> every night. I did notice mt-st was not installed on the machines
Anyone ever seen this before?
I have 4 servers, 2 old and 2 new, all run 6.5.2a, now 6.5.3 as of this
morning. I see this error occur in the logs a few moments after midnight,
every night. I did notice mt-st was not installed on the machines that
were getting this error, so I installed that a
Justin,
If the Oracle agent did not change from the prior release, Symantec
does not re-kit and re-release a new version. As far as I know, there
is not a 6.5.3 Oracle agent; we're using the 6.5.2 agents in our
environment.
--Larry
On Wed, Jan 7, 2009 at 6:02 AM, Justin Piszcz wrote:
> lftp
>
Thanks Larry.
Justin.
On Wed, 7 Jan 2009, Larry Fahnoe wrote:
> Justin,
>
> If the Oracle agent did not change from the prior release, Symantec
> does not re-kit and re-release a new version. As far as I know, there
> is not a 6.5.3 Oracle agent; we're using the 6.5.2 agents in our
> environmen
I saw a lot of these recently (and status 25 as well). It was because
our master had two NICs in our backup LAN IP range and the routing we'd
setup had gotten screwed up. I was able to solve it temporarily by
adding the master server twice to /etc/hosts on the clients that were
failing using bot
lftp
ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterprise_Server>
ls -1 | grep 6.5|grep ORA
NB_ORA_51_2_M_274695.linux64.tar
NB_ORA_51_7_M.hpia64_302615.tar
NB_ORA_6.5.1_294667.tar
NB_ORA_6.5.2_304438.tar
lftp
ftp.nbu.support.veritas.com:/pub/support/products/NetBackup_Enterpri
24 matches
Mail list logo