All-
One of our Windows admins pointed out something odd about one of our
backup clients, and I'm wondering if anyone else has ever seen this.
NetWorker server: 7.5.2.Build 452 on RHEL 5.5
client: 7.4.2.Build 431 on Windows Server 2003 SP2 Enterprise (32 bit)
The windows client in question has an F: volume that's 2.3 TB in size
and is nearly full. Here's the relevant info for the last three (monthly)
fulls for that client:
date ssid name total nfiles ssflags
09/22/10 3734671417 F:\ 2393825931812 12246 vrEF
10/02/10 2141638987 F:\ 2431533007424 12299 vF
11/10/10 2497352593 F:\ 2464296651492 12683 vF
However, here's what the savegrp completion report had to say about the
client:
* client.ndsu.edu:F:\ 1 retry attempted
client.ndsu.edu: F:\ level=full, 1844 MB 56:18:40 12683 files
Notice that the units in the savegrp report are "MB", when in reality they
should probably be "GB".
Going back through older savegrp reports for the F: volume for that client,
I see:
client.ndsu.edu: F:\ level=full, 1339 GB 12:17:23 10322 files
client.ndsu.edu: F:\ level=full, 1348 GB 11:36:39 10350 files
client.ndsu.edu: F:\ level=full, 1426 GB 13:12:59 10504 files
client.ndsu.edu: F:\ level=full, 1408 GB 12:45:21 10647 files
client.ndsu.edu: F:\ level=full, 1378 GB 19:07:11 10296 files
client.ndsu.edu: F:\ level=full, 1405 GB 12:52:36 10241 files
client.ndsu.edu: F:\ level=full, 1406 GB 12:29:36 10245 files
client.ndsu.edu: F:\ level=full, 1415 GB 12:52:54 10371 files
client.ndsu.edu: F:\ level=full, 1423 GB 12:35:36 10471 files
client.ndsu.edu: F:\ level=full, 1252 GB 11:47:17 10323 files
client.ndsu.edu: F:\ level=full, 1334 GB 12:52:27 10766 files
client.ndsu.edu: F:\ level=full, 1450 GB 22:49:36 11308 files
client.ndsu.edu: F:\ level=full, 1492 GB 22:16:26 11373 files
client.ndsu.edu: F:\ level=full, 1733 GB 28:48:58 11764 files
client.ndsu.edu: F:\ level=full, 2051 MB 36:09:37 12930 files
client.ndsu.edu: F:\ level=full, 2082 GB 36:29:02 12479 files
client.ndsu.edu: F:\ level=full, 1996 MB 38:56:18 12609 files
client.ndsu.edu: F:\ level=full, 1880 MB 64:34:26 12997 files
client.ndsu.edu: F:\ level=full, 1810 MB 62:34:45 13027 files
client.ndsu.edu: F:\ level=full, 1969 GB 57:06:39 11804 files
client.ndsu.edu: F:\ level=full, 1972 MB 53:02:08 12236 files
client.ndsu.edu: F:\ level=full, 1943 MB 64:30:53 12383 files
client.ndsu.edu: F:\ level=full, 2071 GB 60:24:53 11955 files
client.ndsu.edu: F:\ level=full, 1915 MB 62:52:11 12431 files
client.ndsu.edu: F:\ level=full, 1911 MB 83:43:01 12246 files
client.ndsu.edu: F:\ level=full, 1875 MB 86:24:49 12299 files
client.ndsu.edu: F:\ level=full, 1844 MB 56:18:40 12683 files
At some point last year (potentially when we went to 7.5.x on the server)
this savegrp notification started having the wrong units for the saveset
size, but not always.
I've done some searching in Powerlink and turned up a similar issue with
the Oracle NMO, esg64466, but nothing else for the standard client savegrp
report.
Anyone else encountered this?
Tim
--
Tim Mooney Tim.Mooney AT ndsu DOT
edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
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
|