The following issues have been fixed:
• On start-up some databases show as suspect due to the sequence in which the HyperBac service starts relative to SQL Server.
I think this is a similar issue.
I have a workaround which involves running a shutdown and startup script to take the databases OFFLINE and return them ONLINE after boot. However, I do not wish to continue such a task.
Hyperbac Configuration Manager shows these values in the Status File:
ServiceVersion=220.127.116.11 UPDATE value is now = 18.104.22.168
KernelVersion=22.214.171.124 UPDATE value is now = 126.96.36.199
Do I have any other options?
Are others experiencing the same issue?