Unsolved

This post is more than 5 years old

30 Posts

541

June 20th, 2006 14:00

question about fields and save set sizes reported out of GUI

i ran the following command at the prompt:

C:\>mminfo -q "ssid=1922395551" -r "ssid,volume,savetime,totalsize,capacity,written,read,fragsize,sumsize,level,name"

The output of the command:

ssid volume date total capacity written read size size lvl name
1922395551 Servers.001 6/18/2006 2048007560 0 KB 728 GB 0 KB 2000 MB 2000 MB full E:\
1922395551 Servers.001.RO 6/18/2006 2048007560 0 KB 0 KB 2863 GB 2000 MB 2000 MB full E:\

Note the size of the save set.

When I go into the GUI, under MEDIA, VOLUMES, and right click on the same volume and say, "SHOW SAVE SETS", it displays the total size as

8671MB

(note that i outputed every size field I could find in the documentation to make sure I wasn't using the wrong field)

What am I missing? Or can someone tell me what field the GUI is using and what number I should trust?

-Eric

PS - Running 7.3 on Windows 2003. (save set was from a Windows machine e:\ volume)

Message was edited by:
Eric Davis

(added network version and host/client information)

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

June 20th, 2006 14:00

What does the daemon.log say - what is the save written for that saveset when done saving? Try to upgrade to 7.3.1 and retest it again. Before that run nsrck -m.

30 Posts

June 20th, 2006 16:00

Ok..as suggested, I checked the Daemon.log for the saveset in question (although save set ID's aren't in there, I saw these entries as it relates to the host and volume backed up.

06/18/06 08:27:01 nsrd: myhostname:E:\ continuing save 2000 MB
06/18/06 08:27:01 nsrd: myhostname:<1>E:\ saving to pool 'Servers' (Servers.001)
06/18/06 08:49:57 nsrd: myhostname:<1>E:\ continuing save 2000 MB
06/18/06 08:49:57 nsrd: myhostname:<2>E:\ saving to pool 'Servers' (Servers.001)
06/18/06 09:01:03 nsrd: myhostname:<2>E:\ continuing save 2000 MB
06/18/06 09:01:10 nsrd: myhostname:<3>E:\ saving to pool 'Servers' (Servers.001)
06/18/06 09:13:23 nsrd: myhostname:<3>E:\ continuing save 2000 MB
06/18/06 09:13:23 nsrd: myhostname:<4>E:\ saving to pool 'Servers' (Servers.001)
06/18/06 09:17:10 nsrd: myhostname:<4>E:\ done saving to pool 'Servers' (Servers.001) 671 MB

This totals exactly to what the GUI says, 8671MB.

when I do this command:

mminfo -q "volume=Servers.001" -r "ssid,volume,savetime,written,level,name"

I found these entries, (I edited the output with only the relevant data)

ssid volume date written lvl name
1888841902 Servers.001 6/18/2006 728 GB full <1>E:\
1872065231 Servers.001 6/18/2006 728 GB full <2>E:\
1855289288 Servers.001 6/18/2006 728 GB full <3>E:\
1838513054 Servers.001 6/18/2006 728 GB full <4>E:\
1922395551 Servers.001 6/18/2006 728 GB full E:\

What I don't understand is why are bracket things being put on the saveset name?

If I do this:

mminfo -q "volume=Servers.001,name='E:\'" -r "ssid,volume,savetime,sumsize,level,name"

I will ONLY get info on SSID # 1922395551.

So, question is, how is the Networker GUI getting the sum total of this volume?

Basically, i want to generate an MMINFO command line that will give me exactly what the GUI is giving....anyone have suggestions?

2 Intern

 • 

1.1K Posts

June 20th, 2006 16:00

Run a media database check to see if that helps any but I suspect not. What it may be is that the 2GB reported is the compressed size on the disk device, and the 8.7GB is the uncompressed size. This should be an easy one to check - firstly you should know the size of the file system you are backing up; secondly as it is an advanced file type device you can find the file corresponding to the saveset ID in the directory you configured as your AFT device and check what size it is.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

June 21st, 2006 01:00

This makes sense now. It seems as you are running 5.x based client/server. In 5.x world each ssid bigger than 2GB was broken to 2GB chunks. You could see that by <1>, <2>, etc. Search for that in forum and you will find a thread where I explained that more in details before. There pssid (parent ssid) which determined previous ssid.

What is important to note is that each 2GB chunk had its own ssid! And that is explaination of your "issue". If both server and client in your case are 7.3 (client is according to your first post) move to 7.3.1.
No Events found!

Top