{"id":17999,"date":"2016-08-22T09:00:18","date_gmt":"2016-08-22T07:00:18","guid":{"rendered":"http:\/\/nolabnoparty.com\/en\/?p=17999"},"modified":"2020-03-15T18:09:54","modified_gmt":"2020-03-15T17:09:54","slug":"veeam-9-scale-out-backup-repository-setup","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-9-scale-out-backup-repository-setup\/","title":{"rendered":"Veeam 9: scale-out backup repository setup"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-18002 size-full\" title=\"veeamscaleoutsetup01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup01.jpg\" alt=\"veeamscaleoutsetup01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Feature introduced in Veeam Backup &amp; Replication 9, Scale-out Backup Repository is a\u00a0<strong>l<span class=\"fontstyle0\">ogical entity<\/span><\/strong><span class=\"fontstyle0\"> made of<\/span><strong><span class=\"fontstyle0\"> multiple simple repositories<\/span><\/strong>\u00a0that\u00a0can be used to store backup and backup copy jobs.<\/p>\n<p>The Scale-out Backup Repository can comprise <strong>one or more extents<\/strong> where an extent is a standard backup repository configured in the backup infrastructure.<!--more--><\/p>\n<p>This feature\u00a0is available only in Veeam\u00a0<strong>Enterprise and Enterprise Plus editions<\/strong> with the following limitations:<\/p>\n<ul>\n<li><strong>Enterprise<\/strong> - allows up to 3 extents<\/li>\n<li><strong>Enterprise Plus<\/strong> - unlimited extents<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Backup storage management<\/h2>\n<p>In medium and large\u00a0environments, the management of backup storage devices can be a hard work for administrators.\u00a0Repositories have a <strong>fixed size<\/strong>\u00a0and space may not be <strong>consumed properly<\/strong> over time.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18003 size-large\" title=\"veeamscaleoutsetup02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup02-600x401.jpg\" alt=\"veeamscaleoutsetup02\" width=\"600\" height=\"401\" \/><\/p>\n<p>Using simple repositories, each backup job\u00a0<strong>needs to be assigned<\/strong> to a specific repository.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18004 size-large\" title=\"veeamscaleoutsetup03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup03-600x278.jpg\" alt=\"veeamscaleoutsetup03\" width=\"600\" height=\"278\" \/><\/p>\n<p>Using Scale-out Backup Repository instead, a\u00a0backup job is pointed to the scale-out repository which\u00a0decides the <strong>best target<\/strong> to run the job. The backup storage <strong>devices management<\/strong> can be reduced without the issue of <strong>underutilized backup<\/strong> devices, optimizing IT costs and improving backup performance.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18005 size-large\" title=\"veeamscaleoutsetup04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup04-600x272.jpg\" alt=\"veeamscaleoutsetup04\" width=\"600\" height=\"272\" \/><\/p>\n<p>This solution avoid the problem of <strong>relocating backup chains<\/strong> when repositories run out of space and administrators can easily <strong>add a new extent<\/strong>\u00a0to the existing Scale-out Repository.<\/p>\n<p>&nbsp;<\/p>\n<h2>Setup a\u00a0Scale-out Backup Repository<\/h2>\n<p>To configure a Scale-out Backup Repository you need to choose\u00a0the available\u00a0storage devices from <strong>Backup Repositories<\/strong> tab.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18010 size-large\" title=\"veeamscaleoutsetup05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup05-600x387.jpg\" alt=\"veeamscaleoutsetup05\" width=\"600\" height=\"387\" \/><\/p>\n<p>Access the <strong>Backup Infrastructure<\/strong> section and select <strong>Scale-out Repositories<\/strong> tab. Click <strong>Add Scale-out Repository<\/strong> to run the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18011 size-full\" title=\"veeamscaleoutsetup06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup06.jpg\" alt=\"veeamscaleoutsetup06\" width=\"562\" height=\"590\" \/><\/p>\n<p>Enter\u00a0the <strong>Name<\/strong> for the Scale-out Repository and optionally a <strong>Description<\/strong> then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18012 size-large\" title=\"veeamscaleoutsetup07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup07-600x421.jpg\" alt=\"veeamscaleoutsetup07\" width=\"600\" height=\"421\" \/><\/p>\n<p>Click <strong>Add<\/strong>\u00a0button to specify the <strong>extents<\/strong> to use. Select the <strong>backup repositories<\/strong> to include and click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18013 size-large\" title=\"veeamscaleoutsetup08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup08-600x421.jpg\" alt=\"veeamscaleoutsetup08\" width=\"600\" height=\"421\" \/><\/p>\n<p>Click <strong>Advanced<\/strong>\u00a0button to access the\u00a0<strong>Advanced Settings<\/strong>. Two options are available:<\/p>\n<ul>\n<li><strong>Use per-VM backup files<\/strong> - enabled by default, it improves performance optimizing disk usage. If existing repositories are imported with\u00a0backup files already stored, an <strong>Active Full Backup<\/strong> needs to be run\u00a0to switch to per-VM files.<\/li>\n<li><strong>Perform full backup when required extent is offline<\/strong> - if the extent containing the backup chain is not available, it allows to complete a successful backup. This feature increase the <strong>space consumption<\/strong>\u00a0each time a new full backup is created.<\/li>\n<\/ul>\n<p>Once configured the Advanced Settings, click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18014 size-large\" title=\"veeamscaleoutsetup09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup09-600x421.jpg\" alt=\"veeamscaleoutsetup09\" width=\"600\" height=\"421\" \/><\/p>\n<p>When all the required extents have been selected, click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18015 size-large\" title=\"veeamscaleoutsetup10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup10-600x421.jpg\" alt=\"veeamscaleoutsetup10\" width=\"600\" height=\"421\" \/><\/p>\n<p>Select the <strong>Policy<\/strong> to use as backup files placement and click <strong>Next<\/strong>.\u00a0You have two different policies available:<\/p>\n<ul>\n<li><strong>Data locality<\/strong> - all extents are at the same level and all dependent files are stored on the <strong>same extent<\/strong>.<\/li>\n<li><strong>Performance<\/strong> - backups are stored on <strong>different extents<\/strong> separating full backups from incremental backups improving performance.\u00a0If the full backup is stored on a <strong>failed repository<\/strong> or stored on an <strong>extent under maintenance<\/strong>, the system may create a new full backup\u00a0breaking your incremental backup chain.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18016 size-large\" title=\"veeamscaleoutsetup11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup11-600x421.jpg\" alt=\"veeamscaleoutsetup11\" width=\"600\" height=\"421\" \/><\/p>\n<p>When the Scale-out Backup Repository has been\u00a0created successfully, click <strong>Finish<\/strong> to exit the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18017 size-large\" title=\"veeamscaleoutsetup12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup12-600x421.jpg\" alt=\"veeamscaleoutsetup12\" width=\"600\" height=\"421\" \/><\/p>\n<p>The new created repository.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18018 size-large\" title=\"veeamscaleoutsetup13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup13-600x333.jpg\" alt=\"veeamscaleoutsetup13\" width=\"600\" height=\"333\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Configure a Backup Job<\/h2>\n<p>From the Veeam console, add a new Backup Job. Enter a job\u00a0<strong>Name<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18019 size-large\" title=\"veeamscaleoutsetup14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup14-600x421.jpg\" alt=\"veeamscaleoutsetup14\" width=\"600\" height=\"421\" \/><\/p>\n<p>Specify the VMs to backup and click <strong>Next<\/strong>.\u00a0Note that a\u00a0<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-9-using-vsphere-tags-backup\/\">VMware vSphere tag<\/a>\u00a0has been used in this\u00a0backup job.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18020 size-large\" title=\"veeamscaleoutsetup15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup15-600x421.jpg\" alt=\"veeamscaleoutsetup15\" width=\"600\" height=\"421\" \/><\/p>\n<p>Select the Scale-out Backup Repository just created. The total amount of available space is the\u00a0<strong>combined space<\/strong> of the extents added\u00a0during the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18022 size-large\" title=\"veeamscaleoutsetup16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup16-600x421.jpg\" alt=\"veeamscaleoutsetup16\" width=\"600\" height=\"421\" \/><\/p>\n<p>Leave default if you don't need VSS processing. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18023 size-large\" title=\"veeamscaleoutsetup17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup17-600x421.jpg\" alt=\"veeamscaleoutsetup17\" width=\"600\" height=\"421\" \/><\/p>\n<p>Specify a <strong>Schedule<\/strong> then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18024 size-large\" title=\"veeamscaleoutsetup18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup18-600x421.jpg\" alt=\"veeamscaleoutsetup18\" width=\"600\" height=\"421\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to save the Backup Job configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18025 size-large\" title=\"veeamscaleoutsetup19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup19-600x421.jpg\" alt=\"veeamscaleoutsetup19\" width=\"600\" height=\"421\" \/><\/p>\n<p>Right click the Backup Job and select <strong>Start<\/strong> to test the new repository.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18026 size-full\" title=\"veeamscaleoutsetup20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup20.jpg\" alt=\"veeamscaleoutsetup20\" width=\"550\" height=\"425\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Maintenance<\/h2>\n<p>Two\u00a0service actions can be performed with extents of scale-out backup repositories:<\/p>\n<ul>\n<li>Put extents to the maintenance mode<\/li>\n<li>Evacuate backups from extents<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Maintenance Mode<\/h4>\n<p>If you want to upgrade the backup repository server and add more memory or\u00a0replace a storage device, you must put the extent to the <strong>maintenance mode<\/strong>.<\/p>\n<p>Right click the repository to process\u00a0and select <strong>Maintenance mode<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18029 size-large\" title=\"veeamscaleoutsetup21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup21-600x387.jpg\" alt=\"veeamscaleoutsetup21\" width=\"600\" height=\"387\" \/><\/p>\n<p>The repository has been put in maintenance mode.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18030 size-large\" title=\"veeamscaleoutsetup22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup22-600x467.jpg\" alt=\"veeamscaleoutsetup22\" width=\"600\" height=\"467\" \/><\/p>\n<p>When an extent is in maintenance mode, the <strong>functionality is limited<\/strong>:<\/p>\n<ul>\n<li>New tasks targeted at this extent are <strong>not started<\/strong>.<\/li>\n<li>VM data from backup files residing on the extent<strong> cannot be restored<\/strong>.<\/li>\n<\/ul>\n<p>When you enable the maintenance mode, the <strong>Repository Maintenance job<\/strong>\u00a0checks the status of jobs and tasks targeted at the extent and puts the extent to one of the following modes:<\/p>\n<ul>\n<li>If <strong>no tasks<\/strong> using the extent are currently running, the job puts the extent to the maintenance mode immediately.<\/li>\n<li>If the <strong>extent is busy<\/strong> with any task,\u00a0the job puts the extent to the Maintenance pending state and waits for the task to complete. When the task is complete, the extent is put to the maintenance mode.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Backup Files Evacuation<\/h4>\n<p>To <strong>exclude an extent<\/strong> from the scale-out backup repository, the backup files need to be evacuated from this extent.\u00a0The extent must be put to the <strong>Maintenance mode<\/strong> before you can evacuate backups.\u00a0When the procedure is executed, the system\u00a0moves backup files from the extent to other extents that belong to the same scale-out backup repository maintaining\u00a0the <strong>backup chains consistent<\/strong>.<\/p>\n<p>To evacuate backup files, right click the extent in maintenance mode and select<strong> Evacuate backups<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18031 size-large\" title=\"veeamscaleoutsetup23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup23-600x348.jpg\" alt=\"veeamscaleoutsetup23\" width=\"600\" height=\"348\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to proceed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18033 size-full\" title=\"veeamscaleoutsetup24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup24.jpg\" alt=\"veeamscaleoutsetup24\" width=\"519\" height=\"131\" \/><\/p>\n<p>Files are evacuated from selected extent.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18035 size-full\" title=\"veeamscaleoutsetup25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/08\/veeamscaleoutsetup25.jpg\" alt=\"veeamscaleoutsetup25\" width=\"553\" height=\"379\" \/><\/p>\n<p>When the evacuation is completed, the processed extent can be <strong>safely removed<\/strong>\u00a0from the Scale-out Backup Repository.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Feature introduced in Veeam Backup &amp; Replication 9, Scale-out Backup Repository is a\u00a0logical entity made of multiple simple repositories\u00a0that\u00a0can be used to store backup and backup copy jobs. The Scale-out Backup Repository can comprise one or more extents where an extent is a standard backup repository configured in the backup infrastructure.<\/p>\n","protected":false},"author":3,"featured_media":18002,"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,1722,584],"class_list":["post-17999","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-backup-en","category-veeam-en","tag-backup-en","tag-scale-out","tag-veeam-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/17999","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=17999"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/17999\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/18002"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=17999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=17999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=17999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}