Veeam - Tape Infrastructure - Media Pool, Media Set and Job Creation

Hello guys!

Continuing the series on Tape Infrastructure in Veeam, today I want to explain how the Media Pool, Media Set and the creation of a job that records your backups on tape as well. That is, the job will start after running a write job from backup to disk. So you guarantee your disk backup to restores faster and also keeps a copy on tape to have the necessary security that in case of disaster you still have a copy of your data on another type of media.

Starting from the Last post, we now have four tapes available in our LTO.

Before starting the job creation, we need to create our Media Pool. The Media Pool is a logical container for organizing the tapes inside the Veeam. Imagine the Media Pool as the partitions that are created in a Library to ensure that your job will only write to the tapes that are part of that Media Pool. To illustrate the Media Pool Veeam offers the following drawing:

As always, for more details on Media Pools you can CLICK HERE.

To create a new Media Pool we should click on the "Media Pools" and choose the "Add Media Pool" option.

In the first screen choose the name of your Media Pool in the way that best suits your environment and click "Next".

In the next screen we will add the tapes that will be part of this Media Pool. To do this click "Add" and select the tapes you want.

Still on this screen, we can check the option "Add tapes from Free media pool automatically when more tapes are required". Checking this option, if the Media Pool needs more tapes to complete a job, it can use tapes that are free in the library, if any. Click "Next" to proceed.

The next screen is where we will create our "Media Set". The Media Set is used to create a split within your Media Pool. Imagine that you have a Media Pool with three tapes, like the one above, but a Media Set will use two tapes because it is for your backup file server and you will create a second Media Set to record the backup of the database. Both are made by Veeam, but you want to split them into your Media Pool.

Although interesting, creating more than one Media Set will use more tapes in your environment. In the example I gave above, if the first backup of File Sever uses one tape and a half the next backup of SQL will skip to the next tape. However, using it that way makes it easier to find your backups and restore if necessary. Not to mention that if you are all in a single giant Media Set of several tapes you will need all of them to recover a data, even if it is a few megabytes. To illustrate the Veeam also offers a small design:

The Media Set is also well explained in the Veeam documentation. To access it CLICK HERE.

In our example I will keep the Media Set settings as simple as possible. For the name I will keep the Veeam pattern that will insert an ID and Date.

Below you can choose whether to create new Media Sets automatically. In this case I want to keep only one that will be used to record all my backups on the Media Pool tapes, without separating the tapes. Click "Next" to proceed.

In the next screen we should choose Media Pool retention. The options are:

  • Do not protect data - Choosing this option will not protect the tape data from being rewritten, that is, the tape can be overwritten any time it is needed.
  • Protect data for - Choose how long you want tape data to be protected against rewriting
  • Never overwrite data - Choosing this option will not be able to rewrite the tapes that will be in that Media Pool.

You can also select Offline media tracking to move all tapes that are offline to a Media Vault. Media Vault is a "safe" of off-line tapes that have already been used. For more information about Media Vault CLICK HERE. After choosing the options for your environment click on "Next".

In the next screen we can check the option "Enable parallel processing ..." to allow more than one tape job to use the LTO. The value should equal the number of drives you have on the tape robot. On this screen you can also enable the encryption of backup files if necessary. Choose the required options and click "Apply".

Click "Finish" to finish creating the Media Pool.

Now we have our Media Pool ready with three tapes and one available to be used if necessary.

Now let's create the tape job based on an existing backup job. It is possible to directly write the files, but you will not have the direct integration with your job that writes to disk. The way I'm going to demonstrate the tape job waits for the finalization of the disk job to start, always maintaining integrity of what is written to tape. Remember that you can only use this option if your license is at least Enteprise. In the standard version you can only use the option to write files that are already on disk.

In the home click on "Tape Job" and choose "Backups".

Choose the job name and click "Next".

In the next screen we will choose our job that we will copy. You can also choose an entire repository. Add the one that best suits your environment and click "Next".

In the next screen we will choose the Media Pool to record the FULL backup of our job. Click "Next" to proceed.

In the next screen we can choose to also record our incremental backups of this job. We can select a different Media Pool from the previous one or continue with it. Click "Next" to proceed.

In the next screen we can choose some automations after finishing the job:

  • Eject media upon job completion - Choosing this option will cause the tapes to be ejected from the drive after finishing.
  • Export current media set upon job completion - Choose this option to export the tapes that are part of the media set of this job. It is used when we are going to remove the tapes and file them.

In Advanced it is possible to choose the job and post script notifications, as in normal jobs. Choose the settings you need and click "Next".

In the next screen we will define the schedule of the job. It is important that the job is scheduled for after your backup to disk so that the most current files from your backup are written to tape.

We can choose how long the job should wait to start if any backup job that is part of the tape job is still running. We can also check the option "Prevent this job from being interrupted by source jobs" so that new jobs on disk do not start without the tape job ending. This prevents the tape job from being stopped before it successfully completes.

Click "Apply" and then "Finish."

When executing the job we can track what is being written to the tape.

In Tape Infrastructure we can see that one of the tapes has been loaded and is being used.

After the job is finished, if we open the tape property we can see the files that were recorded.

That's it, everybody!

That was just a little of what you can use with Veeam integration with Tape Librarys. I recommend that you read the documentation to understand all the possibilities. CLICK HERE to access the complete Tape Infrastructure documentation on Veeam.

GTranslate Your license is inactive or expired, please subscribe again!