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 DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
