Forum Discussion
Can you share some more info about the SQL version?
As you have a CASO environment; on which server did you create the job (CAS or MBES) and on which server did the job run on?
Have you checked if you can see the resource on the CAS server itself?
To confirm that we understand your latest reply correct; if you go via the storage then you can select and successfully restore your SQL data?
Veritas SQL Verison is 2016
It doesn't matter which server creates backup jobs or runs them, We tested it, on all servers we have this problem. for more information we can say in this farm we have more than 3 Backup management servers and one CAS, on the older version of the management backup we can see backup sets but on the updated server we can see backup sets on restore wizard but the backup was successful and create a valid backup sets that we can see them on the media.
- Gurvinder3 years agoModerator
not sure what exactly may be causing this. Can you open a tech support case for this issue ?
Share a screenshot of the backup selections if possible. For a test , if you install BE on a new server with 21.2 , does this new BE server backup of that resource show the same problem ?
BE 21.4 is available as well, would you patch it on CAS and test the backup there and see if it helps ?
https://www.veritas.com/content/support/en_US/downloads/detail.REL523933 ( BE 21.4 download link (sign in to download))
Related Content
- 3 months ago
- 5 months ago
- 21 days ago
- 11 months ago