This is a multipart message in MIME format.
--=_alternative 0071E94086256CB6_=
Content-Type: text/plain; charset="us-ascii"
as for the advantage you listed... it's actually not true.
it's a "FEATURE" of NetBackup that when you add a client in a new policy
it will force a full for the first backup, instead of the incremental,
when the incremental window is open and the window for a full isn't...
however, even though it will back up everything on the system (as if it
were a full), the schedule name still says incremental (which means it
uses the incremental retention, bpstart/bpend, etc.).
also something to think about if you are renaming your policies. it can
be a shock the first time you rename a policy and then find out your
backups ran longer than expected because every client in that policy did a
full the same night.
- Scott
"Fabbro, Andrew P" <Fabbro.Andrew AT cnf DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
01/21/2003 12:52 PM
To: "'markjessup AT northwesternmutual DOT com'" <markjessup AT
northwesternmutual DOT com>
cc: "'veritas-bu AT mailman.eng.auburn DOT edu'" <veritas-bu AT
mailman.eng.auburn DOT edu>
Subject: RE: [Veritas-bu] Using Archive bit vs Modified Date
with Netbacku p
The archive bit is evil ;)
It's just too easy to reset and any admin on the client can perform
functions that will nuke it. This leads to cases where the backup admin
is
in trouble because something wasn't backed up (and can't be restored) but
has no way to determine why something wasn't backed up.
Your mileage may vary. The only advantage I can think of is that you can
create a new policy, drop a client into it, and the incremental will still
be an incremental. If you do that with Unix clients, your first
incremental
will be a full because a new policy means a new "last backed up" time, set
to 0 initially. But how often do you do that?
-----Original Message-----
From: markjessup AT northwesternmutual DOT com
[mailto:markjessup AT northwesternmutual DOT com]
Sent: Tuesday, January 21, 2003 10:34 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Using Archive bit vs Modified Date with Netbackup
We are converting to Netbackup and was curious what is the best practice
for
backing up changed files on Netware, NT, and W2K platforms. Do people
rely
on the "Archive Bit" or the "Modified Bit". Is one better than the other
or
is there any known issues with one or the other with Netbackup. Do they
both work fine with incrementals and cumulative differentials? Any other
info or gotchas you could provide would be great. Thanks!
Mark Jessup
IS Manager, Enterprise Storage and Output Management Northwestern Mutual
(414) 665-3968
markjessup AT northwesternmutual DOT com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 0071E94086256CB6_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">as for the advantage you listed... it's actually
not true.</font>
<br>
<br><font size=2 face="Arial">it's a "FEATURE" of NetBackup that when
you add a client in a new policy it will force a full for the first backup,
instead of the incremental, when the incremental window is open and the window
for a full isn't... however, even though it will back up everything on the
system (as if it were a full), the schedule name still says incremental (which
means it uses the incremental retention, bpstart/bpend, etc.).</font>
<br>
<br><font size=2 face="Arial">also something to think about if you are renaming
your policies. it can be a shock the first time you rename a policy and
then find out your backups ran longer than expected because every client in
that policy did a full the same night.</font>
<br>
<br>
<br><font size=2 face="Arial">- Scott</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Fabbro, Andrew P"
<Fabbro.Andrew AT cnf DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">01/21/2003 12:52 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"'markjessup AT northwesternmutual DOT com'"
<markjessup AT northwesternmutual DOT com></font>
<br><font size=1 face="sans-serif"> cc:
"'veritas-bu AT mailman.eng.auburn DOT edu'"
<veritas-bu AT mailman.eng.auburn DOT edu></font>
<br><font size=1 face="sans-serif"> Subject:
RE: [Veritas-bu] Using Archive bit vs Modified Date with
Netbacku p</font></table>
<br>
<br>
<br><font size=2 face="Courier New">The archive bit is evil ;)<br>
<br>
It's just too easy to reset and any admin on the client can perform<br>
functions that will nuke it. This leads to cases where the backup admin
is<br>
in trouble because something wasn't backed up (and can't be restored) but<br>
has no way to determine why something wasn't backed up. <br>
<br>
Your mileage may vary. The only advantage I can think of is that you
can<br>
create a new policy, drop a client into it, and the incremental will still<br>
be an incremental. If you do that with Unix clients, your first
incremental<br>
will be a full because a new policy means a new "last backed up"
time, set<br>
to 0 initially. But how often do you do that?<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: markjessup AT northwesternmutual DOT com<br>
[mailto:markjessup AT northwesternmutual DOT com] <br>
Sent: Tuesday, January 21, 2003 10:34 AM<br>
To: veritas-bu AT mailman.eng.auburn DOT edu<br>
Subject: [Veritas-bu] Using Archive bit vs Modified Date with Netbackup<br>
<br>
<br>
We are converting to Netbackup and was curious what is the best practice for<br>
backing up changed files on Netware, NT, and W2K platforms. Do people
rely<br>
on the "Archive Bit" or the "Modified Bit". Is one
better than the other or<br>
is there any known issues with one or the other with Netbackup. Do
they<br>
both work fine with incrementals and cumulative differentials? Any
other<br>
info or gotchas you could provide would be great. Thanks!<br>
<br>
<br>
<br>
Mark Jessup <br>
IS Manager, Enterprise Storage and Output Management Northwestern Mutual<br>
(414) 665-3968<br>
markjessup AT northwesternmutual DOT com<br>
<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 0071E94086256CB6_=--
|
