> I would like to ignore them, but they will eventually cause problems as
the
> size of the dsmerror.log increases creating another housekeeping /
> monitoring task.
>
>
>
> But thankyou, at least I know there's no big problem.
>
> Matt.
>
> ______________________________________________
> Matthew Warren.                         GZPTXW
> EDS Core Infrastructure -- Storage Management.
> Wavendon Tower +44(0)190828(4481)
> matthewjames.warren AT eds DOT com
> ______________________________________________
>
>
>
>
>
> >-----Original Message-----
> >From: Andy Raibeck [mailto:Andrew_Raibeck AT TIVOLI DOT COM]
> >Sent: 11 December 2000 03:20:PM
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: Re: NT GetBackupStream & TransWin32RC
> >
> >
> >You can safely ignore these messages. These are logged for
> >files that can
> >not be opened by TSM because another application has already
> >opened them
> >for exclusive use (such as NTUSER.DAT files or *.pst Exchange mailbox
> >files). This can be considered a part of normal TSM processing.
> >
> >These messages are really intended for use by development for
> >diagnostic
> >purposes, and are not intended for end-user consumption. However, in
> >practice they aren't particularly informative (even to developers), and
> >they only cause confusion. Over time they will eventually be
> >eliminated,
> >unless absolutely necessary to capture a run-time problem.
> >
> >Regards,
> >
> >Andy
> >
> >Andy Raibeck
> >IBM/Tivoli
> >Tivoli Storage Manager Client Development
> >e-mail: andrew.raibeck AT tivoli DOT com
> >"The only dumb question is the one that goes unasked."
> >
> >
> >"Warren, Matthew James" <matthewjames.warren AT EDS DOT COM>@VM.MARIST.EDU> 
> >on
> >12/11/2000 06:51:31
> >
> >Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >
> >To:   ADSM-L AT VM.MARIST DOT EDU
> >cc:
> >Subject:  NT GetBackupStream & TransWin32RC
> >
> >
> >
> >Hello TSM'ers,
> >
> >
> >We ahve recently installed a number of NT 3.7 clients. Some of them are
> >backing up fine, but others are filling up the dsmerror.log
> >with hundreds
> >of
> >lines that look like the following;
> >
> >
> >02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:42 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:42 TransWin32RC(): Win32 RC 32 from fioGetAttrib():
> >GetBackupStreamInfo
> >27-11-2000 20:02:45 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:48 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:48 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:48 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:48 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:48 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >27-11-2000 20:02:49 GetBackupStreamSize(): CreateFile(): Win32 RC = 32.
> >
> >
> >
> >interspersed with failures for files as the file is in use by another
> >process. Serialization is set to shared dynamic.
> >
> >Is there a way of preventing these hundreds of errors? why are
> >we getting
> >them as well as the errors for 'file in use by another process'?
> >
> >Thanks,
> >
> >Matt.
> >
> >______________________________________________
> >Matthew Warren.                         GZPTXW
> >EDS Core Infrastructure -- Storage Management.
> >Wavendon Tower +44(0)190828(4481)
> >matthewjames.warren AT eds DOT com
> >______________________________________________
> >