We recently upgraded a number of our windows server 2003
clients from 6.5.4 to 7.0. These clients are in policies who’s
backup and subsequent duplication jobs are managed via a SLP. Ever since
the upgrade full backups run with no issue but the cumulative incremental
backups have started having issues when backing up a drive that has no change,
resulting in a 0 byte backup image file. For some reason, although the
activity monitor shows the job as completing successfully, output from the
nbstlutil stlilist –u image_incomplete | more shows multiple entries for
these clients like the one below…
Image stlcorpsql02.corp.dir.spartech.com_1289597375 for
Lifecycle winos_slp is NOT_STARTED
Copy to winos_su is NOT_STARTED
Copy to winos_rep_su is NOT_STARTED
Image stlcorpex3a.corp.dir.spartech.com_1289602850 for
Lifecycle winos_slp is NOT_STARTED
Copy to winos_su is NOT_STARTED
Copy to winos_rep_su is NOT_STARTED
Image stlcorpex4a.corp.dir.spartech.com_1289602879 for
Lifecycle winos_slp is NOT_STARTED
Copy to winos_su is NOT_STARTED
Copy to winos_rep_su is NOT_STARTED
These entries do not clear unless we force the cancellation
of all pending SLP activity asscociated with the SLP (in this case winos_slp).
Querying the backup client on these hosts works fine for all
drives backed up during a full backup and all drives during a cumulative backup
that had some change data. Any drives that generated a 0 byte file during
the cumulative incremental backup give the following error message when
querying their data in the netbackup client…
WARNING: unable to list the specified files using the
current search criteria
Support seem at a bit of a loss. Does anyone have any
ideas ?
Thanks,
Mark Glazerman
Enterprise Storage Administrator
Spartech Corporation
Desk: 314-889-8282
Fax: 314-854-8282
Cell: 618-520-3401
mark.glazerman AT spartech DOT com
http://www.spartech.com
P
please don't print
this e-mail unless you really need to
This
e-mail and any files transmitted with it are confidential, are intended solely
for the use of the addressee, and may be legally privileged. If you have received
this email in error please notify the sender immediately, and do not copy or
forward it.
