No. From your message:

>>\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent]

This is an SQL backup file. It appears that this could have been the
culprit, since it is mentioned in the scheduled backups log.

--
Mark Stapleton (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
Office 262.521.5627  

>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
>Behalf Of Joni Moyer
>Sent: Tuesday, April 26, 2005 1:54 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: snapshot issue
>
>Hi Mark,
>
>When you say that it is most likely a large SQL backup file 
>being open when
>I do a backup, could you be referring to a .tar file that is 
>used to backup
>the SQL database?  And if so, because the .tar file is open it 
>is trying to
>invoke the snaphot technology?  If so, is there a way to turn 
>off snapshot
>capabilities?  Thanks again!
>
>********************************
>Joni Moyer
>Highmark
>Storage Systems
>Work:(717)302-6603
>Fax:(717)302-5974
>joni.moyer AT highmark DOT com
>********************************
>
>
>
>             "Stapleton, Mark"
>             <mark.stapleton@B
>             ERBEE.COM>                                        
>         To
>             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
>             Dist Stor                                         
>         cc
>             Manager"
>             <[email protected]                                 
>    Subject
>             .EDU>                     Re: snapshot issue
>
>
>             04/26/2005 02:41
>             PM
>
>
>             Please respond to
>             "ADSM: Dist Stor
>                 Manager"
>             <[email protected]
>                   .EDU>
>
>
>
>
>
>
>Please refer to page 638 in the Messages manual for TSM version 5.2, or
>by running help from the TSM command-line client and paging down to
>message number ANS1380E. (You may have a typo in your posting below.)
>
>Your problem is likely being caused by an overly large SQL backup file
>that is for some reason open during your backup, thus invoking the
>snapshot technology in an attempt to perform a backup of it.
>
>--
>Mark Stapleton (stapleton AT berbee DOT com)
>IBM Certified Advanced Deployment Professional
>Tivoli Storage Management Solutions 2005
>Office 262.521.5627
>
>
>>-----Original Message-----
>>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
>>Behalf Of Joni Moyer
>>Sent: Tuesday, April 26, 2005 1:35 PM
>>To: ADSM-L AT VM.MARIST DOT EDU
>>Subject: snapshot issue
>>
>>Hello Everyone!
>>
>>I was wondering what might cause the following error to occur?
>> I had the
>>owner of hmch1134, which is a WinNT 5.0 server at the TSM
>>5.2.2.0 client
>>level ask why they are receiving the errors.  I don't have
>>anything set on
>>the TSM server and they are not aware of what might be causing
>>snapshots to
>>be tried.  Does anyone have any ideas?  I am sorry for my ignorance of
>>Windows servers, but I really do not have any knowledge of
>>that OS.  Thank
>>you in advance!
>>
>>Node Name: HMCH1134
>>Session established with server TSMPROD: AIX-RS/6000
>>  Server Version 5, Release 2, Level 2.5
>>  Data compression forced off by the server
>>  Server date/time: 04/05/2005 01:45:01  Last access:
>>04/05/2005 01:44:49
>>
>>ANS1380W The snapshot operation failed. The filesystem write activity
>>prevented the Logical Volume Snapshot Agent from satisfying the
>>SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options.
>>
>>ANS1377W Unable to perform operation using a point-in-time copy of the
>>filesystem on '\\hmch1134\e$'. The backup/archive operation
>>will continue
>>without snapshot support.
>>
>>Normal File-->        40,159,744
>>\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent]
>>Archive processing of
>>'\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak'
>>finished without failure.
>>
>>********************************
>>Joni Moyer
>>Highmark
>>Storage Systems
>>Work:(717)302-6603
>>Fax:(717)302-5974
>>joni.moyer AT highmark DOT com
>>********************************
>>
>