02-08-2017 01:00 AM
Hello,
We have received few security warnings regarding Backup exec 2012 and the default SQL 2005 wich it uses.
Microsoft did drop the support for 2005 and we receive those warnings on all clients using Exec 2012.
Did try getting an exception but some clients want an official point of view from Veritas. We would like to update to a newer version of sql (2008?) as updating Exec is out of discuttion.
The question is, what impact has in us, if any and if is safe to update sql to 2008.
Part of waning:
Vulnerability Microsoft SQL Server Elevation of Privilege Vulnerability (MS12-070)
Vulnerability EOL/Obsolete Software: Microsoft SQL Server 2005 Service Pack 4 (SP4) Detected
Thank you
Solved! Go to Solution.
02-08-2017 11:21 PM
02-08-2017 11:21 PM
02-13-2017 02:03 AM
As you mention EOS is one of your concerns and not just the security issue itself, then please be aware BE 2012 goes EOS in May as such you probably need to look at updating BE as well.
BE 16 uses SQL 2014 Express as the default BEDB repository (but can run with SQL 2008 R2 and SQL 2012) and if using our default SQL instance the upgrade wil be done for you (as long as SQL 2005 Express is patched to at at least SP4)
If going to BE 16 (or 15) though be very careful to check the Software Compatbility Lists as we have removed support for a lot of older technologies (including older Exchange and SQL versions and 32bit operating systems on the BE server itself)