About Microsoft SQL Server 2005 Express Edition components installed with Backup Exec
The Backup Exec installation program installs Microsoft SQL Server 2005 Express Edition components that are required to run Backup Exec.
Backup Exec prompts you to do one of the following:
-
Install the required Microsoft SQL Express components with Backup Exec and create a default Backup Exec instance.
-
Select a Microsoft SQL Server 2005 (SP3) or SQL Server 2008 instance that already exists on the network on which you want to run Backup Exec.
During the installation process and upgrade process, Backup Exec stops and starts the SQL service several times. Other user-created databases that use the SQL Server instance are unavailable during the process. To avoid such conflicts, you should install Backup Exec into its own SQL instance.
If you choose to install Backup Exec into an existing SQL 2005 instance, make sure that SQL 2005 Service Pack 3 or later is installed before you continue with the installation.
|
Caution:
|
Backup Exec may not function properly if you install it into an existing SQL instance that uses case-sensitive collation. Symantec recommends that you avoid installing Backup Exec to a SQL instance that uses case-sensitive collation.
|
When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up.
You cannot install multiple Backup Exec databases on the same SQL Server instance.
|
Note:
|
If you are installing a managed media server, it is recommended that you select a local Microsoft SQL Server 2005 (SP3) instance or later on which to install the Backup Exec database for this managed media server. Do not select the same SQL Server instance that is used by the central administration server.
|
About Microsoft SQL Server 2005 Express Edition components installed with Backup Exec