Best practices for Backup Exec 2014 installation
|Article:HOWTO74426|||||Created: 2012-03-07|||||Updated: 2014-07-15|||||Article URL http://www.symantec.com/docs/HOWTO74426|
Best practices include tips and recommendations to help you install or upgrade Symantec Backup Exec 2014 more effectively. For more information about installing Backup Exec, see the Backup Exec 2014 Administrator's Guide.
The following best practices are for preparing to install or upgrade Backup Exec:
Visit the Symantec Support Web site to check for updates to the documentation.
Review the Readme document and Documentation Addendum for updates to the Backup Exec Administrator's Guide.
Review the "Features or requirements no longer supported by Backup Exec 2012 and later" section of the readme.
Use only standard ANSI characters for the computer name of the computer on which you want to install Backup Exec. You may receive errors if you install Backup Exec on a computer with a name that uses non-standard characters.
Ensure that the most recent version of Microsoft.NET framework is installed on the computer on which you want to install Backup Exec. Installing the .NET framework expedites Backup Exec's installation process.
Run Microsoft Windows update.
Document your current configuration and settings before you upgrade Backup Exec. You can verify that your configuration after the upgrade is complete.
Upgrade the central administration server first if you perform a rolling upgrade in an existing Central Admin Server Option (CASO) environment. Upgrade the managed Backup Exec servers as soon as possible afterwards.
Back up your server before you install or upgrade any software, including Backup Exec. Copy Backup Exec's Catalogs and Data folders for additional security.
Pause or stop all jobs before upgrading Backup Exec. If you run Backup Exec jobs during an upgrade, the jobs fail.
Pause all communications with managed Backup Exec servers in CASO environments.
Delete any unnecessary job history and alert history before an upgrade to help expedite the process.
Disable any monitoring utilities that may restart services.
Run the Environment Check Utility. The Environment Check Utility automatically runs during local installations. Symantec recommends that you also run the utility for remote installations. You should address all warnings and errors before you install Backup Exec.
Perform database maintenance on your Backup Exec Database immediately before an upgrade.
Close all instances of the Backup Exec Administration Console before the upgrade.
The following best practices are for during the installation process and the upgrade process:
Run Symantec LiveUpdate before you install or upgrade Backup Exec.
Use an uninterrupted power supply (UPS) for your Backup Exec server during the installation. A UPS helps ensure that you do not have a failed installation due to a power outage.
Install Backup Exec to a drive that is neither compressed nor encrypted if you use SQL Express for the Backup Exec Database.
Ensure that you review and acknowledge the upgrade notice about the disk reclamation process called data lifecycle management (DLM) during the upgrade.
Ensure that you review and acknowledge the Migration Report after the migration completes to continue the upgrade process.
Wait until after the installation to make configuration changes. Do not make configuration changes during the installation.
Run the installation wizard from the local server, from a DVD image on the local server, or by push-installing from the local server.
The following best practices are for after the installation process or the upgrade process:
Run Symantec LiveUpdate to check for any Backup Exec updates.
Run Microsoft Windows Update. Backup Exec uses many Microsoft technologies that may have been updated since Backup Exec's release.
Monitor your disk space regularly to prevent disk space problems. Backup Exec's space requirements vary depending on usage and installed options. The requirements in the Administrator's Guide do not include space estimates for the Simplified Disaster Recovery files, catalogs, or job logs, for example.
Article URL http://www.symantec.com/docs/HOWTO74426