VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Continuous Data Protection (CDP) is a new feature provided by the upcoming Veeam VBR v11 mainly addressed for Tier-1 applications that cannot deal with data loss.Announced for a long time, the CDP technology allows you to configure the RPO Per Second and this can be done leveraging vSphere API for IO Filtering (VAIO). Install the Continuous Data Protection filter to hosts First step is the installation of the CDP filter to the hosts member of the cluster. The installation takes place in the Managed Servers section under Backup Infrastructure area. Before proceeding make sure your Veeam Server has been registered in your DNS infrastructure.Once the vCenter Servers have been added to the Veeam infrastructure, right click the source side vCenter and select Manage I/O filters. Configure the CDP Proxy To leverage CDP, it is required the deployment of the new CDP Proxy to handle the data. Although you can install different roles in the chosen Windows Server, make sure CDP Proxy is not alread
VeeaMover is a cool new feature available in the next Veeam Backup & Replication v12 that allows to move or copy backups to different locations.If you need to change the target repository for a Backup Job containing existing backups, a warning message is displayed and the procedure cannot be finalized until the backups have moved to the new repository.With current versions of Veeam this is a manual, time-consuming operation. Here is where VeeaMover come into play. Use casesCommon VeeaMover use cases are the following:Move backups to different repository Copy backups to different repository Migrate ReFS to XFS for Hardened Repository Migrate NTFS to ReFS Re-balance Scale-Out Repository Scale-Out Repository extent evacuation Move backups to a different locationThe target Repository can be changed also in an existing Backup Job. Move a VM to different Backup Job Copy backups to a different location Migrate backups from NTFS to ReFSAnother cool capability of VeeaMover is the option to
Veeam Backup & Replication supports and understands vSphere tags allowing the creation of Backup and Replication Jobs by selecting VMs to backup based on Tags.Tags concept was introduced in vSphere 5.5 and basically it is a label you can assign to any object (VMs, storage and so on...) in the vSphere inventory. You can assign a tag to a specific category to better identify a VM type or simply the installed OS.The use of Tags during Jobs configuration is pretty easy to configure. In the configuration wizard click Add button to add objects to backup. Click the tag icon to display VMs and Tags, select the item you want to include in the job then click Add.Using Tags you no longer need to edit a specific Backup or Replication Job to add or remove a VM. A simple click in the Tags panel of the particular VM in vSphere Client does the trick.No Backup tag?... why you should use it? Well, the No Backup Tag can be used to specify which VMs are not included in any backup on purpose. In big en
New exciting features have been announced for upcoming version 11: CDP, Linux Proxy, etc…Customers quite often ask when a HTML Veeam console will be availbale...Once VBR has been upgraded, latest console is immediately available to be used and no need to install/update the console in every admin’s computer…Do we really need a HTML console for our daily duties?Maybe we don’t need it but it would be a nice feature to have...What do you think?
When a backup policy is configured in Veeam Backup for Microsoft Azure, the job doesn't start automatically on a backup schedule.This is a known bug of the software and the fix requires a patch installation directly in the system. Install the fixAfter copying the patch provided by the support (patch Fix_263734_34880afcb0.zip) to the appliance (you can use WinSCP), stop the service with the following comand:# sudo systemctl stop veeamazurebackupInstall the package using the command:# sudo apt-get install /tmp/veeamazurebackup_1.0.0.261_amd64.debAfter few seconds the patch installation is completed successfully.Start the service veeamazurebackup with the command:# sudo systemctl start veeamazurebackupNow login to Veeam Backup for Microsoft Azure and schedule the job. After applying the patch, the job now runs on a backup schedule.The fix for this issue is quite simple to apply and takes only few minutes.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
