lightness
ADSM.ORG Member
- Joined
- Mar 7, 2006
- Messages
- 18
- Reaction score
- 0
- Points
- 0
Hi there,
I have been struggling with an issue where our container pool volumes become unavailable due to an unexpected error which is affecting our data protection for VMware backups and restores. Our TSM server version is 8.1.10.100 and TDP for VMware is version 8.1.10.0 I have both a Windows datamover and a Linux datamover configured. Here is the info from the actlog for one of the containers affected:
ANR0204I The container state for
G:\DATA\0e\0000000000000efd.ncf is updated from
AVAILABLE to UNAVAILABLE. (SESSION: 127472)
08/30/2021 23:40:08 ANR3660E An unexpected error occurred while opening or
writing to the container. Container
G:\DATA\0e\0000000000000efd.ncf in stgpool MAIN has
been marked as UNAVAILABLE and should be audited to
validate accessibility and content. (SESSION: 127472)
When I run an audit to scan the container it states that the header is corrupt for the container and marks the data as damaged. I then re-run an audit to remove damaged and all is cleared until it happens again.
Hardware support did find a possible issue with the SAS cables that attach the storage to the server, they have been fully replaced and I am still getting the same behaviour.
Just wondering if anyone else has experienced this and if so any possible fixes??
Any info would be greatly appreciated.
I have been struggling with an issue where our container pool volumes become unavailable due to an unexpected error which is affecting our data protection for VMware backups and restores. Our TSM server version is 8.1.10.100 and TDP for VMware is version 8.1.10.0 I have both a Windows datamover and a Linux datamover configured. Here is the info from the actlog for one of the containers affected:
ANR0204I The container state for
G:\DATA\0e\0000000000000efd.ncf is updated from
AVAILABLE to UNAVAILABLE. (SESSION: 127472)
08/30/2021 23:40:08 ANR3660E An unexpected error occurred while opening or
writing to the container. Container
G:\DATA\0e\0000000000000efd.ncf in stgpool MAIN has
been marked as UNAVAILABLE and should be audited to
validate accessibility and content. (SESSION: 127472)
When I run an audit to scan the container it states that the header is corrupt for the container and marks the data as damaged. I then re-run an audit to remove damaged and all is cleared until it happens again.
Hardware support did find a possible issue with the SAS cables that attach the storage to the server, they have been fully replaced and I am still getting the same behaviour.
Just wondering if anyone else has experienced this and if so any possible fixes??
Any info would be greatly appreciated.
