Windows 2000 and 2003 clients - OFS and system objects

[thaddad]

Do I understand this correctly about TSM client support...?



On Win2000 machines, LVSA can be used for Open File support

and all system data is under SYSTEMOBJECT (using INCLUDE.SYSTEMOJECT or Backup SYSTEMOBJECT)??



On Win2003 machines, LVSA can be used for OFS also but now system data is divided between SYSTEMSTATE and SYSTEMSERVICES using VSS service of Windows..??



My client level on either is currently 5.2.3.0.....

 

[may]

Yes,

u r approximativly right!



there is no LVSA on W2K3, it is replaced by VSS.



and yes the "SSYTEM OBJECT" are devided in three part "SYSTEM STATE" SYSTEM SERVICES" and "ASR".



but I, I have an anther Question : why i can't backup the "NTUSER.Dat" with a

Include.Fs "C:" FILELEVELTYPE=SNAPSHOT SNAPSHOTFSIDLEWAIT=0S

SNAPSHOTCACHELOCATION D:\TSMCache



is specified.



i 've installed the "OFS" module and it is still telling me that

"The file is being used by another process"



Why ???

why??

:cry:

 

[CBell]

Actually, the ntuser.dat plus the associated logs are listed in the recommended excludes, but may be needed for PC/laptop restores. I deal with servers, so I have client option sets set up for the ntuser.dat stuff. Maybe v5.3 addresses this, I have yet to get my grubby hands on it...

 

[may]

in fact,

I am testing the "OFS" module with the w2k3 .



and there is no restriction for on this client dsm.opt nor in the client option set !



so i should be able to do the backup!



so ..... ??

 

[CBell]

Soooo...I am saying IBM recommends they be excluded for a reason. They can only be backed up by ensuring that the user account they are tied to is logged completely out. Otherwise, they are in exclusive use, and are therefore restricted from backup access, OFS or not. OFS is pretty neat, but it doesn't get evrything all the time.

 

[may]

hi CBell,

i found the reason here it is :



OFS should not be used for backing up locked Windows system files. The TSM Client has advanced features for backing up data contained within these files. The backup of the system data that is contained in these files requires additional processing and must be backed up in a group to allow for a successful restore. The included TSM Client features "System Objects" (Windows 2000 and Windows XP) and "System State" (Windows Server 2003) are used for the backup and restore of this data. These files are "excluded" from the TSM File level backup.



thank s for ure responses

 

[mvm]

So, what's now ?



Can we use OFS on Windows 2003 or not ?

How can we backup system state, system services and ASR using VSS and other drives with OFS?



In fact I use Command line throught a VBScript like this one:

If OperatingSys = "WIN2K" Then

if arg_nosystemstate = 0 then

TSM_Options = "-optfile=dsm.opt" & SnapOption

TSM_CMD = "backup SYSTEMOBJECT"

Call TSM_Execute(TSM_Out_File,TSM_CMD,TSM_Options)

end if

If arg_partition = 0 or arg_partitionC = 1 then

TSM_CMD = TSM_action & "C:"

Call TSM_Execute(TSM_Out_File,TSM_CMD,TSM_OptionsPart)

end if

TSM_CMD = TSM_action & DOMAIN_DATA

Call TSM_Execute(TSM_Out_File,TSM_CMD,TSM_OptionsPart)

End If



If OperatingSys = "WIN2003" Then

if arg_nosystemstate = 0 then

TSM_Options = "-optfile=dsm.opt" & SnapOption

TSM_CMD = "backup SYSTEMSTATE SYSTEMSERVICE " & DOMAIN_DATA

Call TSM_Execute(TSM_Out_File,TSM_CMD,TSM_Options)

end if

TSM_CMD = TSM_action & DOMAIN_DATA

Call TSM_Execute(TSM_Out_File,TSM_CMD,TSM_OptionsPart)

End If



Sub TSM_Execute (TSM_Out_File,TSM_CMD,TSM_Options)

TSM_EXE = """"& TSM_DIR & "BaClient\dsmc.exe"""

TSM_Run = TSM_EXE & " " & TSM_CMD & " " & TSM_Options

WshShell.CurrentDirectory = TSM_DIR & "BaClient"



RC = WshShell.Run(TSM_Run,1,true)

If RC <> 0 Then

Log_File.WriteLine(time & " ERROR - Command")

Log_File.WriteLine(" " & TSM_Run)

Log_File.WriteLine(" exited with RC=" & RC & " !")

Else

Log_File.WriteLine(time & " Info - Command")

Log_File.WriteLine(" " & TSM_Run)

Log_File.WriteLine(" exited with RC=" & RC & " !")

End If

Check_RC(RC)



End Sub

 

[MarkAnderson]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>Can we use OFS on Windows 2003 or not ?</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>



32-bit 2003 Tivoli says LVSA works 'as is' with 5.3.

64-bit 2003 Tivoli says LVSA doesn't work at all with 5.3.



And in my experience, the as-is equals 'not so much'. The most common thing I see is the cache doesn't flush after the commit, so the drive fills up with logs.



I would stay at your version level until 5.4 comes out if you want working OFS without a hundred headaches and crashes.