Update: IBM finally understood the problem and manage to reproduce the problem in their lab.
They have now created an report (APAR) and working on it.
Here's the APAR (Draft):
------------
Abstract:
Relocate restore operations may fail with ACO5436E and ACO5436E for AlwaysOn databases from non-readable secondary replicas.
Problem Description:
Tivoli Storage Manager for Databases: Data Protection for Microsoft
SQL Server is not able to perform a restore to alternate location of
an AlwaysOn database which was backed up using a non-readable
secondary replica.
The restore fails showing following messages:
ACO5436E A failure occurred on stripe number (0), rc = 428
ACO5436E The SQL server aborted the operation.
Restore of AAGDB failed.
An exception occurred while executing a Transact-SQL statement or
batch.
The file 'C:\Program Files\Microsoft
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\AAGDB.mdf' cannot be
overwritten. It is being used by database 'AAGDB'.
This problem only occurs if the backup of this database was taken
from a non-readable secondary replica.
Customer/L2 Diagnostics:
The problem is Data Protection for SQL Server cannot read the
file information of AlwaysOn databases from a non-readable
secondary replica.
A tdpsqlc query sql command will also return no file sizes for
these databases:
5. tdpsqlc query sql * /sqlserver=Non-readable-AlwaysOnInstance
SQL Server Name ........................ Non-readable-AlwaysOnInstance
SQL Database Name ........................ AAGDB
SQL Database AAG Name ........... ........ AAG
SQL Database Replica Role .. ............. Secondary
SQL Database Sync State Description ...... Synchronized
SQL Database Data Space Allocated ........ 0
SQL Database Data Space Used ............. 0
SQL Database Log Space Allocated ......... 0
SQL Database Log Space Used .............. 0
SQL Database Options .....................
Tivoli Storage Manager Versions Affected:
Tivoli Storage Manager for Databases Version 6.4 and 7.1:
Data Protection for Microsoft SQL Server
Initial Impact:
Medium
Additional Keywords:
TSM High Availability Primary AAG groups replication relocate position path directory
Local Fix:
The database can be restored into original location without any
problem.
Enable secondary replicas for readable access to prevent from this situation.