Information on the Job and Policy migration process when upgrading to Backup Exec 2012.

Article:TECH179063  |  Created: 2012-01-16  |  Updated: 2012-05-08  |  Article URL
Article Type
Technical Solution



Information on the Job and Policy migration process when upgrading to Backup Exec 2012.



Backup Exec 2012 introduces a server-centric, simplified-feature graphical user interface. All backup jobs are now backup definitions. This impacts jobs, policies, and selection lists from earlier Backup Exec versions. Jobs that contain multiple unrelated systems are now split into several jobs. Jobs that earlier protected multiple servers are now split on a per-server basis.

For each server, the upgrade process creates a resource container, which is new in Backup Exec 2012. The upgrade also creates a backup definition name for each policy migrated from the earlier versions. For existing policies, the backup definition name is the policy name plus the resource container name.  The upgrade process also creates a resource container for each distributed application.  
Note: Backup Exec 2012 provides resource ordering at the server and resource container level. However, the upgrade process does not have resource ordering for the resource container and server. Specify and persist the orders after the upgrade process.

Each backup definition contains only one system; all ad-hoc backup jobs(jobs not created through a policy) from earlier Backup Exec versions are now converted to one-time backup jobs or backup definitions. Conflicting backup methods within a single job are not supported; jobs are grouped and split. An example of conflicting backup methods is when the incremental method is used for files, and the full method is used for SQL databases in the same job.
The new server-centric model enables all jobs to be created, monitored, and managed at the server level.  New jobs have same schedule as the old jobs from which they split. However, they do not have job logs and job history information. Some jobs may not be migrated because they contain features that have reached end of life. Backup jobs may be split into multiple jobs or combined. In certain cases, full backups may be added and job schedules may be changed.
Independent ad-hoc full backup jobs are converted into backup definitions with the full backup method. A new backup definition is created that includes stages for full, and incremental or differential backups. The new policy contains a full type and an incremental type. The Full backup job is set to "Run Now" and "On Hold" so the new Full backup jobs won’t start immediately after the upgrade process.

In Backup Exec 2012, archive jobs are not configured as separate jobs. Archive jobs are now a stage in the backup job definition and the archive job selection is a subset of the backup selections. Archive jobs can contain File System and Microsoft Exchange resources for only a single server. The existing archive jobs are upgraded to create new archive jobs, which form part of the upgraded backup definition. Existing archive jobs can contain overlapping selections from multiple servers. These jobs are processed to obtain a list of granular archive resources, which can be a top-level File system folder, an Exchange server, a full Exchange DAG selection, or a specific database in a DAG. For each archive resource, Backup Exec tries to find a match in the upgraded backup job definitions.
After the migration process completes, Backup Exec displays a Data Migration report, which displays how the jobs were migrated. The migration report enables:
       Ensure that the backup data is safe.
       List all the changes that have taken place.
       Use as a reference for what happen during the migration process.
   The report is organized to display critical changes, organizational changes, schedule changes, and minor changes.  Depending on how the previous environment was configured you may have more jobs and scripts.
Considerations during migration for ad-hoc full backup jobs, incremental and differential jobs:
        Ad-hoc full, incremental, and differential jobs that use the same selection lists are grouped into the same backup definition.
       A new policy is created along with a list of new full, incremental, and differential backup templates.
       One new template for each ad-hoc full, incremental, and differential backup job is created.
       All other independent ad-hoc full backup jobs that use the same selection list are grouped into the same backup definition.
       Ad-hoc full backup jobs, incremental and differential jobs that use different selection lists, are not grouped in the same backup definition.
       The old ad-hoc linked duplicate backup jobs are converted to backup definitions. That new backup definition contains both the backup stage and duplicate stage. If the backup job protects multiple servers, a duplicate stage is created for each new split backup job.  Independent duplicate jobs are deleted.
Selection list migration considerations during migration:
       Selection lists created in different ways and which reference different data in Backup Exec are not considered similar and 2 separate selection lists will be created. Only selection lists created with the same style and which protect same resources are considered similar enough to be combined into one definition.
       Selection lists that protect the same resources but have a different sequence or order of the protected resources, are considered the same, and will be combined.
       Selection lists that are created with different login accounts will both be considered during the migrating and combining selection lists process.
       The Selection list of the full jobs will be used when creating the new job family. For a job with a selection list that protects more than one resource, Backup Exec determines whether the job is a full or incremental, based on a prioritized resource type list. For instance, if the selection list of the job protects three resource types, file and folder, Microsoft SQL, and Oracle, then the backup method type of the highest-priority resource is considered as the method type of the job.
The following jobs are not migrated to Backup Exec 2012:
       Ad-hoc, stand-alone duplicate jobs
       Ad-hoc verify jobs
       Catalog job
       Copy job
       Resource discovery job
       Restore job
       Unsupported report jobs
       Delete from Archive
       Restore from Archive
       Test run jobs
       End of life jobs, such as DB2 jobs, SAP jobs, and jobs targeting SPN devices. 
Deprecated agent jobs, such as DB2 and SAP jobs are not migrated. Jobs that contain a DB2 type of resource are migrated; however, the DB2 resources are deleted from the selection list. CPS exchange jobs are migrated as Exchange incremental jobs. CPS File System jobs are migrated as normal backup jobs. Daily and Working Set backup methods is now end of life. During the migration process, backup jobs that are configured with these two methods are updated to use a full backup with modified time. SPN is no longer supported with BE2012. Jobs that target an SPN device are not migrated.


Article URL

Terms of use for this information are found in Legal Notices