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!8.8KViews0likes3CommentsEnhancing resiliency for Instant Recovery
Now not just instant, but also resilient. The Enhanced Resiliency for Instant Recovery increases the data and application availability of virtual machines that are instantly recovered. This improves business continuity in case the Backup Exec server or the Hyper-V server must be restarted.6.7KViews2likes0CommentsProtect 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 UI6KViews4likes2CommentsBackup Exec 16 VSS issues with server 2012 R2
I have a new setup with Backup Exec 16 installed on Windows Server 2012 R2 64-bit. Mostly working fine with 2 virtual hosts and an exchange server, and speed is good. However, we also have a new file server to back up which is experiencing some difficulty. The server is running windows server 2012 R2 and has over 64TB of storage, so we initially ran into the error: Final error: 0x8004230c - 0x8004230c (2147754764) Backup - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected cannot snap this volume. Some reasons for this could be: - The snapshot provider that you selected does not support the volume that you are trying to snap. Try selecting the default snapshot provider, and then run the job again. -A disk with a size greater than 63 terabytes or a 4K sector disk may exist on your computer. These types of disks can cause VSS to stop unexpectedly when it creates snapshot. We reconfigured the storage in the RAID controller so that all disks presented to the OS are 62TB or less. All disks are also either 512 or 512E sectors. After running a test backup, the error was gone. However, a week later after migrating data to the new server, the same error returned. Data backs up OK, but volume shadow copy is not used. I've tried the following to resolve the issue: * Rebooting the target server * Removing and re-installing the remote agent, 3 times so far. * Completely rebuilding the Backup Exec 16 server from bare metal. There are no errors in any logs for VSS or VSC. vssadmin list writers shows no issues.(All writers present and stable) When the backup starts, the VSSVC.exe and VDS.exe services show up in task manager temporarily, but the system quickly falls back to normal file copies. VSS fails on all volumes and system state, not just the large ones. All other servers back up correctly. Testing with Windows Server Backup, Veeam Endpoint Backup FREE, and just manually creating a shadow copy on the server all succeed. The only thing I can think of is that the agent is timing out too early or testing for an issue and failing too quickly? I also don't know why the job succeeded once before more data was copied to the server.Solved5.6KViews0likes8CommentsBackup Exec 16 is here!
November 7 th is GA of Backup Exec 16, Veritas’ trusted mid-market backup solution. With support for the latest Microsoft releases and Azure cloud storage, Backup Exec 16 provides users powerful, flexible options to protect their most crucial asset: data.4.5KViews7likes3CommentsCannot Add a Linux Server at Backup Exec 16
Hi All, Can somebody help me? It's my first time in a linux environment. I have to a backup a Rhel 7.3 Linux using Backup Exec 16 (resides in Windows 2012 R2 Standard). 1. Linux agent was installed at the Rhel 7.3 server 2. But when adding the linux server at Backup Exec, there is an error. (Please see attached) I can ping the linux server from the backup exec server. I also use the IP Address of the linux server when addung it ti BE Server. Hoping for all the support.Solved3.7KViews0likes6Comments