{"id":22142,"date":"2017-09-26T09:00:11","date_gmt":"2017-09-26T07:00:11","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=22142\/"},"modified":"2020-03-15T18:08:42","modified_gmt":"2020-03-15T17:08:42","slug":"veeam-9-5-vtl-to-aws-storage-configure-tape-backup-job-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-9-5-vtl-to-aws-storage-configure-tape-backup-job-pt-2\/","title":{"rendered":"Veeam 9.5 VTL to AWS Storage: configure the Tape Backup Job - pt.2"},"content":{"rendered":"

\"veeamvtlawss3glacierconfig01\"<\/p>\n

After setting up the AWS environment, the new tape infrastructure must be configured also in Veeam to take benefit of\u00a0VTL to AWS feature.<\/p>\n

Again, since the VTL solution emulates the on-premises physical tape device<\/strong>, you don't need to change anything in terms of infrastructure and processes.\u00a0<\/p>\n

 <\/p>\n

Blog Series<\/h2>\n

Veeam 9.5 VTL to AWS Storage: setup AWS \u2013 pt.1<\/a>
\nVeeam 9.5 VTL to AWS Storage: configure the Tape Backup Job \u2013 pt.2<\/p>\n

 <\/p>\n

Connect AWS Tape devices<\/h2>\n

The Backup to Tape process using VTL copies the data from the on-premises production storage<\/strong> to the AWS S3 Storage leaving the option to further move data to most cost-effective Glacier for long-retention purposes<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig02\"<\/p>\n

First step is to establish the connection with AWS tape drives. From Veeam Proxy Server open the iSCSI Initiator to connect the tape device in AWS. In the Targets<\/strong> tab, enter the appliance gateway IP address in the Target<\/strong> field then click on\u00a0Quick Connect<\/strong> button.<\/p>\n

\"veeamvtlawss3glacierconfig03\"<\/p>\n

A list of discovered devices is displayed in the Quick Connect<\/strong> window. Select the media changer<\/strong> device and click Connect<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig04\"<\/p>\n

The device has been connected successfully. Click Done<\/strong>\u00a0to close the wizard.<\/p>\n

\"veeamvtlawss3glacierconfig05\"<\/p>\n

First device is now connected to the Veeam Proxy Server.<\/p>\n

\"veeamvtlawss3glacierconfig06\"<\/p>\n

Now proceed with the second device. Select the tape drive 1<\/strong> then click Connect<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig07\"<\/p>\n

Click OK<\/strong> to establish the connection.<\/p>\n

\"veeamvtlawss3glacierconfig08\"<\/p>\n

Repeat same procedure to connect all tape drives displayed in the Discovered targets<\/strong> list. Click OK<\/strong> when done.<\/p>\n

\"veeamvtlawss3glacierconfig09\"<\/p>\n

Once all devices are connected, access the Veeam Proxy Server's Device Manager<\/strong> and expand the Tape drives<\/strong> item. Right cick the first device and select Properties<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig10\"<\/p>\n

Go to Driver<\/strong> tab and ensure the Driver Provider<\/strong>\u00a0vendor is Microsoft. Click OK<\/strong> to close the window.<\/p>\n

\"veeamvtlawss3glacierconfig11\"<\/p>\n

 <\/p>\n

Configure Tape Server<\/h2>\n

Once the tape devices are connected, open the Veeam Server console, select the Tape Infrastructure<\/strong> tab and click Add Tape Server<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig12\"<\/p>\n

In the Choose server<\/strong> field enter the Veeam Proxy Server on which tape drives have been configured and click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig13\"<\/p>\n

Click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig14\"<\/p>\n

If not already present, Veeam tape components are installed in the selected server. Click Apply<\/strong> to proceed.<\/p>\n

\"veeamvtlawss3glacierconfig15\"<\/p>\n

Components are being installed in the server. Click Next<\/strong> when the procedure has completed.<\/p>\n

\"veeamvtlawss3glacierconfig16\"<\/p>\n

Enable the Start tape libraries inventory when I click Finish<\/strong> then click Finish<\/strong> to exit the wizard.<\/p>\n

\"veeamvtlawss3glacierconfig17\"<\/p>\n

The AWS Gateway-VTL 0100<\/strong> library is discovered and associated tape drives are displayed in the Drives<\/strong> area.<\/p>\n

\"veeamvtlawss3glacierconfig18\"<\/p>\n

 <\/p>\n

Create a new Media Pool<\/h4>\n

Now click on Add Media Pool<\/strong> to configure the media pool to use.<\/p>\n

\"veeamvtlawss3glacierconfig19\"<\/p>\n

Enter a Name<\/strong> and optionally a Description<\/strong> then click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig20\"<\/p>\n

Click Add button<\/strong> to select the tape to use then click OK<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig21\"<\/p>\n

The tape has been added to the new Media Pool. Enable the self explanatory option Add tapes from media pool automatically when more tapes are required<\/strong> then click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig22\"<\/p>\n

Enter a Media set name<\/strong> and select a suitable option for automating the creation of new media set. Click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig23\"<\/p>\n

Select the Never overwrite data<\/strong> as Data retention policy<\/strong> and click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig24\"<\/p>\n

Here you can enable parallel processing<\/strong> and encryption<\/strong>. Select the options you need then click Apply<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig25\"<\/p>\n

Click Finish<\/strong> to create the new media pool.<\/p>\n

\"veeamvtlawss3glacierconfig26\"<\/p>\n

The new media pool has been created and displayed in the Media Pools<\/strong> area.<\/p>\n

\"veeamvtlawss3glacierconfig27\"<\/p>\n

 <\/p>\n

Configure Tape Backup Job<\/h2>\n

Next step is the configuration of the tape backup job. Go to Backup & Replication<\/strong> tab, click Tape Job<\/strong>\u00a0in the menu bar and select Backups<\/strong>\u00a0option.<\/p>\n

\"veeamvtlawss3glacierconfig28\"<\/p>\n

Enter the job Name<\/strong> and click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig29\"<\/p>\n

Click Add<\/strong> button to select virtual machines to backup then click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig30\"<\/p>\n

From the Media pool for full backups<\/strong> dropdown menu select the media pool to use then click Next<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig31\"<\/p>\n

Enable Archive incremental backups to tape<\/strong> option and select from the dropdown menu the media pool to store incremental backups. Click Next<\/strong> to continue.<\/p>\n

\"veeamvtlawss3glacierconfig32\"<\/p>\n

Enable both Media automation<\/strong> options. Export current media set upon job completion<\/strong>\u00a0option allows the automatic tape offload to Amazon S3 after backup job is completed. Click Next<\/strong> to continue.<\/p>\n

\"veeamvtlawss3glacierconfig33\"<\/p>\n

Configure a backup Schedule<\/strong> and click Apply<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig34\"<\/p>\n

Click Finish<\/strong> to create the new Backup to Tape Job.<\/p>\n

\"veeamvtlawss3glacierconfig35\"<\/p>\n

To start the backup job immediately, from Tape<\/strong> section under Job<\/strong>\u00a0area right click the just created Backup to Tape job and select Start<\/strong>.<\/p>\n

\"veeamvtlawss3glacierconfig36\"<\/p>\n

The backup job is executed.<\/p>\n

\"veeamvtlawss3glacierconfig37\"<\/p>\n

When the backup job has completed successfully, click OK<\/strong> to exit the window.<\/p>\n

\"veeamvtlawss3glacierconfig38\"<\/p>\n

Analyzing the available Tape<\/strong> backups, the selected virtual machines have been processed.<\/p>\n

\"veeamvtlawss3glacierconfig39\"<\/p>\n

Looking at the AWS console, you can check in Tapes<\/strong>\u00a0tab the tape currently used and the space consumed by the backup.<\/p>\n

\"\"<\/p>\n

This solution allows the companies to get rid of physical tapes moving to a better cost-effective and scalable solution<\/strong>.<\/p>\n

\"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

After setting up the AWS environment, the new tape infrastructure must be configured also in Veeam to take benefit of\u00a0VTL to AWS feature. Again, since the VTL solution emulates the on-premises physical tape device, you don't need to change anything in terms of infrastructure and processes.\u00a0<\/p>\n","protected":false},"author":3,"featured_media":22143,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2138,933],"tags":[579,584,1785],"class_list":["post-22142","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-backup-en","category-veeam-en","tag-backup-en","tag-veeam-en","tag-vtl","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/22142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=22142"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/22142\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/22143"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=22142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=22142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=22142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}