Upgrade Backup Exec 2010 R3 SP4 To BE 16
Are you currently using Backup Exec 2010 R3 SP4 and planning to upgrade to Backup Exec 16 ? If so, then Veritas recommend you to read this blog and follow the steps before installing Backup Exec 16. Backup Exec supports a direct upgrade from Backup Exec 2010 R3 SP4 to Backup Exec 16. However, specific to 2010 R3 SP4, you need to ensure that your current SQL version is compatible with Backup Exec 16. The Backup Exec 16 Environment Check will block an upgrade , if your implementation is using a local SQL Express instance created by Backup Exec with the name ‘BKUPEXEC’, which is installed with SQL 2005 SP3. Refer to the following screenshot. To avoid this error you must have SQL 2005 SP4 installed, which is compatible with Backup Exec 16. SQL 2005 SP4 version can be installed with Windows updates (if it is enabled on your setup). Make sure your systems are fully patched with Windows updates. You can also download SQL 2005 SP4 from Microsoft: http://www.catalog.update.microsoft.com/Search.aspx?q=KB2463332 To verify that the correct version of SQL is installed on your setup, go to the SQL Server Configuration Manger and select SQL server 2005 services > SQL Server > SQL server (BKUPEXEC) > Properties. The Service Pack Level now displays 4. Note: If you select an existing instance of SQL Server that is not installed by Backup Exec, you must upgrade the SQL Server to SQL 2008 R2 SP2. When you upgrade from previous versions, Backup Exec automatically converts your existing definitions, configurations, and jobs to the current version. Some of your jobs may be combined or moved. After the migration completes, Backup Exec displays the Migration Report that you must review and acknowledge before Backup Exec continues the upgrade process. In this report, you can see how your jobs were migrated. Veritas recommends that you review the Migration Report thoroughly to determine how your existing jobs have changed and how you may need to adjust your jobs manually. The Migration Report is available for viewing from the Backup Exec Administration Console or the Home tab at any time after the migration completes. The Migration Report is stored in the following path: \Program Files\Veritas\Backup Exec\Data\MigrationReportFiles\Data-Migration-Report.html. References Upgrade Bacup Exec 2010 R3 to BE 15 Veritas Backup Exec 16 Version Upgrade Process Upgrading Backup Exec 15 to 16
Backup Exec Install Blog (A Common SQL 2008 R2 Upgrade Failure)
Today's blog is designed to help some of our customers with an issue they may experience during the upgrade to Microsoft SQL Server 2008 R2 Express with Backup Exec 2014. We are seeing a number of failures that return the following error in the install log: "Failed to install SQL Express BKUPEXEC instance with error -2067922409".Backup Exec Install Blog (DLO7 Upgrades)
When your users are mobile, protecting their data requires applications that detect a network presence and copy the data up to the network for backup during a regular nightly backup job. In Backup Exec 2010 and earlier versions (going back to the 10.x days), a Backup Exec option called the Desktop and Laptop Option (DLO) did just that.Backup Exec Install Blog (Why BE Installs a 32bit SQL 2008 Instance)
Hello again! Today, I want to address a question that I anticipate some customers may ask: "Why does Backup Exec 2014 install a 32-bit instance of Microsoft SQL Server 2008 during clean installs and upgrades?" This topic received much discussion as we were deciding which version of SQL to use for Backup Exec 2014. There were several requirements:
