I'll just add one possible answer about the index backups and why they get
scattered all over the place with the backups, its not all of the story though,
others will have further insight to add...
firstly - this is only the default behaviour. it's possible to make something
else happen - eg you manually kick off your index backup only when you want, or
you can make them go to their own pool of tapes.. but after giving it some
thought I generally stick with the default behaviour....
so for the default behaviour and the thinking behind it? -
indices get backed up to tape so you can use the tape quickly at a remote
location without reference to the original server - handy when your main
building is off-limits for some reason - if you have tapes which have backups,
indices, and a 'bootstrap' you can be browsing files in a matter of an hour or
less at a new site. it's important to practice this regularly so the concepts
are well understood, and the right tapes are being offsited...
next thing about index backups is that legato manages data expiry according to
saveset (a single instance of a backup on a particular filesystem) not by
volume, so you want all the savesets on a particular tape to expire around the
same time - otherwise you end up with a pile of tapes with almost but not quite
every saveset expired, and hence not recyclable.. this quickly gets expensive
at us$100+ a tape. so the principle is to try and keep the index backup in the
same vicinity of the saveset it goes with and have it expire at the same
time... also, if it did full backups all the time this would push related
savesets 'further apart' and onto the next tape... something less of a problem
these days now that tapes hold so much (but even so, plenty of my clients have
10GB per year of indices).... anyway - it can take a while to see the sense of
it all, in fact its something you usually only end up learning the hard way.
also you ask why index backups are shown as 'recov' instead of 'brows' -
browsable means that the index for a backup is online.... recoverable means the
saveset is still in the database, but the index for it is not online....
obviously an index backup isnt browsable.. in fact most savesets which are not
in the 'backup' namespace (or uasm backups if you like) show as recov only -
eg MSEXCH backups, or RAW, or some other application module saveset. recov is
not a bad thing.
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT listserv.temple DOT edu]On Behalf Of Srinivas Rao
Sent: Tuesday, 21 March 2006 7:49 PM
To: NETWORKER AT listserv.temple DOT edu
Subject: Re: [Networker] Queries regarding backup....
Hi Jason,
Thanks for your reply. Please see my comments below in the red color.
Thanks,
Srinivas Rao
Philips Software Centre,
Bangalore, INDIA.
Ph: +91 80 25579000 Extn: 1133
Cell: +91 99457 23423
NOTICE
This e-mail and any attachments are confidential and may contain copyright
material of Macquarie Bank or third parties. If you are not the intended
recipient of this email you should not read, print, re-transmit, store or act
in reliance on this e-mail or any attachments, and should destroy all copies of
them. Macquarie Bank does not guarantee the integrity of any emails or any
attached files. The views or opinions expressed are the author's own and may
not reflect the views or opinions of Macquarie Bank.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
