08-18-2020 09:02 PM
08-19-2020 12:48 AM
Any error?
08-19-2020 01:55 AM
08-19-2020 02:02 AM
I would always recommend checking the appropriate SCL (Software Compatibility List) for whichever version of Backup Exec you are planning to migrate to.
The SCLs for the different versions can be found here:https://www.veritas.com/content/support/en_US/article.100040087
Unfortunately CU17 for Exchange 2016 has only just been released in the last couple of months (June 2020) whereas BE15 is quite an old version of Backup Exec (base version over 5 years old, FP5 over 4 years old) consequently to get a version of BE that supports something as new as CU17, you would need to migrate to the latest release (v21.0) as even v20.6 only supports up to CU15.
08-19-2020 05:48 AM - edited 08-19-2020 06:01 AM
@kf2013 No error as the backup to B2D was successful. The only problem is no individual items can be resorted as it only shows database when I tried restoring.
08-19-2020 05:50 AM - edited 08-19-2020 06:01 AM
@pkh Yes I'm aware it's not supported.
I was actually trying to restore individual items of Exchange 2016 that I've backed up to a B2D folder in BE15, but it only shows dataset when I tried restoring but no individual items.
08-19-2020 05:55 AM - edited 08-19-2020 06:02 AM
@PJ_Backup So looks like we may have to consider migrating to BE 21 then...
08-19-2020 06:09 AM
That would be my recommendation. If you still have problems then you can always raise a support call.
08-20-2020 10:57 PM
Starting with Exchange 2016 CU5 the DB schema of Exchange was updated by Microsoft and older versions of BE like BE15 are not able to restore single items until you update BE to the latest version. Back then also other tools like Veeam was affected by this schema change.