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

Article:TECH178524  |  Created: 2012-01-09  |  Updated: 2012-01-24  |  Article URL http://www.symantec.com/docs/TECH178524
Article Type
Technical Solution


Subject

Issue



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.  For details about all of the new features of Backup Exec 2012, see the Backup Exec 2012 Administrator’s Guide.

 


Error



UMI V-225-288
 


Solution



  • 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.
    • 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.
    • 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.

 


Supplemental Materials

SourceUMI
ValueV-225-288
Description

Backup Exec Data Migration Report

 



Article URL http://www.symantec.com/docs/TECH178524


Terms of use for this information are found in Legal Notices