More transparency, fewer hardware restrictions, freedom of choice, clarity of control, and immutability — that’s where backups are headed. Microsoft has been taking too long to adapt its ReFS to those consumer demands. Veeam and Linux, on the other hand, leverage those trends and offer immutability with reasonable freedom of object and cloud storage choice.
Learning how to configure Veeam Backup for Office 365 is great but restoring an O365 tenant is a whole other story. To follow this article and complete the necessary actions, you’ll need to install the explorer console provided with Veeam Backup for O365 on your server. Then, a user-friendly interface will take you through the restoration procedure.
Learn More
Part 2 discussed adding the Linux server to Veeam managed servers and adding immutable repositories, along with incompatible configs that Veeam’ll block if you try using them. Today, you will learn about the entire configuration deeper: how immutability works, scenarios with bad actors, how they can succeed, and how to test if all is working fine.
Part 1 discussed what a hardened repository was, how Veeam B&R V11 had everything to achieve that, and how to set up Linux for those purposes. Now, you will learn how to add the Linux server to Veeam managed servers and how to add immutable repositories. You’ll also learn about incompatible configs that Veeam will block if you try to use them.
Veeam Backup & Replication V11 introduced the ability to build your own immutable, hardened backup repository. There’s no more need to use third-party compatible solutions, like WORM disk storage or others. Now, you can do that using any server with storage that meets the requirements plus several supported Linux distros and XFS.
No one needs to tell that the efficiency and variety of security measures that keep your system up and running have gone quite up in recent years. However, you can’t be ready for everything, so it’s good to make sure your backup’s got your back, in this case – for Office 365 users.
Contemporary Enterprise-grade environments have all-out unstoppable demands. Apart from exceptional redundancy and uptime, such infrastructures need impeccable backup. It must be in a hardened, non-domain joined setup that’s independent of the fabrics and workloads it protects, abide by the 3-2-1 rule, and have a small footprint.
Veeam Backup and Replication 10 has just recently been released, and one of its more exciting features is the ability to back up a NAS. The latter is frequently used for diverse workloads, which include huge amounts of unstructured data. It’s often served chaotically, and it’s in a risk of being lost if there’s no specific fast redundancy mechanism in place.
Although you still won’t be able to install Veeam on Linux and the new Linux proxy won’t be superior to Windows Proxy in performance, there are certain benefits to consider still. For example, Linux has a smaller disk footprint, it doesn’t need a license, and it can act as a gateway server. Subsequently, there will be easier ways to maneuver within you backup.
Veeam enables to restore a VM to Azure from the latest recovery point. The main goal of this feature is disaster recovery. In case of failure, you can restart VMs in Azure. This feature can also be used to migrate the workload from On-Prem to Microsoft Azure. You can also restore a VM in Amazon EC2. In this topic, we’ll see how to restore a VM from Veeam to Microsoft Azure.
