Manual DR of Backup Exec Server - Backup files
Hello Team, Backup Exec Version: 16 OS: Windows Server 12 R2 Some reason my backup exec server got corrupted and lost. However, I have the access to the backup files B2D. I tried below but not working. Created new server with the OS 2012 r2 Installed Backup Exec 16 Created new B2D and copied the files from old B2D. Ran the Inventory job successfully but, catalog job failed with the above error message. V-79-57344-33994 - The data being read from the media is inconsistent. Appreciate for any recommendations or suggestions. I have a test lab, ready to perform any work around. Thanks, Durgarao
Protect Windows Server 2016 with Veritas Backup Exec 16!
So what does that really mean? If I install the released bits of Windows 2016 server, could I then install Veritas Backup Exec 16 on it and start using it immediately? Well, the answer is “Yes” ! Additionally, you can use Windows 2016 server to install Backup Exec Server and Agent, as well as options and components such as: Protection for remote Windows 2016 Server computers. Simplified Disaster Recovery (SDR), which recovers the entire windows 2016 server from a bare metal state. Backup and recovery of the latest Microsoft Hyper-V 2016 platform. Protection for resilient file system (ReFS) & Dedupe Volumes. Support for the current versions of Microsoft applications like SQL Server, Microsoft Exchange, and SharePoint Active directory for application item level GRT on Windows 2016. How did we go about supporting Windows 2016? Deploy Windows 2016 today, without waiting for backup to catch up! There is no need to take the old approach of waiting until late in the game to start implementing a new server OS. You can immediately start protecting Windows Server 2016 with Veritas Backup Exec 16. We have been actively working with Windows 2016 builds for quite some time now. We tested technical preview releases and prepared ourselves to support the final release. Testing on Windows 2016 Server began almost 10 months ago with validation of pre-release builds. We executed manual as well as automation test suites on each pre-release build. We executed over 1000 test cases (500 automated and over 500 manual) spread across features such as core Backup and Restore, Simplified Disaster Recovery, Hyper-V, and Microsoft applications such as Exchange, SharePoint, Active directory, and SQL server. We have qualified over 20 Windows 2016 Server pre-release builds with different configurations, such as Windows 2016 failover cluster, storage pools, and ReFS. Backup Exec 16 has been tested with all versions of Windows 2016 Server, such as Datacenter, Essentials, Standard, Storage Server and Hyper-V Edition. Automation helped us in a big way to qualify the pre-release builds. In addition, our manual test lab consists of over 30 test servers, on which every new build of Windows Server was installed and manual test cases were executed. How did automation help testing Backup Exec 16 on Window 2016? Providing support to new offering coming in market in a short time span is a challenging job. Without automation, repeating the test cycles on frequent early-access builds of an upcoming OS or application, is very difficult. To address this problem and provide maximum coverage, we utilize the automation labs of Backup Exec. We deployed Windows 2016 drops on an automation environment consisting of more than 100 virtual machines. We refreshed of the Windows 2016 build on at a one-week cadence on our setups, with a two-week cadence on the more complex setups Over 500 test cases have been running daily on Windows 2016 builds right since April 2016 till Windows RTM. We were not only able to catch potential issues in our product but also were able to identify and worked with Microsoft to resolve Windows issues. All builds with fixes were re-tested again by automation. We were successfully able to provide automation for various features of Backup Exec 16 mentioned below: Feature Names: Install, Migration ,Licensing and Upgrade Base functionality of Backup and Restore and BEMCLI support Disaster Recovery Hyper-V Exchange SQL MSFT-Active Directory Various supported Storage types AVVI CAS General UI
Exchange db backup goes fine but restore shows empty arc/db
Hi, I am having problems restoring emails using the restore function.The backup of the email server goes perfect and all databases are backed up, when i check the disk and catalog i see all databases are backed up however i cannot browse the selection. However when i try to restore emails or email folders it doesnt show anything when i expand the database, it just waits and gives a Error 95. I remember having this issue in the past which was solved by a hotfix (cant remember for sure) however i already installed the patches and hotfixes. Can anyone tell me what i can do? No correct exchange backup can be a big problem.
Expired Backup Sets unable to delete on Backup Exec 16
Hi, I need some helps how to delete expired Backup Sets on Backup Exec 16. [Done] - "Allow Backup Exec to delete all expired backup sets" is ticked. - Backup Sets I want to delete is "Expired". - "DeleteLastRecoverySetsOnceExpired" registry value is 1. - Backup Exex 16 is the latest as of Jan 2018. However it is not deleting after hours unfortunately. I went through topics here in the past, but nothing worked so far. If you have any tips I can try next, please let me know. Thank you!
Initial observations from Backup Exec 16 and Windows Server 2016
We've been completing some initial testing with Backup Exec 16 and Windows Server 2016 and thought we'd share the results. 1. The upgrade of the Backup Exec to 16 and then the backup server to Windows Server 2016 went smoothly. 2. System State backups appear to run very slowly whenthe Windows Defender service (Antimalware Service Executable)is running real time scanning. 3. We haven't yet been able to successfully complete a backup of AD DS running on Windows Server 2016 when GRT and consistency checking is enabled. The following errors and warnings are listed: The consistency check of the snapshot for the Microsoft Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) transaction log ntds has failed. You should check for possible data corruption in the transaction log that is online. VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.206\x86_installed is not present on the snapshot. VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.0\amd64_installed is not present on the snapshot. VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.206\amd64_installed is not present on the snapshot. VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.0\x86_installed is not present on the snapshot. 4.Our tests of Active Directory show no problems with the consistency of the database and then are no errors or warnings logged on the AD server during the backup.
