[Networker] Fulls versus incrementals and inodes?

If a given save set has a large number of files, say many tiny files,does this affect the time it will take a full to start running?

I guess where I'm going with this is that I'm trying to understand howLegato is affected by a large number of inodes and in what way. Forexample, I have this directory that takes hours to run a 'du' command onbecause it has a huge number of files, but it's only about 700 GB, but Imight have another path that's over 1 TB, and it only takes 5 minutes torun a 'du'. Just curious what an incremental does before it actuallystarts backing up any data versus what a full would do. Obviously, bothwill update the client's index while the data is being backed up, so ifthe save set has a lot of files then the full backup will force theindex to grow even larger, but it seems that while the full willundoubtedly cause the index to grow larger than the incremental, I wouldthink the incremental would take longer to figure out what, if anything,needs to be backed up since it has to read the index from the lastbackup and traverse the inode information on the data path to determinewhat to actually back up, right? What about a full?


Thanks.

george

--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145       | Voice: (301) 713-3284 x210
1315 East West Highway        | Fax:   (301) 713-3301
Silver Spring, MD 20910-3282  | Web Site:  http://www.nodc.noaa.gov/

- Any opinions expressed in this message are NOT those of the US Govt. -

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 with 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