TSM Server : 5.1.9 running on AIX
TSM Client : 5.3 running on Win 2003 (Lotus Domino Server)
I installed the TSM Client with OFS Support.. I configured it for the snapshot backup..
Archive Backup Size : 131 GB
Free Space on the SnapShotCacheLocation : 234 GB
Archive Backup Location : D:\Lotus\*
Snapshot Provide FS : LVSA
Cache Location : d:\tsmlvsa
Cache Size : 100
FS Idle Retries : 99
FS Idle Max Wait : 5 S
FS Idle Wait Min : 500 MS
The Scheduled Archive Backup & the Manual Archive Backup had failed with following error...
11/22/2007 23:44:36 Normal File--> 14,155,776 \\kanika\d$\Lotus\Domino\data\iNotes6.ntf Sent
11/22/2007 23:47:03 Normal File--> 1,830,813,696 \\kanika\d$\Lotus\Domino\data\Intercom List.nsf ** Unsuccessful **
11/22/2007 23:47:07 --- SCHEDULEREC STATUS BEGIN
11/22/2007 23:47:07 Total number of objects inspected: 163
11/22/2007 23:47:07 Total number of objects archived: 108
11/22/2007 23:47:07 Total number of objects updated: 0
11/22/2007 23:47:07 Total number of objects rebound: 0
11/22/2007 23:47:07 Total number of objects deleted: 0
11/22/2007 23:47:07 Total number of objects expired: 0
11/22/2007 23:47:07 Total number of objects failed: 0
11/22/2007 23:47:07 Total number of bytes transferred: 1.30 GB
11/22/2007 23:47:07 Data transfer time: 85.70 sec
11/22/2007 23:47:07 Network data transfer rate: 16,009.57 KB/sec
11/22/2007 23:47:07 Aggregate data transfer rate: 331.53 KB/sec
11/22/2007 23:47:07 Objects compressed by: 55%
11/22/2007 23:47:07 Elapsed processing time: 01:08:58
11/22/2007 23:47:07 --- SCHEDULEREC STATUS END
11/22/2007 23:47:07 ANS1375E The snapshot operation failed.
11/22/2007 23:47:07 --- SCHEDULEREC OBJECT END KANIKASHED 11/22/2007 22:30:00
11/22/2007 23:47:07 ANS1512E Scheduled event 'KANIKASHED' failed. Return code = 12.
11/22/2007 23:47:07 Sending results for scheduled event 'KANIKASHED'.
11/22/2007 23:47:07 Results sent to server for scheduled event 'KANIKASHED'.
Pls, help me on this..
Pinned topic ANS1375E The snapshot operation failed
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-17T21:17:36Z at 2012-10-17T21:17:36Z by SystemAdmin
SystemAdmin 110000D4XK1188 Posts
Re: ANS1375E The snapshot operation failed2007-12-03T11:05:51ZThis is the accepted answer. This is the accepted answer.Firstly
run chkdsk.exe (with /F for fixes errors).
It was help me with very similar problem.
Using OFA for backup Lotus isn't good idea. You can have problem with data integrity.
In this situation you can backup data using TDP for Mail, when restore it to different location and archive it using B/A client.
It is very simple to automatize.... or stop Domino server...
dhillmohan 270005N7G11 Post
Re: ANS1375E The snapshot operation failed2012-09-06T06:08:03ZThis is the accepted answer. This is the accepted answer.
- WellingtonKMK 060001U6RU
Could you Please help me any one for the below error message.
09/06/2012 00:28:53 ANS5269E The Microsoft Volume Shadow Copy Services writer 'System Writer' current state (VSS_WS_FAILED_AT_FREEZE) is not valid for the current operation or cannot be determined. The last error reported is '00000000'.
09/06/2012 00:29:15 ANS5250E An unexpected error was encountered.
TSM function name : baHandleSnapshot
TSM function : DVssSnapshot::startSnapshot(): VSS[QueryStatus:DoSnapshotSet: E_OUTOFMEMORY (See the Microsoft Application event log for additional VSS messages).
TSM return code : -1
TSM file : incrdrv.cpp (10130)
09/06/2012 00:29:15 ANS1327W The snapshot operation for 'GBISOMAN23\SystemState\NULL\System State\SystemState' failed with error code: -1.
09/06/2012 00:29:15 ANS1228E Sending of object 'GBISOMAN23\SystemState\NULL\System State\SystemState' failed
09/06/2012 00:29:15 ANS5283E The operation was unsuccessful.
09/06/2012 00:29:15 ANS1375E The snapshot operation failed.
SystemAdmin 110000D4XK1188 Posts
Re: ANS1375E The snapshot operation failed2012-10-17T21:17:36ZThis is the accepted answer. This is the accepted answer.
- dhillmohan 270005N7G1
1.There could be a memory issue or less space on c:\drive
2.Vss writers might not be stable
3.Keep the volume shadow copy service in stopped state and try to take a backup.it works some times