Veeam Back-up & Replication: Migrate present repository volumes of a dropped server to a fresh one

 <h2>          <span id="1_Introduction">     1. Intro     </span>          </h2>     

This article is dependant on Veeam KB1905 and written for advanced administrators of Veeam Backup & Replication who’ve a basic understanding of Veeam PowerShell commands.

We’ll dive right into a disaster situation when a Veeam repository server can’t be recovered, however the block storage, useful for keeping the backups, continues to be intact and consistent. As an instance, a classic situation will be a bodily server with hardware that’s defective, but the disk shelves or fibre-channel sub-storage system isn’t suffering from the hardware failure.

By the end of the article, you ought to have successfully added the repository disk storage space to a fresh Windows or Linux server and also continue operating backups and recuperation tasks without the larger impact.

Before doing any kind of critical shifts or migration in your manufacturing environment, will have a backup copy prepared. Please observe this short article concerning the 3-2-1 Rule, an idea for optimizing data safety.

 <h2>          <span id="2_Requirements">     2. Needs     </span>          </h2>     

 <h3>          <span id="21_Windows_to_Windows_migration">     2.1. Windows to Home windows migration     </span>          </h3>     

When compared to failed supply server, the brand new server should possess the same or perhaps a newer version associated with Windows installed. It really is advised to set up all available up-dates on the brand new server. Please start to see the system needs for Repository Server in the Veeam Help Center.

The new server will need a different name then your original server.

 <h3>          <span id="22_Linux_to_Linux_migration">     2.2. Linux to Linux migration     </span>          </h3>     

When compared to failed supply server, the brand new server should possess the same or perhaps a newer version associated with the Linux distribution set up. It is advised to set up all available improvements on the brand new server. Please start to see the system specifications for Repository Server in the Veeam Help Center.

The new server will need a various name then your original server.

 <h3>          <span id="23_Status_of_the_failed_source_server">     2.3. Standing of the failed resource server     </span>          </h3>     

The initial failed server should be powered off and the repository should be permanently disconnected, even if it really is powered on later on. If both servers can entry the storage simultaneously, you may experience heavy information corruption or loss.

 <h3>          <span id="24_Status_of_the_new_target_server">     2.4. Position of the new focus on server     </span>          </h3>     

The new server must be setup and running. This consists of:

 <ul>          <li>     Network access (could be same or perhaps a new Ip).     </li>     
 <li>     DNS configured for the brand new server’s name.     </li>     
 <li>     The repository volumes are offered and mapped to the brand new server.     </li>     
 <li>     The      <a href="https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html#backup-repositories" data-wpel-link="internal" target="_blank" rel="follow noopener">     needed Firewall ports     </a>      are usually open.     </li>     
 <li>     The mandatory permissions are configured. The repository is operate by way of a Veeam Data Mover support, so please start to see the associated      <a href="https://helpcenter.veeam.com/docs/backup/vsphere/veeam_transport_service.html" data-wpel-link="internal" target="_blank" rel="follow noopener">     Helpcenter web page     </a>     .     </li>     
 <li>     The brand new target server isn't additional as a Managed Server in Veeam Back-up &amp; Replication!     </li>     

 <h2>          <span id="3_Preparation">     3. Planning     </span>          </h2>     

The first thing to accomplish is disable all of the scheduled backup jobs targeting the failed repository server.

The easiest way is always to sort the work list by Target, mark all of the dependent jobs and choose “Disable”:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-01.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="214" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-01.png" alt class="wp-image-151022 lazyload" loading="lazy" />          <img width="605" height="214" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-01.png" alt class="wp-image-151022" data-eio="l" />          </a>          </figure>          </div>     

The second step would be to develop a Veeam Backup & Replication Config Back-up and a back-up of the SQL Data source. This is often done from the overall menu by selecting “Construction Backup.”

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-02.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="258" height="414" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-02.png" alt class="wp-image-151036 lazyload" loading="lazy" />          <img width="258" height="414" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-02.png" alt class="wp-image-151036" data-eio="l" />          </a>          </figure>          </div>     

Depending on migrating the Linux or Home windows server, continue with among the next two sections.

 <h2>          <span id="4_Linux_Server">     4. Linux Server     </span>          </h2>     

Notice 1:  The brand new target server shouldn’t be additional as a Managed Server in Veeam Backup & Replication because the old server object will undoubtedly be renamed in a later on step!

Notice 2: Based on your environment, the road and devices will likely be different to the example. Please fit the actions to your needs.

 <h3>          <span id="41_Mount_the_volume">     4.1. Mount the quantity     </span>          </h3>     

Note the aged mount route of the repository in the Veeam Backup & Replication Console. This route will be required to mount the quantity on the brand new server in the right path. In this illustration, it is /repository/repo01:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-03.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="533" height="90" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-03.png" alt class="wp-image-151050 lazyload" loading="lazy" />          <img width="533" height="90" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-03.png" alt class="wp-image-151050" data-eio="l" />          </a>          </figure>          </div>     

If not done already, attach the prevailing disk with the repository information to the brand new Linux server. Here we have been using Ubuntu 21.10 and you may use

 <div class="notice-block">            <i>     sudo fdisk -l     </i>          </div>     

to list all current disks and devices. The device we have been looking for is /dev/sdb1.

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-04.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="588" height="179" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-04.png" alt class="wp-image-151064 lazyload" loading="lazy" />          <img width="588" height="179" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-04.png" alt class="wp-image-151064" data-eio="l" />          </a>          </figure>          </div>     

Make certain the mount directory is present or create it along with mkdir /repository.

Mount these devices to exactly the same path while on the old server with

 <div class="notice-block">            <i>     sudo mount -t car -v /dev/sdb1 /repository      </i>          </div>     

and be sure the documents and folders are noticeable inside the repositories subfolder:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://img.veeam.com/blog/wp-content/uploads/2022/09/26171844/migrate-repository-storage-05.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="473" height="73" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26171844/migrate-repository-storage-05.png" alt class="wp-image-151079 lazyload" loading="lazy" />          <img width="473" height="73" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26171844/migrate-repository-storage-05.png" alt class="wp-image-151079" data-eio="l" />          </a>          </figure>          </div>     

Since you should have the mount being available following a reboot, check these devices UUID with

 <div class="notice-block">            <i>     sudo blkid /dev/sdb1      </i>          </div>     

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172038/migrate-repository-storage-06.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="22" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172038/migrate-repository-storage-06.png" alt class="wp-image-151094 lazyload" loading="lazy" />          <img width="605" height="22" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172038/migrate-repository-storage-06.png" alt class="wp-image-151094" data-eio="l" />          </a>          </figure>          </div>     

and add this to the /etc/fstab document:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172113/migrate-repository-storage-07.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="69" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172113/migrate-repository-storage-07.png" alt class="wp-image-151108 lazyload" loading="lazy" />          <img width="605" height="69" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172113/migrate-repository-storage-07.png" alt class="wp-image-151108" data-eio="l" />          </a>          </figure>          </div>     

Based on your storage answer, you may want additional mount attributes within the fstab file. For instance, the attribute “nofail” could be necessary to properly mount iSCSI products during boot once the network isn’t ready.

Now you possess added the foundation volume with the prevailing repository data to the brand new target server.

 <h3>          <span id="42_Additional_steps_for_Hardened_Linux_Repositories">     4.2. Additional methods for Hardened Linux Repositories     </span>          </h3>     

If you used the initial server as a Veeam Hardened Linux Repository, please perform these additional ways on the brand new server. In this instance, the volume mount stage will be /vbrrepo and the repository is situated in /vbrrepo/hardened .

Create a user accounts with exactly the same ID since it was upon the older server. In this illustration, the ID is 1001:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-08.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="118" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-08.png" alt class="wp-image-151122 lazyload" loading="lazy" />          <img width="605" height="118" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-08.png" alt class="wp-image-151122" data-eio="l" />          </a>          </figure>          </div>     

 <h3>          <span id="43_Additional_information_on_immutable_flags">     4.3. More information on immutable flags     </span>          </h3>     

The VBM files in a repository store metadata information regarding the restore points, how they’re linked to one another plus some more data that should be up-to-date on each job run. This is why the VBM data files cannot possess the immutable flag.

Examine the immutable flags with

 <div class="notice-block">            <i>     sudo lsattr -R /vbrrepo/hardened :      </i>          </div>     

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-09.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="163" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-09.png" alt class="wp-image-151136 lazyload" loading="lazy" />          <img width="605" height="163" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-09.png" alt class="wp-image-151136" data-eio="l" />          </a>          </figure>          </div>     

For management purpose, enough time until backup documents are locked for immutability is stored in .veeam.*.lock files inside each repository folder.

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-10.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="114" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-10.png" alt class="wp-image-151150 lazyload" loading="lazy" />          <img width="605" height="114" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-10.png" alt class="wp-image-151150" data-eio="l" />          </a>          </figure>          </div>     

This information will help to obtain a better understanding when restore points could be deleted.

If you realise any inconsistency between your data files flagged for immutability and those listed in the .veeam.*.lock document, please start a Veeam support situation because of this to be corrected.

Continue with renaming the Manged Server as explained later in this post.

 <h2>          <span id="5_Windows_Server">     5. Home windows Server     </span>          </h2>     

 <div class="notice-block">      Note 1:  The brand new target server shouldn't be additional as a Managed Server in Veeam Back-up &amp; Replication because the old server item will undoubtedly be renamed in a afterwards step!      </div>     

 <div class="notice-block">      Note 2:  Based on your environment, the road and devices will likely be different to the example. Please match the measures to your preferences.      </div>     

Note the outdated mount route and generate letter of the repository in the Veeam Backup & Replication Console. This route will be required to mount the quantity on the brand new server with the right push letter. In this instance, it is E:Repo01:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172613/migrate-repository-storage-11.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="595" height="64" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172613/migrate-repository-storage-11.png" alt class="wp-image-151164 lazyload" loading="lazy" />          <img width="595" height="64" src="https://img.veeam.com/blog/wp-content/uploads/2022/09/26172613/migrate-repository-storage-11.png" alt class="wp-image-151164" data-eio="l" />          </a>          </figure>          </div>     

If not currently done, attach the prevailing disk with the repository information to the new Home windows Server and open up the Disk Management system to start to see the offline disk:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-12.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="357" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-12.png" alt class="wp-image-151178 lazyload" loading="lazy" />          <img width="605" height="357" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-12.png" alt class="wp-image-151178" data-eio="l" />          </a>          </figure>          </div>     

Arranged the disk online:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-13.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="363" height="216" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-13.png" alt class="wp-image-151192 lazyload" loading="lazy" />          <img width="363" height="216" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-13.png" alt class="wp-image-151192" data-eio="l" />          </a>          </figure>          </div>     

It should are available online with the mount letter from the aged server:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-14.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="426" height="124" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-14.png" alt class="wp-image-151206 lazyload" loading="lazy" />          <img width="426" height="124" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-14.png" alt class="wp-image-151206" data-eio="l" />          </a>          </figure>          </div>     

If the drive letter isn’t assigned automatically, you are able to do this utilizing the “Change Drive Letter and Paths…” option:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-15.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="170" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-15.png" alt class="wp-image-151220 lazyload" loading="lazy" />          <img width="605" height="170" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-15.png" alt class="wp-image-151220" data-eio="l" />          </a>          </figure>          </div>     

Usually do not run any “File format…” option on the quantity!

Check that all of the backup files are usually visible:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-16.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="236" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-16.png" alt class="wp-image-151234 lazyload" loading="lazy" />          <img width="605" height="236" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-16.png" alt class="wp-image-151234" data-eio="l" />          </a>          </figure>          </div>     

You can now continue with another steps inside the Veeam Backup & Replication console.

 <h2>          <span id="6_Migration_within_Veeam_Backup_Replication">     6. Migration within Veeam Back-up &amp; Replication     </span>          </h2>     

If the repository server is set from the operating-system and volume perspective, you have to perform migration tips within Veeam Backup & Replication.

 <h3>          <span id="61_Rename_the_Managed_Server">     6.1. Rename the Managed Server     </span>          </h3>     

The old repository server was an object in the Managed Servers in Veeam Backup & Replication. To keep all of the references and information regarding its repository info intact, we have to rename this fresh Managed Server object through PowerShell. Open up the Veeam Back-up & Replication PowerShell System:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-17.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="471" height="455" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-17.png" alt class="wp-image-151248 lazyload" loading="lazy" />          <img width="471" height="455" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-17.png" alt class="wp-image-151248" data-eio="l" />          </a>          </figure>          </div>     

Save the previous server into a good object with

 <div class="notice-block">            <i>     $Servers = Get-VBRServer -title “old-title”      </i>          </div>     

where “old-name” have to be the precise name as shown within the Veeam Backup & Replication Console:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-18.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="221" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-18.png" alt class="wp-image-151262 lazyload" loading="lazy" />          <img width="605" height="221" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-18.png" alt class="wp-image-151262" data-eio="l" />          </a>          </figure>          </div>     

Right now rename this Managed Server item to the brand new server’s name with

 <div class="notice-block">            <i>     $Servers.SetName(“new-title”)     </i>          </div>     

where “new-name” must be the IP, Hostname, or FQDN of the brand new server:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-19.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="219" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-19.png" alt class="wp-image-151276 lazyload" loading="lazy" />          <img width="605" height="219" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-19.png" alt class="wp-image-151276" data-eio="l" />          </a>          </figure>          </div>     

In the Veeam Backup & Replication gaming console, you should now start to see the Manged Server becoming renamed:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-20.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="229" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-20.png" alt class="wp-image-151290 lazyload" loading="lazy" />          <img width="605" height="229" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-20.png" alt class="wp-image-151290" data-eio="l" />          </a>          </figure>          </div>     

 <h3>          <span id="62_Edit_Linux_Server">     6.2. Edit Linux Server     </span>          </h3>     

To set up the Veeam services with this new server, simply open up the properties and switch the credentials if essential.

For Hardened Linux Repository, you need to use single-use credentials as described in the Help Center.

The Veeam Transportation service isn’t yet installed, it’ll be installed when applying, even though no changes have already been manufactured in the properties:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-21.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-21.png" alt class="wp-image-151304 lazyload" loading="lazy" />          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-21.png" alt class="wp-image-151304" data-eio="l" />          </a>          </figure>          </div>     

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-22.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-22.png" alt class="wp-image-151318 lazyload" loading="lazy" />          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-22.png" alt class="wp-image-151318" data-eio="l" />          </a>          </figure>          </div>     

 <h3>          <span id="63_Edit_Windows_Server">     6.3. Edit Home windows Server     </span>          </h3>     

To set up the Veeam services with this new server, simply open up the properties and modification the credentials if essential.

The Veeam Transportation service isn’t yet installed, it’ll be installed when applying even though no changes have already been manufactured in the properties:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-23.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-23.png" alt class="wp-image-151332 lazyload" loading="lazy" />          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-23.png" alt class="wp-image-151332" data-eio="l" />          </a>          </figure>          </div>     

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-24.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-24.png" alt class="wp-image-151346 lazyload" loading="lazy" />          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-24.png" alt class="wp-image-151346" data-eio="l" />          </a>          </figure>          </div>     

 <h3>          <span id="64_Update_the_Repository">     6.4. Up-date the Repository     </span>          </h3>     

The last step would be to open the properties of the Repository, change the title if desired and be sure the repository server title has successfully been changed:

 <div class="wp-block-image">          <figure class="aligncenter size-full">          <a href="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-25.png" data-wpel-link="internal" target="_blank" rel="follow noopener">          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-25.png" alt class="wp-image-151360 lazyload" loading="lazy" />          <img width="605" height="431" src="https://www.infracom.com.sg/wp-content/uploads/2022/09/migrate-repository-storage-25.png" alt class="wp-image-151360" data-eio="l" />          </a>          </figure>          </div>     

Run an incremental back-up job targeting this particular repository and be sure it completes successfully.

 <h2>          <span id="7_Conclusion">     7. Summary     </span>          </h2>     

The described steps assist in migrating a preexisting repository storage from the failed server to a fresh server by leveraging the benefit to:

 <ul>          <li>     Preserve any restore factors by reusing the prevailing storage and meet brief- and long-term protection guidelines.     </li>     
 <li>     Preserve the immutability flags and security times (if utilizing a hardened Linux repository) rather than starting a fresh timeframe with shorter defense in the beginning.     </li>     
 <li>     Avoid the have to run new complete backups for new back-up chains, since all restore factors and metadata could be kept.     </li>     
 <li>     Keep all important info for the partnership between backup work, restore factors and the repository in order to avoid the necessity of reconfiguring backup careers or scale-out repositories.     </li>     
 <li>     Avoid disruption in Veeam ONE reviews because the repository target names will undoubtedly be automatically updated.     </li>     

The listed advantages may save a dramatic period of time and administration effort. Even though the occurrence of a unsuccessful server ought to be rare, it is important especially, in such situations, to possess a fast and simple recovery option, to get back to a productive stage. The continuous dependence on data protection could be satisfied and there’s little as well as no effect on backup associated SLAs that must definitely be met.

In case you have any doubts or want further assistance, feel free to get in touch with the Veeam support .