The XP system state is about 300MB, much like a Win2K system. It's Vista where the weirdness kicks in...
On 12/7/07, Tyree, David <[EMAIL PROTECTED]> wrote: > > I did a backup using the GUI and selected system state along with the C: > drive. The backup was 8 gig when it finished. > > I went back and did a C: drive only and it was only a few hundred meg. > Then I did a system state only and got the 8 gig again. > > That system state in Vista is just crazy. I need to go back and really > look at some of my servers and see just how big the system state backups > are. I'll also take a close look at a few Win XP Pro desktops that I'm > backing up and see what the numbers look like. > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Wanda Prather > Sent: Friday, December 07, 2007 2:35 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Vista oddness > > Don't know myself, but someone else posted a while back that the System > State on Vista is many GB. > > That is consistent with what you are seeing - a scheduled backup will do > the > System State, whether things have changed or not. And selecting the C: > drive will not do the system state. > > As a test, try your backup from thh GUI again, but this time select > System > STate as well as the C: drive, see if the results change... > > And please post back the results! > > > > On 12/6/07, Tyree, David <[EMAIL PROTECTED]> wrote: > > > > We are testing Vista and I'm seeing something odd. TSM > seems > > to want to do almost a full backup every time it runs automatically. > > > > I'm running the 5.5.0 client on a VMware (6.0) Vista > > Ultimate box that is talking to a TSM server running 5.4.1 on Windows. > > > > The backup on the Vista machine is automated using the > > DSMCAD service. The incremental backup kicks off at the correct time, > > but it ends up doing a full backup. > > > > I've looked through the dsmsched log on the Vista machine > > and I'm seeing where it has contacted the TSM server and picked up the > > schedule name and the action. The schedule name is correct and the > > action is set to incremental. And several lines in the dsmsched log > > mention "Incremental backup of '\\is-vista-test-d\c$' finished". > > > > The log shows everything just like what I would expect to > > say, the issue is that it ends up backing up almost 8 gigs of files > each > > time the backup runs. I've run scheduled incremental backups almost > back > > to back on the machine and it picks up 8 gigs each time. The machine > is > > just sitting there between backups; I'm not doing anything on the > > machine in between. > > > > If I open the GUI and tag the c drive for incremental > backup > > it goes out and looks at all the files on the drive and backs up a few > > dozen files and it done. Just like I would expect it to. > > > > If I go to the baclient folder and run "dsmc incr" from the > > command line it ends up doing what looks like a full backup. > > > > > > > > In the last couple of hours I had a scheduled backup run > > that moved about 8 gigs worth of files. Right after that finished I > did > > a c drive backup from the GUI. It moved a few hundred megs of files. > > Right behind that I did the "dsmc incr". So far it's moved over 4 gig > of > > files and is still running. > > > > > > > > Anybody got a idea what's going on here? > > > > > > > > > > > > PS, Vista looks good. Except most of our software doesn't > > run. The UAC (User Account Control) is a real piece of work. And they > > have moved everything around so you can't find what you're looking > for. > > But at least it looks good.... > > > > David Tyree > > Interface Analyst > > South Georgia Medical Center > > 229.333.1155 > > > > Confidential Notice: This e-mail message, including any attachments, > is > > for the sole use of the intended recipient(s) and may contain > > confidential and privileged information. Any unauthorized review, > use, > > disclosure or distribution is prohibited. If you are not the intended > > recipient, please contact the sender by reply e-mail and destroy all > > copies of the original message. > > > > > > >