Author: David Gold-news <dave2 AT CAMBRIDGECOMPUTER DOT COM>
Date: Mon, 15 Feb 2010 10:08:42 -0500
Hi, I've been doing some sizing analysis, and have noticed that mminfo reports show the amount written to a device (AFTD, in this case), rather than the amount of source data. So when using compressa
Yup. That's what the server sees. I'd say that "save set" is an overloaded term and may mean different things in different contexts, and adding "size" on the end doesn't make it much clearer. However
Author: David Gold-news <dave2 AT CAMBRIDGECOMPUTER DOT COM>
Date: Wed, 17 Feb 2010 09:03:49 -0500
Hi, Thanks for your thoughts. I think what threw me off is that the media database does include both server-side and client-side info--ssinsert versus savetime as a primary example--and I assumed tha
In regard to: Re: [Networker] mminfo size reporting when using compresasm?,...: I've seen a lot of sites use backup reports for sizing--so this is probably something that has hit a lot of sites witho
Author: Preston de Guise <enterprise.backup AT GMAIL DOT COM>
Date: Thu, 18 Feb 2010 09:41:32 +1300
The problem as such is that it's effectively the client that reports (via the save output to the server) the amount of data transferred ... and that's the compressed size. I blogged about this a whil
Author: David Gold-news <dave2 AT CAMBRIDGECOMPUTER DOT COM>
Date: Thu, 18 Feb 2010 09:32:08 -0500
Tim, good idea on checking the client. Unfortunately, that isn't a specific enough, it just shows a total. MB:174690 Dave In regard to: Re: [Networker] mminfo size reporting when using compresasm?,..