FYI,currently OFS is not supported on windows 2003.
when it is, you will be able to ofs the c: drive and get
the ntuser.dat files.

Regards, Paul

TSM_User wrote:

> I believe I did a poor job asking the question due to the responces.  I am 
> concerened specifically with how the TSM client backs up the profile 
> information (ntuser.dat) on Windows 2003 servers.  As has been pointed out 
> many times on the list with 2000 and XP you can get ntuser.dat files that 
> were not backed up directly from the adsm.sys folder.
>
> With Windows 2003 this is not the case.  My question is why? Is it because 
> the SystemState backup includes all profile data.  On Win2003 the ntuser.dat 
> files are still open and skipped by the backup.  That is when I don't have 
> OFS enabled.
>
> As for the explanation on Windows 2003 not supporting open file caching. 
> Well.... you might want to install the latest TSM client and enable OFS.  
> Then try to backup an open file.  I know, I know its not supported... yet.  
> But it works.  Any one out there from IBM that could let us know when you 
> might support it offically?
>
> "Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM> wrote:
> >Von: TSM_User [mailto:tsm_user AT YAHOO DOT COM]
> >On Windows 2003 it appears that a user that is currently logged on does
> not
> >have their ntuser.dat file backed up under adsm.sys like Windows 2000
> and
> >Windows XP.
> >
> >Was eliminating this done for a specific reason? Or is the profile
> data
> >backed up differently on Windows 2003?
>
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Stefan Holzwarth
> >No way to do that with TSM at the moment.
> >We use a presched-cmd for backup of that data with ntbackup
>
> There's a little more to this issue...
>
> TSM uses the operating system's own utilities to back up files that are
> normally open, and would thus be unavailable for backup. For Windows NT
> and Windows 2000 open files are performed by using TSM's open file
> backup service, which involves caching the file's information to a
> temporary file so that the original file would be closed long enough for
> the backup to occur. Windows NT and 2000 support such caching; I suspect
> that NTBACKUP probably backs up open files in just such a way.
>
> Now, enter Windows 2003. Win2003 does not support caching of open file
> transactions for backup purposes; instead, it uses the Windows' volume
> shadow service (VSS), which keeps a copy of specified files on an
> alternate location on the hard disk; this copied file is what would be
> backed up during a TSM client session. Unfortunately, TSM does not yet
> support VSS, and therefore at this time TSM does not support open file
> backups of Windows 2003 clients. (There has been a fair amount of
> discussion of this matter in this list the last few months.)
>
> As Stefan indicates above, the workaround is to use a Windows utility
> (NTBACKUP) to back up any open files. My only addition to his suggestion
> is to run the NTBACKUP as a postschedcmd, not a preschedcmd. There has
> been a history of NTBACKUP sessions occasionally hanging; such a hang
> would prevent the backup from completing successfully. Profiles and
> system files do not change that often; running the NTBACKUP as a
> postschedcmd does not leave much of a hole in the case of a necessary
> restoration, and would allow a successful TSM backup no matter what the
> state of the NTBACKUP session.
>
> I'm off to Minneapolis to teach a TSM class tomorrow!
>
> --
> Mark Stapleton
>
> ---------------------------------
> Do you Yahoo!?
> Win a $20,000 Career Makeover at Yahoo! HotJobs

pbergh.vcf
Description: Card for Paul Bergh