How an existing Backup Exec configuration is migrated to Backup Exec 2012

When upgrading, Backup Exec automatically converts the existing configuration to the current version. The following items provide information about how the configuration is migrated to Backup Exec 2012. Review this information before using Backup Exec 2012. 

·         If multiple backup-to-disk folders are on the same volume, Backup Exec 2012 converts one backup-to-disk folder on the volume to a disk storage device.  Disk storage is a location on a locally attached internal hard drive, a USB device, a FireWire device, or a network-attached storage device to which you can back up data.  All of the other backup-to-disk folders on the volume become read-only so that the data can be restored from them.   The read-only backup-to-disk folders are called legacy backup-to-disk folders.  Backup Exec no longer creates new backup sets in the legacy backup-to-disk folders.  All backup jobs that were sent to the legacy backup-to-disk folders are now sent to the disk storage device that Backup Exec 2012 creates on the volume. Backup Exec’s data lifecycle management feature manages the existing data in the legacy backup-to-disk folders, eventually expiring and deleting the data according to the overwrite protection period that you specified when you created the backup.  When a legacy backup-to-disk folder becomes empty, Backup Exec deletes it.  The data lifecycle management feature also manages the backup data on the disk storage device.

o    Note: If upgrading from a release prior to Backup Exec 2010 R2, all backup-to-disk folders that have the same drive letter are considered as being on the same volume.

·         Removable backup-to-disk (RB2D) folders are now called disk cartridge devices. Disk cartridge devices are a type of storage that usually remains attached to the Backup Exec server while you remove the media, such as RDX.  If you are not sure if the storage has removable media, you can open the Computer folder on your Windows computer. The devices that contain removable media are listed. You can manage data retention on disk cartridge devices by associating the media with media sets.  Media sets specify append periods, overwrite protection periods, and vaulting periods.

·         Existing storage device pools that contain exclusively disk storage, or disk cartridge devices, or tape cartridge devices remain intact. Storage device pools that contain a mix of storage device types are labeled as disk storage device pools, and all cartridge devices are removed.  New storage device pools are created to contain the cartridge devices.

By default, Backup Exec automatically creates the following storage device pools:

·         Any disk storage – contains any backup-to-disk folders that Backup Exec converts to disk storage devices.

·         Any tape cartridge storage – contains any tape devices that Backup Exec detects as attached to the Backup Exec server.

·         Any disk cartridge storage – contains any disk cartridge devices that were previously used as removable backup-to-disk folders, or that have been configured to be used as a backup destination.

·         Any virtual disk storage – contains the virtual disks that are on storage arrays. This pool is created only if the Storage Provisioning Option is installed.

o    Note: In a Central Admin Server Option environment, the storage device pools that Backup Exec 2012 creates contain all of the storage devices that are on all Backup Exec servers in the environment.

Best practices for Backup Exec 2012 installation

Best practices for Backup Exec 2012 installation


Best practices include tips and recommendations to help you install or upgrade Symantec Backup Exec 2012 more effectively. For more information about installing Backup Exec, see theBackup Exec 2012 Administrator's Guide.


The following best practices are for preparing to install or upgrade Backup Exec:
• Review the "Features or requirements no longer supported by Backup Exec" 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 secondary 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.
• 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.
• Consult any of the following resources on the Help and Documentation menu if you have questions or difficulties:
o Use the Administrator's Guide for comprehensive information about Backup Exec.
o Use the Backup Exec Help for searchable, topic-based documentation.