Backup Exec 2012 Upgrade Guide.
|Article:TECH180232|||||Created: 2012-01-30|||||Updated: 2013-11-19|||||Article URL http://www.symantec.com/docs/TECH180232|
Purpose of this guide: To aid in the understanding of various topics pertinent to upgrading an installation of a previous version of Backup Exec to the 2012 version of the product.
The new 2012 version of Backup Exec has a completely new interface and new paradigms for data resource protection and data storage management. It is very important when migrating to the new version to understand the full implications of the changes and how they will affect the upgrade experience. This is particularly true in an environment with a large number of protected resources and/or storage devices. A Backup Exec Server installation with a complex policy/job/selection list schema could also result in an upgrade that may, at first, seem hard to understand in terms of resultant job definitions.
Key areas of the product changed significantly:
- New UI look and feel: Simplified UI design is easier to use with less actions required for most operations.
- Reduced Number of Tabs: New views for Home, Backup and Restore, Storage and Reports.
- New licensing model: The use of SLF files reduces licensing administration and clutter compared to the previous license key model.
- New Backup and Restore Workflow: New consolidated Job Definitions make protecting resources easier than ever. Reduces the time and complexity of data protection.
- New storage paradigm: Backup to Disk Folders are replaced by Disk Storage locations. Advanced Device and Media Management concepts such as Media Sets, Overwrite Protection and Append periods are still available for tape based media but have been replaced for disk based media. The simplified Data Lifecycle Management (DLM) functionality now manages tracking the retention (overwrite protection) period for disk based media.
NOTE: B2D media upgraded from a previous version will honor data retention settings for the media sets they are migrated from. Disk storage location (previously B2D) data that has an expired retention could subsequently be “groomed” and deleted from the system. Please review data retention (overwrite protection) settings for individual protected resources after an upgrade to make sure they are compliant with your data retention business requirements.
- New Simplified System Protection and Simplified Disaster Recovery: New system protection features make disaster preparedness intuitive and easy to configure. Standardized Windows PE based recovery system makes system recovery quicker and easier than in previous versions.
So, the two most important steps to being prepared for an upgrade scenario to this new version are to: first, become familiar with the new version concepts and procedures, and second, review your current environment and make any changes or adjustments to ensure the upgrade process goes as smoothly as possible. Following these steps will make the transition to the new paradigms presented in Backup Exec 2012 a relatively simple and painless experience.
It is highly recommended that for upgrading a complex environment that a significant amount of testing in a lab environment is performed prior to upgrading production systems. Also, the Backup Exec Support Tool has the added functionality for to perform a dry run through the migration, and review the resultant changes, prior to actually running the upgrade installation. This step is highly recommended. particularly for upgrading a complex environment.
Breakdown of changes to the new version by specific product areas:
- Additional links to videos and other informational documents have been added to assist in understanding the new product version.
- Change in licensing scheme from the previous license keys that were alpha-numeric and entered manually by the user, to a new method of license key files (files with the SLF extension). This should greatly automate and simplify the tracking and maintenance of licensing for a given Backup Exec installation. The License Files (SLF) will be sent to the customer via e-mail, downloaded from the License Portal or obtained through the In Product Licensing in the BE UI. License free trial installation for 60 days is exactly the same as previous versions.
- Changes and simplifications to agent and options choices – several items have reached end of life (EOL) status and several items have been combined. A few notable examples are the CASO (Central Administration Server Option) option which now includes the functionality of SSO (SharedStorage Option, previously a separate option) and is included as part of the ESO (Enterprise Server Option) license, as well as the combining of the virtualization agents into the single Agent for VMWare and Hyper-V, and the combining of all major Database agents (Exchange, MS SQL, MS SPS, Lotus Domino and Oracle) into a single Application Agent. The overall result is a simplified installation experience.
- The following agents and options have reached end of life status (EOL): Agent for Netware, Agent for DB2, Agent for SAP, Agent for Unix. There have been additional items EOL’d, please review product documentation for additional details.
- The new “Enterprise Server Option” license now contains all the functionality for CASO, SSO, and ADBO (Advanced Disk Based Backup Option).Not available for trial installation.
- New capacity edition licensing available.
- Installed licenses viewable from the ‘Application button\Installation and Licensing\License Information’ menu item.
- Due to the new “resource-centric” data protection paradigm introduced in Backup Exec 2012 policies, job templates, selection lists and jobs may be altered significantly as part of the upgrade process. Selection lists protecting multiple resources will broken out into individual backup jobs for each resource.
- As part of the upgrade process Backup Exec creates a migration report that details for the user the following.
- Jobs that will be split into multiple jobs
- Jobs that will be combined
- Jobs that will be added
- Job schedules that will be changed
- Jobs that you must configure manually
- Tips for minimizing the effect of changes
- Users should review the migration report during the upgrade process. If desired, the upgrade can be halted at this point and rolled back to retain the previous version installation.
- During the upgrade process jobs are split out by resource/resource type (Server/data).
- Policies that contain specific steps are converted to job definitions which are then displayed graphically.
- All jobs become part of a new job definition (analogous to Policies in previous versions).
- Jobs are not migrated that are protecting unsupported (EOL) data types (DB2, SAP, etc.)
- Jobs will be split up or combined as necessary to accommodate the new resource-centric model for job creation. Some job types have changed or are no longer available.
- New paradigm allows for One Job/Selection List and Schedule PER SERVER and job type.
- Archive jobs are treated uniquely as they are now a part of the new job definition stages.
- Storage devices may also be altered as part of the upgrade process.
- B2D folders are converted to disk storage locations or legacy B2D folders. Only one randomly selected B2D folder per Volume will be converted to a Disk Storage Location. Any additional B2D folders on the same volume will be converted into a Legacy or Archive Read Only B2D folders.
Storage configuration and utilization
- Tape based storage devices - The concepts of media sets to configure data overwrite protection and append periods still exists for tape based media. These concepts function identically to previous versions.
- Hard disk based storage devices - There are two major changes in regards to disk based devices. One, the concept of “Backup to Disk Folders” has changed to one of “Disk Storage”. The change removes the necessity for users to create and manage specific storage containers (folders). Now, Backup Exec will manage disk use for the user on any specified disk devices. Two, rather than the “Media Set” concept, now, disk location backup data is managed by “Data Lifecycle Management” (DLM). This is a much simplified method of data retention management where the only user input needed is to specify the time period the data is to be retained for. The concepts of “Media Sets” and “Append Periods”, while still appropriate for tape, are no longer applied to hard disk based storage media.
- When the migration process runs, One B2D folder per Volume is converted to a Disk Storage Location, all other B2D folders on the same Volume are converted into Legacy or Archive Read Only B2D folders.
Backup Job creation
- Backup Job Policies - While there is no longer a “Policy” container for Job Definitions per se, the Job Definition essentially serves the same function, but is created in a more automated fashion.
- Selection Lists + Job (properties) Template was combined in previous versions to create backup jobs. Now, in BE 2012, the user starts with the Resource (Server and related data types, i.e. file systems, applications and associated databases). The Resources, as referenced in BE 2012 are roughly analogous to the Selection List as created in previous versions. Job properties are applied as part of the Job Definition.
- Hierarchical rules and data protection workflow formerly accomplished in Backup Policies is now accomplished through the creation of specific “stages” in the Job Definition.
Global settings and administration options
- The ‘Tools’ menu has been replaced by the “Application Button”. This is the large yellow and black button with the disk/tape storage graphic in the top left corner of the user interface. Clicking on the Application Button reveals a number of menu choices similar to those found under the Tools menu in previous versions.
- Configuration and Settings>Backup Exec Settings shows the bulk of global settings previously reached from the Tools>Options menu choice. Configuration and Settings>Job Defaults and the appropriate sub-category reveals additional global settings specific to job types.
- The Installation and Licensing menu item reveals links to view and manipulate all the settings and operations relevant to installation, licensing and upgrade functions.
Article URL http://www.symantec.com/docs/TECH180232