i noticed one nt incremental set has been backing up too much data on one nt
volume, and traced it back to starting a couple of weeks ago, in the middle
of the week, for no apparent reason. we've done 3 fulls since, and all incs
are still getting about 9 gig. a saturday full and monday morning
incremental backup (with very little activity sat. or sun.) show:
ID Stat Class Schedule Client Try Started Kbytes Files
FL:
----- ---- ------ -------- ------- --- ----------------- ---------- -------
---
59341 0 nt_dpt full walrus 1 01/02/10 01:01:50 13,007,824 55,800
N:\
60497 0 nt_dpt cumulati walrus 1 01/02/12 01:01:48 8,911,350 30,862
N:\
the rest of the machine looks okay:
59348 0 nt_dpt full walrus 1 01/02/10 05:46:24 5,008,554 18,785
F:\
60504 0 nt_dpt cumulati walrus 1 01/02/12 01:22:25 1 0
F:\
59347 0 nt_dpt full walrus 1 01/02/10 05:25:32 1,248,019 10,954
G:\
60503 0 nt_dpt cumulati walrus 1 01/02/12 01:21:39 1 0
G:\
59346 0 nt_dpt full walrus 1 01/02/10 04:04:51 11,231,218 195,110
H:\
60502 0 nt_dpt cumulati walrus 1 01/02/12 01:11:02 19,774 78
H:\
59345 0 nt_dpt full walrus 1 01/02/10 02:11:07 3,646,441 51,789
I:\
60501 0 nt_dpt cumulati walrus 1 01/02/12 01:06:53 643 22
I:\
59344 0 nt_dpt full walrus 1 01/02/10 01:58:56 1,023,940 1,591
J:\
60500 0 nt_dpt cumulati walrus 1 01/02/12 01:06:28 1 0
J:\
59343 0 nt_dpt full walrus 1 01/02/10 01:22:21 4,748,536 3,699
K:\
60499 0 nt_dpt cumulati walrus 1 01/02/12 01:05:45 1 0
K:\
the client netbackup configuration has "use archive bit" checked. attrib
and exploring both show the archive bit not set on files that are being
backed up in the cumulative backup for the N: drive. event viewer shows
OtMan4 events running during the backups (several OTMs opened, one OTM
closed). the backups end with status 0. the incremental has backed up
files dated as old as 1994. anywhere or anything else to look for?
netbackup server: sun450, solaris 7, netbackup 3.4ga, patch J0850482.
netbackup client: compaq, nt4.
thanks in advance,
jerald iverson
sysadm
|
