New support for Windows 2008 R2
I’m at to TechED in Berlin … great party for the fall of the Berlin Wall 2009 (shameful timing) – once again Microsoft mess up my weekend. Windows Server 2008 R2 is pretty bold and it will have a significant impact on the market. Piles of guys I have spoken to are interested in the new capabilities.
There are some significant features in the R2 operating system that can help to boost productivity and help administrators gain more management control. It will be of specific interest to companies that have an extensive investment, or plans a complex deployment, of Hyper-V-based virtualisation; any company that has vast swaths of Windows servers in data centres where space, power or both are becoming tight; as well as any company that is planning to deploy Windows 7 on a wide scale in the near future.
In terms of support for R2 BE is already there with Backup Exec 12.5 for Windows Servers revision 2213 Hotfix 331998. This hot-fix contains recommended fixes for Backup Exec for Windows Servers version 12.5 revision 2213. New support for Windows 2008 R2 (RAWS – Remote Agent Support Only) and a Agent for VMware Virtual Infrastructure fix (AVVI).
Affected versions
- Backup Exec 12.5 revision 2213 32bit Media Servers
- Backup Exec 12.5 revision 2213 x64bit Media Servers
Prerequisites
Before installing this hotfix, Backup Exec for Windows 12.5 Service Pack 2 must be installed. Service Pack 2 can be obtained here: http://library.veritas.com/docs/334937. Administrative privileges are required to install this hotfix.
Post requisites
A full backup is recommended after installing this hotfix. Backup Exec Remote Agents must be updated
Download links
- Backup Exec 12.5 or Windows Servers revision 2213 Hotfix 327135 – 32 bit download: http://support.veritas.com/docs/334937
- Backup Exec 12.5 for Windows Servers revision 2213 Hotfix 327135 – 64 bit download: http://support.veritas.com/docs/334938
Issue(s) resolved
After applying Backup Exec 12.5 Hotfix 328462, an Agent for VMWare Virtual Infrastructure (AVVI) backup job with the “Granular Recovery Technology” (GRT) option enabled, completes with the exception “Failed to mount one or more virtual disk images” (For more details please refer to this document: http://support.veritas.com/docs/331927)
Installation Guide – The installation guide here contains general information for installing Backup Exec product updates as well as special instructions for configurations including CPS, Remote Agents for Windows Servers, Remote Agent for Linux/Unix/Macintosh Server (RALUS/RAMS), Clustered Backup Exec, Shared Storage (SSO) installations, Central Admin Servers (CASO) installations, and SAP/R3 Oracle Agents. http://support.veritas.com/docs/300795
Enterprise Vault and Backup Exec
Backup Exec 12.5 released an Agent for Enterprise Vault, which is designed to offer complete protection for Enterprise Vault 7.5 implementations. When Enterprise Vault 8.0 was released, architectural changes in EV 8.0 made the Backup Exec 12.5 Agent for Enterprise Vault unable to automatically protect all aspects of Enterprise Vault. An integrated solution will be in the next version of BE. In the meantime …
For customers who have not purchased the Agent for Enterprise Vault, and wish to protect Enterprise Vault manually with a combination of Backup Exec Agent for SQL Server and Agent for Windows Systems, refer to the following Tech Note: http://seer.entsupport.symantec.com/docs/312327.htm
The Backup Exec 12.5 Agent for Enterprise Vault contains all of the building blocks necessary to protect Enterprise Vault 8.0. Customers who have purchased the Agent for Enterprise Vault do not need to purchase any additional Agents/Options to fully protect Enterprise Vault with Backup
The following procedure will create several jobs which will result in complete protection for the Enterprise Vault 8.0 infrastructure.
Step 1
When the Agent for Enterprise Vault is installed on each member server in the Enterprise Vault infrastructure, the Enterprise Vault entities shown in the Backup Browse view will form the core of the first job. From the Backup View, expand the “Enterprise Vault” icon, and select the Sites,
Vault Stores, Vault Store Databases, Partitions, Index Locations, Directory Databases, and Monitoring Databases to be backed up in this first job.
This will create a single job that protects these specific entities. This job will keep the EV Services in read-only mode for database consistency purposes.
Step 2
Create a series of SQL jobs to protect the additional databases introduced in EV 8.0. These databases are the Auditing Database (AuditDB), the FSA Reporting Database (FSAReportingDB), Fingerprint Database (FingerPrintDB), Compliance Accelerator, and Discovery Accelerator databases.
Administrators will need to browse to the appropriate physical server where these databases run in order to select them for protection. The Agent for Enterprise Vault must be licensed and the Remote Agent for Windows Systems must to be installed on any system that hosts an Enterprise Vault database.
These databases do not require Enterprise Vault to be put into ReadOnly or backup mode, and as such can be protected while they are online. The Agent for Enterprise Vault includes all features and functions necessary to consistently protect running Microsoft SQL databases.
1. Create a SQL backup job to protect the Auditing Database (EnterpriseVaultAudit) and the FSA Reporting Database (EnterpriseVaultFSAReporting)
a. Use Full or Incremental (backup transaction log and truncate) backup method.
2. Create a SQL backup job to protect the Fingerprint Database and ExpressVaultStore Databases
a. Use Full, Differential, or incremental (backup transaction log and truncate) backup method.
b. Symantec advises customers to backup the FingerPrint databases after every VaultStore backup. This is to ensure that backup copies of the Fingerprint Database and the physical VaultStore are consistent. In case of a recovery, the closer the FingerPrint Databases and VaultStores are in time will make for a faster recovery process.
3. Create a SQL backup job to backup Compliance Accelerator and Discovery Accelerator databases (i.e. ConfigurationDB, CustomerDB and CustodianDB) if present.
a. Protect Configuration, Customer, Custodian, and other databases using Full, Differential, or Incremental (backup transaction log and truncate) backup methods.
A Few Things …
1. BE SP2 Release
There are a number of fixes around GRT including up to a 90% decrease in the time taken to run an incremental GRT backup. Please see the following technote which provides links to and details around the changes and fixes in SP2
http://seer.entsupport.symantec.com/docs/324918.htm
Release notes are here:
http://seer.entsupport.symantec.com/docs/323735.htm
2. You know I keep banging on about AD … well it’s not just me:
Optimizing Exchange and Active Directory Backup and Recovery – Thursday, 28 May 2009, Written by Pat Hanavan
http://datacenterjournal.com/index.php?option=com_content&task=view&id=2855&Itemid=40
… and Pat seems to express the whole subject rather better than I do …
3. Symantec Backup Exec System Recovery 8.5 Technical Exam and Assessment
Although each product varies in complexity and depth of technical knowledge, all Symantec Technical Specialist accreditation exams (not to be confused with customer certification), are designed for partners and cover core elements measuring technical knowledge against factors such as planning, installation, implementation and high level troubleshooting. Symantec Partners: See Symantec University for Partners and product Training Path to access the exam and recommended courses.
4. Backup Exec 12.5 Video Product Review by David Strom
The video highlights the key features/benefits of the product.
youtube.com – http://www.youtube.com/watch?v=8DhrpeQ9jAM
Date Posted: February 23, 09
Top 10 Technotes searched …
I thought it might be of some interest for you to see what everyone is accessing on the Symantec Support Site.
So, here are the top 10 technotes searches …
|
Technote |
Description |
| How to troubleshoot issues with a Robotic Library or Tape Drive in Backup Exec for Windows Servers. | |
| When attempting to run a backup job “Physical Volume Library Drive not available” Error occurs | |
| “Corrupt data encountered” (a000fe36 HEX or e000fe36 HEX) is reported when a backup job fails. | |
| Symantec Backup Exec ™ 10.1 (10d) for Windows Servers revision 5629 – Service Pack 3 – Includes Critical Security Updates | |
| Symantec Backup Exec ™ 10.1 (10d) for Windows Servers revision 5629 – Service Pack 4 – Includes Critical Security Updates | |
| How to backup Exchange 2007 with Backup Exec for Windows Servers (BEWS) | |
| How to troubleshoot the error “A failure occurred querying the Writer status” (a000fed1 HEX or e000fed1 HEX or 0xfffffed1 HEX) using VSSADMIN | |
| Backup fails with the error “AOFO: Initialization failure on: “\\\Shadow?Copy?Components“. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0x8007000E): Ran out of memory” | |
| Granular Restore Technology (GRT) Backup of an Exchange Information Store fails with error “Cannot log on to MAPI with the specified credentials” | |
| Backup Exec for Windows Servers – Snapshot provider error (0xE000FED1) A failure occurred querying the Writer status when backing up Exchange 2007. | |
| How to perform a local installation of the Backup Exec Remote Agent for Windows Servers or the Advanced Open File Option | |
| Backup of a Microsoft Exchange Information Store fails with error “V-79-57344-33928 – Access Denied. Cannot backup directory mailbox database and its subdirectories” | |
| Backup or restore job fails with Final error: 0xe00084ed – A hardware error has occurred. |
Backup Exec 12.5 Granular Recovery
One of the really cool functions of BE is the Granular Recovery Technology (GRT). By the way, anytime you need more information on any aspect of BE please see the Backup Exec for Windows Servers Administrator’s Guide. In fact, don’t take my word for it, download from here:
http://seer.entsupport.symantec.com/docs/308400.htm
Just a few tips to help you get the best out of BE’s GRT:
- Review the requirements for staging locations in the Administrator’s Guide.
- You must use a staging location for GRT-enabled jobs in the following scenarios:
- You back up to or restore from a volume with file size limitations.
- You restore granular items from tape.
- You run an off-host backup job.
- You are better off creating a separate backup-to-disk folder specifically for all GRT enabled backup jobs – this really simplifies media management. You will need to manage the IMG media that GRT enabled jobs create differently than other backup-to-disk media.
- Don’t allocate a maximum size for backup-to-disk files. If you do then you are in danger of getting failed jobs because of low disk space. This is because the backup-to-disk file often occupies extra space since GRT information is stored in IMG media and Backup Exec will only create a backup-to-disk file that is as large as the size that you specified.
- If you are using frequent incremental GRT enabled jobs it is a really good idea to run a full GRT enabled backup job every so often. This is because each incremental GRT enabled job requires a small amount of internal storage. If this storage amount increases too much, it can affect system resources. When you run the full GRT enabled backup job, you make available the storage space that has accumulated from incremental jobs.
12.5 delivers GRT for Exchange, Active Directory, SharePoint Server, and SharePoint Services which gives you the ability to recover granular data quickly and efficiently from a single-pass backup. It means, for example, that you do not have to run Exchange mailbox backups to recover granular data, including documents, list items and user attributes, or properties.
BE Installation Upgrades
If you are not on Backup Exec 12.5 you really should think about upgrading, if not for the new comprehensive recovery of virtual and physical systems, or enhanced granular data recovery, or the fact that Backup Exec is now integrated with the Symantec ThreatConTM system to automatically manage continuous data protection functionality in an increased threat cycle, but for the fact that the new version of Backup Exec enhances the management capabilities around managing disk and tape based backup – across the board.
The great thing about upgrading is its simplicity. Now you can run the Backup Exec Environment Check on the computer on which you want to install Backup Exec, before you actually install Backup Exec for real. This makes sure that the installation process can complete. If there are any configuration issues the environment check kicks out warnings that tell you if there are configuration issues that can be fixed or that will prevent the BE installation.
I would also suggest that you install the storage device controller, drives, robotic libraries on the media server (following the documentation included with your storage device hardware for installation instructions, of course) and check that your Windows security settings to make sure they work properly with the Backup Exec service account.
If the drive on which you want to install Backup Exec is encrypted or compressed, and you would like to use a default SQL Express database, verify that an unencrypted and uncompressed drive is available for SQL Express installation.
Check the computer name of the computer on which you want to install Backup Exec. It should only use standard ANSI characters. You may receive errors if you install Backup Exec on a computer with a name that uses non-standard characters.
Oh, and exit everything before you start.
So, for upgrades from 11d or more recent then no separate migration or upgrade utility is necessary. Most settings and all catalogs and data directories from previous versions of Backup Exec are kept. At the end of the installation, the upgrade process is summarised. Before you upgrade delete job histories and catalogs that you no longer need to shorten the upgrade window and then run a database maintenance job.
Like most application installs Backup Exec has a default location for both the program files as well as all the existing catalogs and data. You do not have to keep previous catalogs and data and there is an option during the install process that allows you to continue with the upgrade without backing up existing data. Just a word of warning, you cannot change the database location during the upgrade process. If you want to change the database location after the upgrade, use BEUtility.
Following the install make sure that your storage devices are connected and configured properly and decide if your backup will be to a tape device or a disk device. You can configure both devices when you prepare your Backup Exec environment. If you’re backing up to a tape device, make sure the device is supported. You can install drivers for the devices when you configure your Backup Exec environment. If you’re backing up to disk using the Backup-to-Disk feature, decide where you can create a backup folder. You should create it on a disk that won’t be included in the backup jobs and that has enough free space to contain the backup job.
-
Polls
Loading ...