The latter gives seamless integration with Veeam Explorer for Storage Snapshots which we will have a quick look at during the next step. Whilst this is not mandatory it makes the difference between creating a crash- and application- consistent snapshot. This is the page where you configure application-aware processing. backup copy jobs) too and in the real world this is probably what you would do.
Note that you can also configure secondary destinations (i.e. Rather than selecting a backup repository, select (in the case of NetApp) NetApp SnapShot. Here, select a virtual machine which is located on your storage appliance in the normal way and click Next. To begin the process click the big Backup Job button on the top left of the Console to start the New Backup Job wizard: This gives a tiered approach to your backup strategy by providing a very fast restore point on a local snapshot but also backing up the data in a traditional sense which can protect you against RAID or controller failures or even the loss of the entire site, providing you have an off-site copy. a backup copy) to then perform an actual backup. As for a normal backup, Veeam will perform all necessary application-aware processing but the advantage here is that you can then also configure a secondary destination (i.e. It is worth considering that, just as you can configure a backup job to create a primary backup on a local, fast disk, you can also create a backup job to create a snapshot. Whilst the underlying storage system can be configured to create snapshots directly we will do this step within Veeam (after all this is a post on Veeam rather than NetApp!). As already mentioned, if you have already configured BoSS this is your actual starting point. Configure the snapshotsĪt this point we have Veeam Backup and Replication configured with our associated integrated storage appliance. You should be able to see your storage device with any presented LUNs. You should then see something similar to the following: In this example, selecting NetApp gives us the following:įill in the IP information and then click Next:Īt this point click Add to enter the required admin permissions then click Next followed by Finish. Click the relevant system and then fill in the required information.
You can see the supported storage systems. If not, then navigate to Storage Infrastructure and then click ADD STORAGE.Īfter clicking Add Storage you should see the following: Add the storage system using the Veeam Backup ConsoleĪgain, if you have already configured Backup from Storage Snapshots you can safely skip this step. For my environment I have added the IQN of my proxy server to the initiator group on the NetApp LUN and have also ensured that the proxy has the Microsoft iSCSI initiator configured correctly.Ģ. In any case, if you have a supported storage system chances are that you will be using Backup from Storage Snapshots so the storage side of the configuration should already be in place, with the Veeam proxy having access to the LUN and the correct permissions configured in the storage world, so you can probably skip this part. I am using an iSCSI LUN with NetApp but any other supported system will work just as well. In this post we will not go into the configuration of the underlying storage in any great detail. SAN connectivity between the Veeam Proxy and the underlying storage with permissions correctly assigned.
In this post we will look at how to setup and configure this for a simple configuration running on NetApp storage. This is very useful for both testing and development purposes. Out of those which were not announced prior to launch, On Demand Sanbox for Storage Snapshots is one of the more significant features as it enables users to quickly spin up a test environment directly from the snapshot of a supported storage system rather than having to use either a backup file or a replica.
Many of these were publically announced prior to v9 release and are now well known. which came out in January, brought in a number of exciting new features. Version 9 of Veeam Backup and Replication.