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
Backup 2015 DLM not running
I have a CASO setup with one VM running the CASO role and three media servers on different locations. The media servers are physical with big D: and E: drives (only local disk, no removable disk or so), disk storage + dedupe storage. Catalogs are stored centrally and all servers run 2012 R2 OS and Backup Exec is fully patched with the latest patches as of today. Our normal backup procedure is to run the backup jobs to disk and then duplicate to dedupe storage, we also do some optimized duplication from one media server to another with duplication from dedupe to dedupe storage. We installed all serversearly Septemberand everything is running fine except that the disk storage backup sets will not be removed by DLM even if they are expired (or manually expired by right clicking and selecting "expire"). I installed another server to test earlier today and noticed that in the audit log (on the new test server) I could see that DLM log an event for every backup set it removes and it works just fine on that setup. This is acompletely independent backup exec instanceand only runs one backup job for test. In the audit log of our "real" backup server there is not a single entry logged by DLM from day one which is really strange. I logged a case yesterday with Veritas/Symantec support and the test we agreed on doing was to first run an inventory of the disk storage and when that didn't help we decided to do an inventory + catalog as well, since we have 39,5 TB of data to process it will take a while so I decided to try it on one of the other media servers instead (which is not fully used yet) and it didn't help so instead of just waiting until Monday I decided to write here to see if anyone else have experienced the same issue. I have tried with (and without)the "Allow Backup Exec to delete all expired backup sets" enabled with no changeof the result. Anyone who has information that can help me, it would be very appreciated? Thanks!Unable to backup Exchange 2010 with BackupExec 2015
Hi Everyone, We're running into a pretty major issue after an upgrade to BackupExec 2015 and we're pretty much at our wits end and hoping for a solution. We were successfully using BackupExec 2010 to backup our Exchange 2010 configuration to tape. We were sold BackupExec 2015 and we've been attempting to implement it to simplify our backup configuration. We built a new server and then started running our backups to BackupExec 2015. We have not been able to successfully backup our Exchange configuration since then and we're getting very frustrated. We've had a ticket open with Symantec for weeks and the agents haven't been able to provide a resolution. They just had us run a debug and came back to us that our network drivers need to be updated. I checked the network drivers on both servers and they're both running the newest available driver. And again, we didn't have an issue with BackupExec 2010. Here is what happens: We have 3 datastores. One about 900GBs, one about 400GBs, and a new one that I created as part of this troubleshooting that's about 45GBs. We've attempted to run a full backup against all three datastores and in every instance it fails at the "Consistency Check" phase for all three databases. The error that we get is: Job Completion Status Job ended: Tuesday, June 30, 2015 at 7:05:23 AM Completed status: Failed Final error: 0xe000ff12 - A communications failure has occurred with an Exchange Store resource. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-65298 Errors GRT backup set folder: \\.pdvfs\SERVERNAME\2\BEData\IMG000009 The consistency check of the snapshot for the Microsoft Exchange database Database was successful. V-79-57344-65298 - The Exchange Store service is not responding. Backup set canceled. V-79-57344-65072 - An error occurred while connecting to the Backup Exec Remote Agent on the Backup Exec server. Ensure that the job options are correct, and then submit the job again. The backup set was not created. So it backs up all of the data, passes the consistency check, and then fails on the step right after that, clears all of the data off. This issue has literally been going on for weeks. Our Exchange setup is running on older hardware and I'm getting very nervous about this issue. We've attempted disabling GRT. We've tried disk storage, deduplication disk storage, virtual tape storage, etc. We're successfully backing up Oracle, SQL server, and flat files to this new BackupExec server without issues. Any help would be GREATLY appreciated.Backup Exec 15 FP4 was anounced today but not showing up
Hi, Backup Exec 15 Feature Pack 4 was anounced today but when I run a LiveUpdate It tells me that I'm up to date. Checking installed updates I see Feature Pack 3. So isn't it available through LiveUpdate, or not yet or will it be a manual update only? Anybody else having this? Thx
