This is set to continue with the addition of Linux proxies for CDP (Continuous Data Protection) which again can show massive savings specially for service providers.Īnd, whilst not Linux as such, Open Source in general has a big part to play in Veeam v12 with PostgreSQL being the default Veeam database new for installations. The introduction of secure Linux repositories along with Linux based backup proxies showed the commitment of Veeam to this OS, allowing businesses to make significant savings on Windows licensing. V12 has introduced a wizard for configuring the repository and removed the need for SSH access to the repo for patching and updates. In addition, the creation, ongoing maintenance and security of a hardened Linux repository has been enhanced. Now v12 brings immutability to all workloads including NAS and physical server agent backups. Today the default should be immutability for your all your backups, however this was previously limited to primary VM backups. Secure Restore to ensure integrity and safety of data prior to recovery Insider Protection used by us VCSPs to stop offsite backups being deleted Veeam have been at the forefront of providing features to protect against cyber attack and in the last 5 years alone have introduced. The same feature allows VM’s to be moved between backup jobs which would again, usually be administrative nightmare to arrange. Its ability to move backups between repositories without having to inflate the synthetic full backups to their full size – game changer. For those who are managing data backups, especially at scale, and making full use of the space-saving benefits of ReFS and/or XFS, you will absolutely love this functionality. Object storage provides several enhancements over traditional block storage with data transmission safeguards and advanced redundancy features, all helping make sure your backup data is error free and available when you need it.Īs a VCSP (Veeam Cloud Service Provider), this was the most eagerly anticipated feature for us. Historically, with block storage-based repositories, we have been reliant on expensive storage arrays at the back end to provide data resilience and availability. Control was limited to defining which backups should be offloaded to this storage. Whilst we have had the ability to burst out into object storage as part of a capacity tier “bolt-on” for some time now, this didn’t give us much control. Fundamentally object storage is now a Tier 1 storage class. One of the biggest features for me is the support for object storage as a direct target for backups. This component can not only automate recoveries using pre-defined recovery plans but also makes validation of recovery targets much easier to achieve. If you have the network bandwidth there is no reason to not run it continuously, that means in the event of a failure you will have lost the least amount of data.Click next.It’s great to see automation becoming a core feature of the product now as, when disasters strike, this puts people under pressure to recover workloads as fast as possible. Set your schedule of when you would like the veeam replication to take place. Then next screen is fairly self explanatory. If you are using any of these applications then enter the information here. The next screen is for VSS, pop in your domains admin credentials, this allows veeam to lo-gin to VSS aware applications such as SQL and Exchange. Restore points is as it says, how many replications would you like to be able to go back to. For example ALLENSERVER on the cluster would become ALLENSERVER_replica. The replica name suffix is what the replicated servers have as a suffix on the DR host. You get the option to select a repository for the backups metadata, I have a NAS box so im using it, you can just use the default setting that is the clusters datastore. On the Job settings screen that follows leave the settings of automatic proxy enabled unless you have a specific backup proxy server setup. If you have multiple datastores then it may be an idea to have multiple replication jobs the replicate to multiple stores.Once you have chosen your options click next. Then finally select the datastore you would like to replicate to. Again the same for folders of you have them defined, I do not. If you have a resource pool on your DR host then again select it, I’m just using the default pool here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |