Hi,
we are running a new Windows 2012 R 2 Datacenter Hyper-V Cluster, installed TSM Client 7.1.02 and TBMR 7.1.2. Scheduled Backups are running correctly and completed successfuly with no errors in scheduler log.
All local drives, the quorum itself (attached as drive w: and systemstate is successful backed up. We don't want to backup the VM's, because they make a backup themself.
From dsminfo.txt we use the followed cluster related parameters:
CLUSTERDISKSONLY: YES
CLUSTERNODE: NO
The Cluster is configured to use shared VHDX, and during backup genetrates error in the Hyper-V-Shared VHDX eventlog with entries with eventid 80:
Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy348. Error: The specified request is not a valid operation for the target device..
But when i checked the backupdata on tsm server all seems fine, nothing missed. Also VSS writers all stable.
Google isn't very helpful in this.. :-(
Any clue?
All helpful comments / questions are appreciated
Regards
we are running a new Windows 2012 R 2 Datacenter Hyper-V Cluster, installed TSM Client 7.1.02 and TBMR 7.1.2. Scheduled Backups are running correctly and completed successfuly with no errors in scheduler log.
All local drives, the quorum itself (attached as drive w: and systemstate is successful backed up. We don't want to backup the VM's, because they make a backup themself.
From dsminfo.txt we use the followed cluster related parameters:
CLUSTERDISKSONLY: YES
CLUSTERNODE: NO
The Cluster is configured to use shared VHDX, and during backup genetrates error in the Hyper-V-Shared VHDX eventlog with entries with eventid 80:
Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy348. Error: The specified request is not a valid operation for the target device..
But when i checked the backupdata on tsm server all seems fine, nothing missed. Also VSS writers all stable.
Google isn't very helpful in this.. :-(
Any clue?
All helpful comments / questions are appreciated
Regards
