RajeshR
ADSM.ORG Senior Member
- Joined
- May 11, 2016
- Messages
- 82
- Reaction score
- 9
- Points
- 0
Dear All,
I have a backup issue on TSM TDP4VE Hyper-V,
Error log says: ""error VSS_E_SNAPSHOT_SET_IN_PROGRESS. 0X80042316""
This is issue happened when 2 schedules conflicted, which tries to trigger backup for 2 separate VM's in same clustered volume from different nodes.
My Hyper-v is in cluster environment with 4 hosts and 2 CSV's.
When 2 schedules conflicted all other schedules following got failed with same error, Even after restarting Hyper-V hosts also manual backup r schedule backup's without conflicts getting failed.
And This looks like APAR IT15657:
This APAR got fixed in 8.1.0 and i have upgraded my TSM TDP4VE Hyper-V to 8.1.0 from 7.1.3 but still no luck and same error occurred.
After upgrade and before upgrade i have performed restart on Hyper-V host and installation is successful.
But when i tried taking IFINCR/IFULL backup for any of the VM it's still getting failed with same above error.
I have tried restoring one of the VM to a different location and with different name and it's successful when the version is 7.1.3 and 8.1.0 both versions working for restore.
Note: We are taking backup only for supported VM generations that is 2nd generation VHDX disks and we do not have any ISCSI devices attached to any of the VM's.
All VSS writers in all 4 Hyper-V hosts are stable state without any error.
Error in detail:
ANS5250E An unexpected error was encountered.
TSM function name : StartSnapshotSet()
TSM function : 'StartSnapshotSet() failed with error VSS_E_SNAPSHOT_SET_IN_PROGRESS.
0X80042316'
TSM return code : -2147212522
TSM file : ..\..\common\vm\HyperV\vsssnap.cpp (1132)
ANS1950E Backup using Microsoft volume shadow copy failed.
Issue started when 2 schedules conflicted, but after restart of hyper-v hosts one VM IFINCR backup completed successfully but i tried for another alone it's got failed again, even after many restarts of hyper-v hosts, still backup's not working.
I have tried taking backup with a different node and completely for a different domain but there also no luck.
Kindly suggest.
Thanks,
Rajesh R
I have a backup issue on TSM TDP4VE Hyper-V,
Error log says: ""error VSS_E_SNAPSHOT_SET_IN_PROGRESS. 0X80042316""
This is issue happened when 2 schedules conflicted, which tries to trigger backup for 2 separate VM's in same clustered volume from different nodes.
My Hyper-v is in cluster environment with 4 hosts and 2 CSV's.
When 2 schedules conflicted all other schedules following got failed with same error, Even after restarting Hyper-V hosts also manual backup r schedule backup's without conflicts getting failed.
And This looks like APAR IT15657:
This APAR got fixed in 8.1.0 and i have upgraded my TSM TDP4VE Hyper-V to 8.1.0 from 7.1.3 but still no luck and same error occurred.
After upgrade and before upgrade i have performed restart on Hyper-V host and installation is successful.
But when i tried taking IFINCR/IFULL backup for any of the VM it's still getting failed with same above error.
I have tried restoring one of the VM to a different location and with different name and it's successful when the version is 7.1.3 and 8.1.0 both versions working for restore.
Note: We are taking backup only for supported VM generations that is 2nd generation VHDX disks and we do not have any ISCSI devices attached to any of the VM's.
All VSS writers in all 4 Hyper-V hosts are stable state without any error.
Error in detail:
ANS5250E An unexpected error was encountered.
TSM function name : StartSnapshotSet()
TSM function : 'StartSnapshotSet() failed with error VSS_E_SNAPSHOT_SET_IN_PROGRESS.
0X80042316'
TSM return code : -2147212522
TSM file : ..\..\common\vm\HyperV\vsssnap.cpp (1132)
ANS1950E Backup using Microsoft volume shadow copy failed.
Issue started when 2 schedules conflicted, but after restart of hyper-v hosts one VM IFINCR backup completed successfully but i tried for another alone it's got failed again, even after many restarts of hyper-v hosts, still backup's not working.
I have tried taking backup with a different node and completely for a different domain but there also no luck.
Kindly suggest.
Thanks,
Rajesh R