Not Applicable

927 Topics

Backup 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
SuperBrain
10 years ago Place Backup Exec
1.8KViews
7likes
0Comments
Monitor Appliance Health & Performance 24x7
Today’s businesses require access to their information on a 24x7 basis, not to mention the ability to protect that data in the event of unplanned interruptions which leads to complexities in their IT infrastructure. For many IT leaders, moving to Symantec appliances for their backup issues to protect data means reducing cost, complexity and operational risks in their IT environment. Symantec understands that a properly planned out data protection strategy enables customers continuous access to their information. To that end, Symantec has gone a step further to simplify, automate and enhance the support experiences for its appliance customers with its latest functionality in appliances, Symantec AutoSupport. Symantec AutoSupport proactively identifies issues, automates support, and enables faster resolution with the aim of lowering customer’s total cost of ownership of their appliance environment. As a result, appliance downtime is minimized, product reliability and serviceability is enhanced, storage capacity planning and management is simplified, and who doesn’t want their issues resolved before the customer is aware of any problems. To find out how Symantec AutoSupport can help, check out this video http://bit.ly/EnableAutoSupport
kirankamreddy
12 years ago Place Backup Exec
552Views
5likes
1Comment
My List of Problems With Backup Exec
I've used Backup Exec for years at numerous employers on numerous platforms, in both virtual and non-virtual environments, backing up everything from app servers to file servers, SQL servers to Exchange server, domain controllers and VM snapshots. I've used Backup Exec v7, v9, 2010, 2012, and 2014 across every major version of Windows Server from 2000 through 2012 R2. Backup Exec is the monster I love to hate. When it works it works, but when it doesn't it's infuriating. On one hand I've seen it perfectly restorecomplex applicationservers to pre-crash states. On the other, I've seen it completely unable to perform the simplest tasks. This article is NOT intended to be a rambling complaint. Instead, I am posting it as an official record of my own experiences with the product. The following issues are not isolated, but rather have been observed across many different platforms and clean installs, and are easily reproduced/encountered. Some are bugs. Others are just bad design. My hope is that the folks over at Veritas will take notice. At the very least, you may find you're not aloneregardingone or moreissues you've encountered yourself. NOTE: Having said the above, it's possible that some issues are unique to my environment (that is, my network, my Active Directory domain, etc...). Many of these problems have been observed across domains, and all of them have been observed across multiple backup servers, but I won't rule out the possibility that some of these are unique to my domain (if that's possible). GENERAL When modifying a backup job containing multiple target systems, even minor changes (such as job name or scheduling changes) often result in ‘Unable to create the Backup Items’, ‘The method Backup Items was called with invalid arguments’ error messages, forcing you to completely delete and recreate the backup job. This is unacceptable, and is half the reason I rarely group backups for different servers (if I can't update the job later then I'm only asking for trouble). Selecting ‘Do not run a delayed catalog operation’ suggests that a catalog operation won't be run. In fact, it merely ensures the catalog operation is run in parallel with the job itself.I understand the need to run the catalog, but thisis a highly misleading option. VSS provider selections are poorly-implemented, especially in regards toExchange backup jobs. When backing up (A) Exchange databases on (B) a virtual server, you must select ‘System – Use Microsoft Software Shadow Copy Provider’. If your server isn’t virtual, or if you’re backing up file system and System State data on a virtual server, you must select ‘Automatic – Allow VSS to select the snapshot provider’. This is an incredibly obscure setting that isn’t well-documented. The software knows the Exchange server is virtual, and it knows what I'm backing up. Why can't it just use that information to select the best VSS provider? The jobs don't offer nearly enough granular control over different resources. For instance, I can't set up one Exchange backup job to back up 5 databases in full, and another 3 as incrementals. It's all or nothing. Added flexibility in the job design would be nice. JOB MONITOR FILTERS Filters are a good idea, but they inevitably disappear without any explanation. This happens on both servers and client-side installations. The filters are poorly designed insofar as their categorization options. For instance,you can build a filter to show you either(A) active or(B) pending backup jobs, but you can't build one filter to show you both. MICROSOFT EXCHANGE You cannot perform granular Exchange restores from an incremental Exchange backup, even with GRT enabled. This seems to be a bug. [NOTE: Per comments added to this thread below, it has been pointed out that incremental GRT backups are not supported when using deduplication, but for B2D backups they should work fine. In my environment, while (A) I can verify that they do work when run against B2D storage devices, the (B) GRT processoperation often fails for one or more database, rendering those emails non-restorable from a GRT standpoint, and thus rendering the GRT function itself useless. After observing this over a long period of time in my environment, my best estimates are that while incremental GRT backups to B2D fail the GRT processing phase for between 40%-50% fo the databases backed up, whereas the failure rate drops to aroung 10% of databases when those same backup jobs are switched from incremental to full.] Incremental Exchange backups often hang backup jobs, specifically in regards to the cataloging operation. There are no safeguards in place to prevent two jobs from backing up the same Exchange database at the same time. While not a bug, this would be a welcome improvement. Exchange backup jobs often report as having completed successfully, but examination of the job logs shows that one or more backup selections were not processed for GRT. Why do the jobs report a successful completion if the GRT aspect failed? The option to use the search function to find objects backed up as part of an Exchange GRT backup(versus manually navigating databases/mailboxes/etc...) is not present after cataloging old media. Not sure if this is a limit tied to data restores from tape versus hard drives, or if it is related to reintroducing old media and cataloging. The Exchange search options are not very useful. You can search for message title, size, and modified time (I assume this is the date/time the message was created), but you cannot search for things like recipients (TO, CC, BCC), sender, or message body. As a result, finding that one email lost amidst tens of thousands can become a very tedious task. Expanding on the current search options would be a welcome addition. SCHEDULING Every incremental/differential job must be directly tied to a corresponding full job. This robs you of tremendous flexibility when it comes to running a full backup once a week, with multiple incremental backups on multiple schedules throughout the week. It also means that if you want to back up a specific piece of data on a server you must back it up fully and incrementally/differentially outside of the usual backup job. No way to link backup jobs outside of some fancy PowerShell commands, and even then, the GUI doesn’t indicate that the jobs are linked. The app does a great job of visualizing different stages of a single job, but it would be great if it included the ability to link completely unrelated jobs and present this visually as well. DUPLICATION LTO duplication jobs behave very erratically. Consider the following scenario: You have a tape library with three tapes (let's call them tapes A, B, and C). Each tape has been partially written-to but still has plenty of free space, and each is still appendable. Your goal is to copy the data off tape C over to either tape A or tape B, in order to consolidate data and use fewer tapes for that particular backup set. You browse the backup sets on tape C, highlight all the entries, then right-click and choose the duplication option. [PROBLEM 1] - Backup Exec doesn't allow you to target a specific LTO tape as the destination. Alright, I'll admitthis is more of an annoyance than a problem, but it still complicates the ordeal and leads directly into...[PROBLEM 2] - Backup Exec will load the source tape, but then it might grab *ANY* tape as the target tape. So you don't know if your backups are going to be written to tape A or tape B. Worse, it *MIGHT* even be written to another tape, possibly one not written to at all, even when you've told the job to append to an existing tape first. This logic results in lots of wasted tape space. DEDUPLICATION There's no way to enable client-side deduplication on a single job containing multiple servers. To use client-side deduplication you must separate every server into its own job. Deduplication databases have a habit of not mounting after reboots, forcing numerous service stops/restarts, each of which can take 30-40 minutes. Or they don’t mount at all. Either way, this introduces huge amounts of downtime during something as simple as a reboot. For those of you thinking the database or the backup server must be bad, I have observed this over several years across multiple backup servers and numerous deduplication databases. Client-side deduplication works intermittently at best. A job may utilize client-side deduplication one day, then fail the next, then run successfully the day after that. Veritas techs have told me to just use server-side deduplication, since client-side deduplication doesn't do much anyway and the errors aren't worth the effort, but if this is the case why does the app offer client-side dedup at all? After importing an old deduplication database, you cannot write to it. All you can do is read from it. Why? Does this mean every time you build a new backup server and migrate a deduplication database you have to start building a new database from scratch? That's a huge waste of space that some admins can't afford. Not only that, but because Backup Exec only allows you to have one deduplication database at a time, the act of importing an old database shoots you in the foot, preventing you from backing up to a new deduplication database while you reference an old database. RESTORES After cataloging old media, the old server name appears in the ‘Backup and Restore’ server list. However, you cannot initiate restores from here - the option is present but it's grayed-out. Instead, you must manually browse to the loaded media, find the backup set in question, and perform a restore from there. It makes no sense to add the server into the server list if you can’t use it, especially since when I'm done restoring I have to go in there and blow away the server anyway. It's a useless feature that adds more work and can lead you to believe you can't restore the server at all. The Exchange GRT search function is only available when you right-click a server from the server list page and perform a restore from there. If you right-click the backup media itself (a must if you've recently cataloged old media), the search function doesn't exist. Backup Exec provides no way of restoring Exchange mailbox data directly to a PST file. The only way to do this is to install the backup agent to a client system (probably a PC) with a copy of Outlook, adding the system into your servers list, then perform a restore from Exchange to that client system. Not only does this mean you need a secondary PC in play to achieve the export, but the requirements that the version of Outlook be 2010 or earlier means that you need a specific PC. In my case, my team of techs have Outlook 2010, 2013, and 2013, depending on which tech you're talking about, and that means my 2010 tech is the only person whose PC supports this function. So every time I restore to PST I have to make sure he's around and plugged in, with no intention of rebooting any time soon or leaving the office. It's stupid to have to involve any client PC in the first place, but to further limit us by restricting versions of Outlook is insane. SERVICES Backup Exec services don’t always start properly. Often you must configure them for a delayed start. This has been observed across multiple backup servers and multiple clean installs of Backup Exec. Oddly, this problem rarely arises immediately upon install, so there may be mitigating factors. STORAGE DEVICES Pending jobs claim available read operations against disk storage. For instance, let's say you have a 1 tape drive and 1 B2D store. The B2D store allows 4 read/write operations at a time. Now let's say you have 5 jobs queued up to copy data from the tape drive to the B2D store. You'd think that since you have just 1 tape drive, you'd only use up 1 of your read/write operations, allowing Backup Exec to run other jobs against the B2D store in the meantime. You'd be wrong. Instead, Backup Exec eats up all 4 of the read/write operations for the B2D store, claiming each for one of the pending tape-to-B2D jobs, even though only 1 can run at a time because you only have 1 tape drive. This bottlenecks all your other jobs. Admittedly this is probably a rare circumstance, but in my environment I have to copy data from tapes to a B2D store, and the read/write limits combined with Backup Exec's poor way to reserving the operations means that all my other jobs just sit there waiting until the tape drive finishes its jobs first. Backup Exec only allows you to create one B2D storage device per drive letter. This is a rediculous limitation. LICENSING When inputting new license keys into the software, the license count doesn’t appear next to the product name. Instead, you must proceed to the next screen of the wizard, then use the Back button to return to the first page. Only then can you verify that the new license keys incorporated the correct counts. This is just sloppy. If the wizard can immediately detect the new license types based on the key, it should be able to detect the count as well. Instead, it makes you think your keys are bad unless you happen to go back in the wizard after you've proceeded to the next step. License counts can easily get screwed up, even when you’re adding the proper keys. Backup servers can 'lose' licenses for no good reason. This is more common during upgrades, but it should never happen at all. BACKUP AGENTS Remote agents will occasionally become unresponsive, resulting in failed backup jobs. When backing up Exchange databases directly to LTO tapes, jobs will report as failed better than 90% of the time, resulting from a disconnect between the Backup Exec server and the remote agent. However, the job itself seems fine and the data is restorable. Backing up Exchange databases to non-LTO mediums don’t result in these errors.
Bob_Gruett
9 years ago Place Backup Exec
4.4KViews
4likes
5Comments
Backup exec License since Backup exec 2012
Hello Team, I am little bit confused about backup exec licensing since backup exec 2012 and latest versions. In previous versions we could see which licenses are available and installed in backup exec. But since backup exec 2012 and in all latest versions all the licenses are not visible. Like I have seen in once of the server Agent for windows is not available its showing 0 0. But when I configured the backup for one of the remote server it tooks the backup of databases as well as local drives. How it happens? Do we need to purchase seperate license for agent for windows in backup exec 2012 onwords or it is included with default licenses.
Solved
Santosh23
9 years ago Place Backup Exec
975Views
4likes
4Comments
VMware based incrementals not working
Hi, I'm having issues with getting Incremental backups of VMware virtual machines working using the AVVI agent. V-79-57344-38324 - Incremental\\Differential backup methods are not supported for this VM. The backup job failed, since the option 'to fall back to a full backup' was not selected. V-79-57344-38366 - Backup Exec 2014. vSphere 5.5 I've confirmed that VM hardware version is appropriate and that CBT is enabled and working. Full backups have completed successfully. What can caused the above message and incrementals to not be possible? Thanks
Dead-Data
9 years ago Place Backup Exec
1.1KViews
4likes
4Comments
Backup Exec 2014 SP2 – Release Notes and Technical Information
Backup Exec 2014 revision 1786 Service Pack 2 has been released. New features/enhancements that are included in this release: Oracle 12c for Windows and Linux Oracle Enterprise Linux (OEL) 7.0 Red Hat Enterprise Linux (RHEL) 7.0 Red Hat Enterprise Linux (RHEL) 6.5 SUSE Linux Enterprise Server (SLES) 12 Open Enterprise Server (OES) 11 SP2 Exchange 2013 CU6 SQL Server 2008 R2 SP3 SQL Server 2008 SP4 Windows 2012 R2 and 8.1 November update NDMP Hitachi FOS 5.x For more information see: Backup Exec 2014 revision 1786 Service Pack 2 Release notes Backup Exec 2014 revision 1786 Service Pack 2
SuperBrain
10 years ago Place Backup Exec
3KViews
4likes
15Comments
Never Been to Vision? Tell Us Why and Receive 200 Connect Rewards Points and a New Hoodie
Never attended a Symantec Vision conference? We want to know why. For the first 20 people (10 in the US and 10 in Europe) who sign up and participate in a 30-minute interview before August 22nd, we’ll award you 200 Connect points AND send you a custom Vision Hoodie. To set-up a time, please click here or email your contact information to vision@symantec.com.
A_L_Johnson
11 years ago Place Backup Exec
185Views
4likes
0Comments
Backup exec error.
Hi Technical, http://www.symantec.com/business/support/index?page=answers&startover=y&question_box=V-79-57344-33928 My file server fails and I restart it some times to reconnect to the backup exec 2012 but it gives me the above troubleshooting link. file server and backup server are windows 2008 r2 Regards, Daniel
Wainaina
11 years ago Place Backup Exec
312Views
4likes
1Comment
New Backup Exec 2010 R3 SP3 and Backup Exec 2012 SP2 are now available!
The much awaited Service Packs for Backup Exec 2010 R3 and Backup Exec 2012 have been released. You can download them by going to the following links: Backup Exec 2010 R3 revision 5204 Service Pack 3 - http://www.symantec.com/docs/TECH203157 Release Notes:http://www.symantec.com/docs/TECH208601 Backup Exec 2012 revision 1798 Service Pack 2 - http://www.symantec.com/docs/TECH203155 Release Notes: http://www.symantec.com/docs/TECH208600
SuperBrain
11 years ago Place Backup Exec
750Views
4likes
4Comments
Backup Exec 2012 update – vSphere 5.5 support and R2 Beta registration!
EXCITING NEWS!!! Please find the new announcement on the BE Blogregarding Backup Exec 2012, vSphere 5.5 support and R2 beta registration from Blake McConnel,vice president of Product Management, Backup and Recovery, Symantec Corp. Follow this thread forthe latest updates:https://www-secure.symantec.com/connect/blogs/backup-exec-2012-update-vsphere-55-support-and-r2-beta-registration Thank you, Amy Johnson
A_L_Johnson
11 years ago Place Backup Exec
251Views
4likes
1Comment