I just wanted to thank everyone for their input on this topic;
the move to new hardware and the catalog recovery steps went smoothly. One
caveat in case you ever have to do the same, your media servers have to be
re-added to the Master server. The media server list is a registry entry that
does not get updated with a catalog recovery. And for reference, a 320GB
catalog took 5 hours to recover from a disk based backup.
Thanks again, if you’re ever in the neighborhood stop by for
some Texas bar-b-q, my treat.
Randy
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Randy
Samora
Sent: Tuesday, November 04, 2008 08:47: VIRUS ALERT!
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] 6.0 MP5 Upgrade to 6.5.2
I'm getting ready to start this upgrade early tomorrow
morning and I had a couple of last minute questions.
1.
Anyone have an idea of how long it’s going to take to
recover a 350GB NBU 6.0 catalog backup from LTO2 tape?
2.
I’m shutting down the old server and bringing up a new
one with the same name. Should I backup my catalog to one of the drives
on the new server to recover it faster?
Thanks,
Randy
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of scaud
Sent: Monday, November 03, 2008 03:01: VIRUS ALERT!
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 6.0 MP5 Upgrade to 6.5.2
Hi Randy,
Yes, the problem is there in v6.5.2A as well. The 'A'
version just stops a full backup being run after the upgrade, even if only an
incremental is scheduled. 6.5.2 has changed the way Calendar based scheduling
works. It is due to go back to 'normal' in v6.5.3 (due in Q4 '08 but not here
yet...).
So if you have calendar based scheduling with a window
that crosses the midnight boundary, expect to see 196 errors turn up.
Frequency-based scheduling isn't affected. You can get around the 196 errors by
enabling 'Retries allowed after runday' in your schedules but this just means
your jobs restart after they've failed at 00:00:00am. It's not an elegant fix.
Another option is to amend your jobs so only some start before midnight (enough
to have all of them running and un-queued by midnight) with the rest starting
afterwards.
Cheers,
Simon.
+----------------------------------------------------------------------
|This was sent by simon.caudwell AT lloyds DOT com via Backup
Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist -
Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu