Step by Step guide to download and install BE 2010 R2: http://www.symantec.com/docs/TECH138264

BE 2010/R2/R3 Administrator's Guide: http://www.symantec.com/docs/DOC2211

BE 2010/R2/R3 Software Compatibility: http://www.symantec.com/docs/TECH137682

BE 2010/R2/R3 Hardware Compatibility: http://www.symantec.com/docs/TECH137050

BE 12.5 Software Compatibility: http://www.symantec.com/docs/TECH62301

BE 12.5 Hardware Compatibility: http://www.symantec.com/docs/TECH62114

BE 12 Software Compatibility: http://www.symantec.com/docs/TECH56442

BE 12 Hardware Compatibility: http://www.symantec.com/docs/TECH55640

How to upgrade and migrate BE 11d/12/12.5 standard,CASO and SAN/SSO environments to 201o with a different server name and version of windows: http://www.symantec.com/docs/TECH137015

Direct upgrade path from BE 11d/12.0/12.5/2010 to BE 2010 R2: http://www.symantec.com/docs/...

Posted on behalf of Symantec.Cloud team

You might remember that back in May, we made an announcement focused on a new approach to help small and mid-sized organizations protect data through new delivery models.  Our Backup Exec software has long been an industry leader in data protection.  But we are increasingly hearing that our customers need a choice in how they manage their backup environment.  Enter Symantec Backup Exec.cloud – a new delivery model that lets our customers leverage the industry leading Backup Exec technology in a cloud service model. 

In September, we began offering Backup Exec.cloud (BE.cloud) through a pilot offer with Synnex US and Ingram Micro.  Some of our partners have been able to offer their customers BE.cloud, enabling us to collect valuable feedback and enabling we meet partner and customer needs. ...

Vmware Backup Requirement:

Licence:

Backup Exec - AVVI agent licence

ESX - Vstorage API licence

Permission:

>> Through ESXi directly Requires a root account or an account equal to access the Vm and take snapshot.

>> Through Vcenter as described in the Article Here

Other requirements: (GRT And NON GRT)

>> Fault Tolerance based machine does not allow snapshot, hence avoid backing Up FT based VM's or Turn off FT on the machines

>> Either Vmware snapshot Provider or BE vss provider is a Must for Application level GRT.(recommended BE VSS)

Incremental and differential Job requirement:

>> hardware version: 7 for the virtual machines

>> Policy based full and Incremental/differential Job

>> change block tracking should be enabled (by default it is enabled , otherwise backup exec uses vstorage to enable...

Well if you have got to this page you probably already have backups running to disk (and duplicate to tape) via the VCenter using AVVI and your looking to turbo charge your backups.

Well here are the simple truths.

1. You muck this part up and the windows host initialises the LUN that your datastore is on… there goes all your VMs. You have been warned
2. Getting Backup Exec to use the SAN is straight forward. Obviously your VMhosts and  BE Media Center  must be connected to the SAN via HBAs. The VCenter does not have to be, it is just acting as a “go between”
3. If your backing up directly to tape, the only gain you are going to get is likely to be marginal as the tape drive is likely to be your bottleneck. But putting the backup traffic over the SAN switching fabric will free up bandwidth on your main network.
4. If you are backing up to disk, then prepare for some major reductions in backup...