Glossary - To make sense of the alphabet soup
Below is a glossary of acronyms and terms used in this forum AD Active Directory ADAMM Advanced Device And Media Management ADRA Active Directory Recovery Agent AES Advanced Encryption Standard AFE Automatic File Exclusion AMHV Agent for Microsoft Hyper-V AOF Advanced Opened File BE 2012 and above AOFO Advanced Opened File Option Up to BE 2010 AP Append Period AVVI Agent for VMWare Virtual Infrastructure B2D Backup-to-Disk B2D2T Backup-to-Disk and then to tape B2V Backup-to-Virtual BE 2012 and above BE Backup Exec BEMCMD Backup Exec Commandline Applet Up to BE 2010 BEMCLI Backup Exec Management Command Line Interface BE 2012 and above BESA Backup Exec Service Account BESR Backup Exec System Recovery CAS Client Access Server (used in relation with Exchange) CAS Central Admin Server CASO Central Admin Server Option CCR Cluster Continuous Replication(for Exchange) CDO Collaboration Data Ojects CIFS Common Internet File System CPS Continuous Protection Server Up to BE 2010 CSV Cluster Shared Volume DAG Database Availability Group DAOS Domino Attachment and Object Storage DC Domain Controller DDI Device Driver Installer dedup deduplication DFS Distributed File System DLO Desktop & Laptop Option DLM Data Life-cycle Management BE 2012 and above DR Disaster Recovery DSF DeDuplication Storage Folder ELS Enterprise Licensing System BE 2012 and above EMT Exchange Management Tool EV Enterprise Vault FC Fibre Channel GA General Availability GAL Global Address List GRT Granular Recovery Technology HCL Hardware Compatibility List IDR Intelligent Disaster Recovery Up to BE 2010 IPL In-Product Licensing BE 2012 and above LCR Local Continuous Replication (for Exchange) LEO Library Expansion Option LU LiveUpdate LUN logical unit number MAPI Messaging API MBES Managed Backup Exec Server BE 2012 and above media server machine where BE is loaded MITM man-in-the-middle (attack) MMS Managed Media Server Up to BE 2010 MOSS Microsoft Office SharePoint Server NAS Network-attached Storage NBU NetBackup NDMP Network Data Management Protocol NFR Not For Resale NSF or .nsf Lotus Domino mail database file OP original post - first post in the discussion OPL Overwrite Protection Level OPP Overwrite Protection Period OST Open Storage Technology P2V Physical-to-Virtual RALUS Remote Agent for Linux and Unix System RAMS Remote Agent for Macintosh Systems RAWS Remote Agent for Windows System RDM Raw Disk Mapping remote server machine that is backed up by BE RHEL Red Hat Enterprise Linux RMALS Remote Media Agent for Linux Servers RPO Recovery Point Objective RSG Recovery Storage Group RTO Recovery Time Objective SAN Storage Area Network SBE Small Businness Edition SBS Small Businness Server SCL Software Compatibility List SDR Simplified Disaster Recovery BE 2012 and above SEP Symantec Endpoint Protectioni SLF Symantec License File BE 2012 and above SP service pack SSO Shared Storage Option SSP Simplified System Protection BE 2012 and above SSR Symantec System Recovery UNC Universal Naming Convention VCB VMware Consolidated Backup VM Virtual Machine VTL Virtual Tape Library VSP VERITAS Volume Snapshot Provider VSS Volume Snapshot Service or Volume Shadow Copy Service WORM Write Once, Read Many WSS Windows SharePoint Services
Backup Exec 2012 - where to find manuals, videos and trainings.
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 Training: Backup Exec 2012 Administration course (5-day instructor led or virtual) Backup Exec Tech Center (a library of self-paced video learning modules) Backup Exec 2012 Videos on Symantec TV: Backup Exec 2012: Overview Introducing the new Backup Exec 2012 User Interface Backup Exec 2012: Job monitoring Backup Exec 2012 Documentation: Backup Exec 2012 Administrator’s Guide (DOC5211) Backup Exec 2012 Readme (DOC5215) Backup Exec 2012 Performance and Tuning Guide (DOC5481) Backup Exec 2012 - Getting started: Backup Exec 2012 Licensing - New licensing system (TECH178483) Backup Exec 2012 Upgrade Guide - Tips & tricks (TECH180232) Backup Exec 2012 vs. Backup Exec 12.5/2010 - a list of differences (DOC5216) Backup Exec 2012 - Best practices: Best Practices for Backup Exec 2012 Agent for Microsoft Exchange Server (HOWTO74428) List of 25+ Backup Exec 2012 best practices (HOWTO74626) 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)How to - Backing up Hyper-V and VMware environments
Are you are looking to find information on the most common tasks related to backing up Hyper-V and VMware environments using Symantec Backup Exec 2012? Here are the two consolidated articles - Hyper-V and VMware that lists out: - Top Knowledge Base articles - Top Videos - Top Getting Started Articles - Top Troubleshooting Articles - Symantec Backup Exec 2012 Administrator's Guide Check them out!
How-To: Downgrade Backup Exec 2012 to 2010 R3
Two months ago I decided to upgrade our backup environment to Backup Exec 2012. I have upgraded Backup Exec in the past and always had relatively few issues during the upgrade process. I had tried to find some detailed information about Backup Exec 2012 but all I could find was some vague descriptions of what was new. I figured I would give it a shot(totally going against my own if it aint broke don't fix it policy). After the relatively smooth upgrade process my jaw dropped at the interface. I thought it was terrible. But I thought I would give it a chance. I eventually got used to the interface although after two months I still preferred the old interface. My problem was the bugs. Maybe it was because I upgraded rather than installed fresh. But over the course of two months I ran into numerous bugs. The application would randomly quit with exception errors. Sometimes during the middle of my jobs it would just stop backing up and I could not perform any jobs (inventory, erase, etc) without restarting the services. It was terrible. I was having to babysit the thing constantly and still not having reliable backups. After working with Support and them telling my to just "repair" the installation and having the same problems, I decided to take matters into my own hands and downgrade. Luckily before I upgraded I made a copy of my Catalog and Data folders that are located in the Backup Exec program files folder. I would like to preface by saying the intro to this article is not meant to start a discussion about the fallacies of BE 2012 - there are plenty of forums for that - just giving a little background on why I chose to downgrade. The following are the steps I used to downgrade my installation. 1. Locate your backed up Data and Catalogs folders.Hopefully, you backed up your Data and Catalogs folder before you upgraded. If you didn't then this article doesn't apply to you. 2. Uninstall BE 2012 choosing to remove everything when asked. 3. After uninstall is complete reboot the server. 4. Install BE 2010 and select the options you need during the wizard, choose to use a new SQL Express instance. 5. After installation run Live Update and update to R3. 6. Reboot the server. It doesn't prompt you to reboot but if you try opening the application it tells you that you need to so go ahead. 7. Stop all the BE services. 8. Navigate to C:\Program Files\Symantec\BackupExec\ and rename the Data folder to Data.new and the Catalogs folder to Catalogs.new 9. Copy your backed up Data and Catalogs folder to the directory in Step 8. VERY IMPORTANT STEP - WILL NOT WORK IF NOT PERFORMED 10. Run thebeutility.exefound in the location from Step 8. Ignore the warning message that pops up when you open it. 11. Select All Media Servers in the left pane. 12. Select your media server in the right-pane and right-click. 13. Select Copy Database. 14. Navigate to the .mdf database file that is located in your Data folder that you copied over in Step 9. 15. Do the same thing for the .ldf log file located in the same location. 16. Press OK. It will run through stopping services re-attaching the database and starting the services again/ NOTE: The first time I did this I didnt do steps 10-16 and the BE services would not start correctly. Thanks to owner ofthis blogI was able to follow their steps and get it going. Big shoutout. 17. You now have an almost fully-restored BE 2010 installation again. It will be running in trial mode. You will still need to contact Symantec Licensing (1-800-721-3934) to get your license keys donwgraded to BE 2010. But at least you can run backups now for 60-days. Now the time-consuming part...This will vary depending on how many servers you are backing up. After I restored my BE 2010 installation I edited my policies and checked my selection list. The first thing I noticed was I was not able to select anything other than user shares on each server. I then proceeded to check my resource credentials. They all failed stating the agent was not installed or the credentials were invalid. I was sure the service account I was using was valid but just to make sure I went ahead and logged into another machine succesfully using it. After I confirmed it wasnt the service account, I knew it was most likely the newer agents I had installed for using BE 2012. I tried to install the BE 2010 agents through the BE 2010 interface. It said they installed correctly but I was still getting the same error. Here is what I did to get the agents going again. 1. Log into each server you are backing up. (I used RDP, but console would work also) 2. Navigate to the backup exec program files unc path located on your media server. ex: \\servername\c$\program files\symantec\backupexec\agents 3. You will see RAW32 and RAW64. These obviously are the Windows installation agents for 32-bit version and 64-bit. 4. Select the appropiate folder for your server architecture and run setup.exe 5. Select the Uninstall option (repair doesnt work - I tried). 6. After the uninstall is complete, run setup.exe and this time install. NOTE: You could also just run the uninstall on all your servers and then re-install the agents using the BE 2010 interface. Actually this would have been my preferred method but I didn't think about it until after I installed all the agents. 7. Most of my servers did not require a reboot but if you get an error about a missing file after the install - uninstall again, but this time reboot after the uninstall and re-install after the server reboots. 8. Go back to your media server and test your resource credentials and selection lists. They should all pass and you should be able to see and select all the drives, SQL database, and Exchange IS'. You are done! I would say for a ~20 server environment this process might take around two hours to complete. It took me much, much longer but I was figuring things out as I went. Like I said the most time consuming part was the agent installs and this will greatly affect how long it takes in your environment. I hope this helps someone out. Again, I'm sure BE2012 is right for someone but for us, we'll stick with 2010 as long as we can. We already bought Avamar and will be moving to that in the next 30 days but we still have to keep BE for at least 7 yearsBackup Exec 15 - where to find manuals, guides and compatibility information
Are you looking to find information related to Backup Exec 15? If so, here is a list for your reference. Bookmark now! Backup Exec 15 Documentation Backup Exec 15 - Administrator’s Guide Backup Exec 15 - Readme Backup Exec 15 - Performance and Tuning Guide Backup Exec 15 - Licensing Guide Backup Exec 15 - Command Line Interface (BEMCLI) Help Download Backup Exec 15 - Compatibility Backup Exec 15 - Software Compatibility List Backup Exec 15 - Hardware Compatibility List Backup Exec 15 - Getting Started What's Different in Backup Exec 15 Benefits of upgrading to Backup Exec 15 Backup Exec 15 Trialware Download About upgrading from previous version of Backup Exec to Backup Exec 15 How to migrate (move) and upgrade Backup Exec from 32-bit computer to 64-bit computer that has a different Windows OS Backup Exec 15: Step-by-Step guide to download and install the program
Question : Regards backup exec 10d
Issue is Server was carashed re-built a new server with same hardware and trying to restore the backup from old server to a new server Getting error : Invalid physical volume library media identifier. Customer want to know if this is related to hardware issue or software issue ? I found a KB link : "Invalid Physical Volume Library Media Identifier" (a0008105 HEX or e00008105 HEX) is reported when a restore job fails. Please let me know If the above KB link will be helpfull ?
Backup Exec 2012 Small Business Edition (SBE) tial software and documentation...
I am trying to get hold of a trial version of "Backup Exec 2012 Small Business Edition". However, when I follow the "Trial Software" link on the product page, log in and download the .ISO files. IT appears to be the full product and not the SBE. Now, I know there are very specific limitations on what agents are covered by the SBE licensing and that there are very specific installation scenarios that the SBE licensing and product will only support. I also recall, during the beta testing of the SBE product, that there was a SBE specific "simplified" interface. So, I'm kind of lost as to how I can get a trial of the SBE version of BE, when I only have the full product, which has none of these limitations/restrictions/benefits!? I also have another issue in that the Backup Exec Administrators Guide still has no information specific to these significant SBE product limitations or supported installation scenarios. For those of you in Symantec involved in the release of this product... I gave feedback on this issue, during the beta testing, and was told that it would be looked into. But it is apparent that this has not been done or deemed important enough. However, I am glad to see that you guys are at least giving some kind of version reference in your admin guide now. So, I have two questions: 1. Why can we not get a trial version of the real SBE product, with all it's relevant limitations and restrictions in place? 2. Why does the BE admin documentation not at least have a SBE appendix that covers the supported installation scenarios and agent licensing limitations This would at least reduce the need for the above specific SBE trial version of the software; as we would be able to install the full product as if it were the SBE product, following the limitations outlined in the documentation. Looking forward to your responses.Server Agent out of date
I started seeing LiveUpdate Information About the agent for windows on at least one server does not have the most recent updates? To Install the most recent updates, on the Backup and restore tab, right click the remote computer that is out of date, and then select Update. 1.There is no indication on what server agent is out of date 2.After right clicking on each server on some I can see Update is grayed out and on some its clickable 3.Does this mean they are out of date and need to be updated? 4.What happen if I update the server will I have to reboot? 5.The server is Windows 2003 with exchange 2003 running on a cluster serves with 2 nodes 6.It seem each node might need the upgrade and the cluster seems to need 7.I am assuming after I update the active node the cluster will be up-to-date 8.Should I manually run LiveUpdate on the backup Exec server monthly and after an update I should update the clients?
