Hi

My group needs to do some NetWorker 'full' vs. 'incremental' testing using CLI 
commands.  While the NetWorker 'save' command does not support this (all 
backups run with 'save' are 'adhoc' (basically a 'full')), the 'savefs' command 
does support specifying the level on the command line.

But it appears that Windows and Linux behave differently.  I know, this doesn't 
make sense, and would be glad to be told what the real problem is.

Here are the results of a test I ran on SLES 10 SP3 using NetWorker for Linux 
V7.5 SP1:

tivo2:~ # savefs -l full /swlib/Terry/Oracle
tivo2.backup: /swlib/Terry/Oracle level=full,    118 KB 00:00:12     22 files
tivo2:~ # savefs -l incr /swlib/Terry/Oracle
tivo2.backup: /swlib/Terry/Oracle level=incr,      0 KB 00:00:00      0 files
tivo2:~ # mminfo
 volume        client       date      size   level  name
A00001         tivo2.backup 04/01/10 118 KB   full  /swlib/Terry/Oracle
A00001         tivo2.backup 04/01/10  4  B    incr  /swlib/Terry/Oracle

So, this confirms that 'savefs' can  work (allow the level to be specified).

But when I ran tests on Windows 2003 using NetWorker for Windows V7.6, every 
backup that I ran was a full:


C:\>savefs -l full c:\Testdata\1MBFiles\1MB_Dir_1
tivo1: C:\Testdata\1MBFiles\1MB_Dir_1 level=full, 1000 MB 00:01:02   1008 files

C:\>savefs -l incr c:\Testdata\1MBFiles\1MB_Dir_1
tivo1: C:\Testdata\1MBFiles\1MB_Dir_1 level=full, 1000 MB 00:00:26   1008 files

C:\>mminfo
 volume        client       date      size   level  name
A00001         tivo1       4/1/2010 1000 MB   full  
C:\Testdata\1MBFiles\1MB_Dir_1
A00001         tivo1       4/1/2010 1000 MB   full  
C:\Testdata\1MBFiles\1MB_Dir_1

C:\>

These Windows results were mirrored on another Windows system, also running 
NetWorker V7.6.

Any thoughts about the cause for this behavior?

Thanks!
tl

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