Are you looking to find information related to Backup Exec 2012? If so, here is a list for your reference. Bookmark now!
Backup Exec 2012 - Getting started:
Backup Exec 2012 - Best practices:
Backup Exec 2012 - Compatibility:
Backup Exec 2012 - Software Compatibility List (TECH175581)
Backup Exec 2012 - Hardware Compatibility List (TECH175582)
Backup Exec 2012 - Platforms, Agents, Options, and features no longer supported (TECH178552)
Let me add this video related to disaster recovery testing (re-installation of BE2012 server using SDR:
Budget approved to replace Back-up Exec and all things Symantic!
After 12.5 versions and x number of owners, you would think BE could backup data from a local disk to an attached tape drive more then twice in a row without errors. (I know, it was all hardware! Don't have to hear it anymore tech support!!!!)
I am free!
I tried to reply you beautiful and helpful thread. ut i just had to give a vote instead since i did not see the reply icon.
Thank you for the video it was really helpful.
There is a BEMCLI shortcut list http://www.symantec.com/docs/TECH181699. It has 7 docs at the moment, but I am adding to it as I find things people are trying to do.
The best way to get examples is using get-help cmdlet -example
each BEMCLI cmdlet has use examples.
To get a list of available commands run get-becommand. This will list all 223 cmdlets which is a little much to proccess. Luckily get-becommand supports wildcards.
To see all the cmdlets that have backup in them:
Once you find a cmdlet you want to see examples for use get-help:
BEMCLI> get-help New-BEBackupDefinition -Examples
Creates a new backup definition in Backup Exec.
-------------------------- EXAMPLE 1 --------------------------
C:\PS> Get-BEAgentServer -Local | New-BEBackupDefinition -BackupJobDefault BackupToDisk | Save-BEBackupDefinition
These commands create a new backup definition that backs up the entire local computer using the BackupToDisk defaults.
-------------------------- EXAMPLE 2 --------------------------
C:\PS> Get-BEAgentServer -Local | New-BEBackupDefinition -BackupJobDefault BackupToDisk -FileSystemSelection C:\Windows\*,D:\* -SystemStateSelection Include | Save-BEBackupDefinition
These commands create a new backup definition that backs up the C:\Windows directory, the D: drive, and the System State of the local computer.
-------------------------- EXAMPLE 3 --------------------------
C:\PS> Get-BEAgentServer -Local | New-BEBackupDefinition -BackupJobDefault BackupToDisk | Remove-BEBackupTask * | Add-BEDifferentialBackupTask | Save-BEBackupDefinition
These commands create a new backup definition that backs up the local computer with an initial full and a differential backup.
Get-help also has additional switchs that will give you even more info about the selected cmdlet.
to see how to use get-help:
BEMCLI> get-help get-help
Was there some thing in particular you could use an example for?
Here are some links on CLI that are also on Connect - hope this helps!
Thanks Kirk for the great info!
I've came here to get the manual or train on 2012.
The fact I have to do this should tell you that as far as making your product easier to use, you failed.
I've never read a manual in the decade plus I've been using BEW and I've backed up, restored, incrementally, full server recoveries and entire bit.
That means it was easy to use. Nothing beats the tree list check box for simplicity in backup or restoring.
IF I could get corporate not to buy another copy of BEW I would. At least then I'd have gotten some good out of this poor decision to revamp the internface.
You need to slap yourself in the face instead of patting yoruselves on the back on this product. You took a fine, easily used, never need to read the manual interface and ruined it imho.
...before we get to your not having any sort of actual manual that I can download, print off or read on a smartphone. I click on the manual link and it sends me to your knowledge base search engine... really...
Get back to simplicity and fire whoever thought this was a good idea.
...and I'll waste hours of my time overcoming your "improved" product.
Thanks for absolutely failing to make it easier to use.