We are having some issues with suspect databases which are mounted via HyperBac 220.127.116.11. The databases have multiple data files and are sized larger than 400gb natively. The backup files are split into two and which are 30-60gb each compressed. Each time a restart of the vm guest occurs these databases come back as suspect. I have set the SQL Server Service to have a service level dependency so that the HyperBac service was required to be online and initialized before SQL Server services would come online.
This has not resolved our instabilities and I would like to get to the latest 5.9 version of HyperBac to see if the instability is resolved in this release.