Wanda,

My calculations

Current Windows = 3 Gb in c$; new Windows = 15 Gb in c$.  That's installed out 
of the box.  If we collocated by filespace, the $c tape would hold about 250 
clients from current Windows, and about 50 clients from new Windows.

Current Windows = 16k files so 16k entries in TSM db or 12.8 Mb; new Windows = 
71k files so 71k entries in TSM db or  56.8 Mb.  There are today 2140 WinNT 
clients that will be upgraded to or replaced by new Windows.

Current Windows Systemobject = 600 Mb; new Windows systemobject = 7+ Gb.  TSM 
has 2.5-3 Gb of storage for Systemobject for current Windows;  New Windows will 
have 28-35 Gb per client.  The exception is the AD clients which keep 180 
versions or 108 Gb for current Windows, which translates to 1.25 Tb in new 
Windows.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Wanda Prather
Sent: Thursday, November 05, 2009 1:29 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Win2008 System State

Yes, systemstate backups have always been fulls.  (I believe there was some
mumbling about Win2K3 changing something to make it possible to do
incrementals instead of fulls, but I've never seen any difference, and no
further mumbling has ensued...sort of like the mumbling that told us Vista
would be better than those XP annoyances...)

What you have NOT mentioned is the impact of SystemState backups on the TSM
DB, because in WIn2K the systemstate backup is at least 2000 objects.  Per
systemstate backup, meaning per day.  Couple thousand more for 2003.
Anybody figured out the number for 2008?

I've had customers where I've found a SUBSTANTIAL percentage of their TSM DB
taken up with (pretty useless) system state backups, with just WIn2K and
Win2K3.   Win2008 will blow up a lot of TSM data bases, looks like.

W