On Wed, May 13, 2009 at 12:51:03PM -0400, George Sinclair wrote:
> When NetWorker is backing up a *single* save set, does it send each file
> over one at a time or does it wrap two or more files together into that
> one stream?
Hmm. I'm not sure what the distinction is here.
There's a single TCP stream that is receiving the serialized output of
'save'. Just like 'tar' serializes a filesystem. The data from one
file is independent within the stream, but there's still only one
stream. So I don't know if that's yes or no to your question.
> Does it change its behavior from one save set to another, one client
> to another, etc. or is it consistent?
I can't think of anything that would change this behavior for a normal
filesystem backup (rather than an application backup).
> I'm assuming that one is using standard NW backups and not some
> ancillary package that would enable block level backups. In other words,
> when NW decides a file needs to be backed up, it backs up the entire
> file - this is what happens in our case - and not just the low level
> block changes.
Hmm. Both are true, but I'm not sure they're related. It backs up the
entire file, and each file is combined into a single stream of data.
--
Darren
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
|