Backup Central

We have a large drive on one of our networker clients, about 1,3 TB. This
volume produces incremental savesets which are almost as large as the
total data on the volume. We have selected to use the windows change
journal, and have ensured that it is indeed large enough (4GB according to
the networker change journal manager). We have also run a level 6 check of
the client index for the client in question, but none of these actions
seem to help. We have also performed a full backup after taking these
steps, but it still persists.

The client and server version are 7.1.3. Is this anything that seems
familiar to someone in the networker community? We're really out of ideas
of how to troubleshoot it.

//Oscar

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Oscar Olsson wrote:
We have a large drive on one of our networker clients, about 1,3 TB.
This volume produces incremental savesets which are almost as large as
the total data on the volume. We have selected to use the windows change
journal, and have ensured that it is indeed large enough (4GB according
to the networker change journal manager). We have also run a level 6
check of the client index for the client in question, but none of these
actions seem to help. We have also performed a full backup after taking
these steps, but it still persists.

The client and server version are 7.1.3. Is this anything that seems
familiar to someone in the networker community? We're really out of
ideas of how to troubleshoot it.

The first thing to look at is the output of nsrinfo for one of the
incremental save sets. Then you can pick out a number of files and work
out whether or not you believe these files should have been backed up as
part of the incremental in question. This will help you to investigate
further.

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Hi,

The workaround is to split your saveset in multiple parts and reduce your client parallelism.

Reagrds,

-----Message d'origine-----
De : Davina Treiber [mailto:Treiber < at > HOTPOP.COM]
Envoyé : jeudi 31 mars 2005 11:40
À : NETWORKER < at > LISTSERV.TEMPLE.EDU
Objet : Re: [Networker] Large incremental backups on w2k volume?

Oscar Olsson wrote:
We have a large drive on one of our networker clients, about 1,3 TB.
This volume produces incremental savesets which are almost as large as
the total data on the volume. We have selected to use the windows change
journal, and have ensured that it is indeed large enough (4GB according
to the networker change journal manager). We have also run a level 6
check of the client index for the client in question, but none of these
actions seem to help. We have also performed a full backup after taking
these steps, but it still persists.

The client and server version are 7.1.3. Is this anything that seems
familiar to someone in the networker community? We're really out of
ideas of how to troubleshoot it.

The first thing to look at is the output of nsrinfo for one of the
incremental save sets. Then you can pick out a number of files and work
out whether or not you believe these files should have been backed up as
part of the incremental in question. This will help you to investigate
further.

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Don't know if it relates. We were not using the change journal method.
Also I tell you things I read long ago, dont know it it still applies.

When networker finds a Windows file with the attribute 'A' (modified),
it backups the file in any incremental, and continues to save it until
a full is run, moment in which it removes the modified attribute.

Bye.

Oscar Olsson wrote:

We have a large drive on one of our networker clients, about 1,3 TB. This
volume produces incremental savesets which are almost as large as the
total data on the volume. We have selected to use the windows change
journal, and have ensured that it is indeed large enough (4GB according to
the networker change journal manager). We have also run a level 6 check of
the client index for the client in question, but none of these actions
seem to help. We have also performed a full backup after taking these
steps, but it still persists.

The client and server version are 7.1.3. Is this anything that seems
familiar to someone in the networker community? We're really out of ideas
of how to troubleshoot it.

//Oscar

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu






Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Oscar,

Suggest that you set the "NSR_AVOID_ARCHIVE" environment variable on your
w2k machine to a non-null value, i.e. "yes" or "1" or something. Then
reboot. This will instruct NetWorker to ignore changes that may be being
made to files on your client machine as a result of antivirus scanning. I
know that this fix solved the exact problem you mention on over 500 win2k
servers at my site.

-ty

Phillip T. ("Ty") Young, DMA
Manager, Data Center and Backup/Recovery Services
Information Services
i2 Technologies, Inc.



Patricio Mora
<patricio.mora.ex
t < at > JUNTADEANDALUCI To
A.ES> NETWORKER < at > LISTSERV.TEMPLE.EDU
Sent by: Legato cc
NetWorker
discussion Subject
<NETWORKER < at > LISTSE Re: [Networker] Large incremental
RV.TEMPLE.EDU> backups on w2k volume?


04/01/2005 12:54
AM


Please respond to
Legato NetWorker
discussion
<NETWORKER < at > LISTSE
RV.TEMPLE.EDU>;
Please respond to
Patricio Mora
<patricio.mora.ex
t < at > JUNTADEANDALUCI
A.ES>






Don't know if it relates. We were not using the change journal method.
Also I tell you things I read long ago, dont know it it still applies.

When networker finds a Windows file with the attribute 'A' (modified),
it backups the file in any incremental, and continues to save it until
a full is run, moment in which it removes the modified attribute.

Bye.

Oscar Olsson wrote:

We have a large drive on one of our networker clients, about 1,3 TB. This
volume produces incremental savesets which are almost as large as the
total data on the volume. We have selected to use the windows change
journal, and have ensured that it is indeed large enough (4GB according to

the networker change journal manager). We have also run a level 6 check of

the client index for the client in question, but none of these actions
seem to help. We have also performed a full backup after taking these
steps, but it still persists.

The client and server version are 7.1.3. Is this anything that seems
familiar to someone in the networker community? We're really out of ideas
of how to troubleshoot it.

//Oscar

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu






Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu