How to manually test hotadd functionality

KB ID: 1184
Product: Veeam Backup & Replication
Published: 2011-08-25
Last Modified: 2022-07-15
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article documents the procedure for manually performing hotadd to test whether a Veeam Backup Proxy can attach a VM's base disks.

Solution

Requirements and Limitations

How to Test

Performing the following steps will help determine if the infrastructure is present to allow the Proxy to attach the disks of the VM to be processed using hotadd. It is advised to do this with a VM during off-peak hours as it requires a snapshot on the production server.

Note: Remember to review the cleanup section after performing the test.

  1. Create a snapshot on the VM to be processed by Veeam Backup & Replication.
  2. Within a vSphere client, attach the base disk from the VM in Step 1 to the Veeam Proxy.
    1. Edit the Veeam Proxy that will be processing the VM from Step 1.
    2. Click [ Add New Device ]
    3. Chose “Existing Hard Disk”
    4. Navigate to the location of the base disk from the VM in step 1.
    5. After selecting the disk, expand the disk node.
    6. Under "Disk Mode" select to "Independent - Nonpersistent"
    7. Click [ Ok ]

Analyzing the results:

  • If the "Reconfigure virtual machine" task completes and the disk is now attached to the proxy, this means the infrastructure is present to allow the Proxy to hotadd the VMs base disk. Proceed to the Cleanup section below.
  • If you were unable to select the base disk (VMDK) from the datastore because the datastore was not visible to be browsed, then this means the proxy you were testing with does not have access to that datastore. 
  • If the task failed, it may be a permissions-related issue that prevented the account you are using from completing the disk attach task. Test again with the account configured within Veeam Backup & Replication to access the VMware environment. If permissions issues still occur check permissions assigned to the account.
  • There are many other reasons why this task could fail, if it has failed and you would like assistance, please open a support case, and a Veeam Support Engineer will be happy to assist you.

Cleanup after test

After you have completed testing, follow these steps to clean up the environment.

  1. If you were able to attach the VM's disk to the Proxy, detach it.
    1. Edit the Veeam Proxy used in the testing.
    2. Hover over the disk that was attached during testing.
      Note: If you are unsure which disk needs to be detached from the Proxy, check the disk's file path, it should contain the name of the production server from which it is from.
    3. Click the ( X ), which will turn into a green arrow indicating that the disk will be released.
      (DO NOT select the option to "Delete files from datastore")
    4. Click [ Ok ] to release the disk(s) from the Proxy.
Identify the hotadd test disk(s) and remove from Proxy
Steps 1b and 1c: Identify the hotadd test disk(s) and remove from Proxy.
Double-check which disks are being removed, and click OK.
Step 1d: Double-check which disks are being removed, and click OK.
  1. Remove the snapshot created on the production server during testing.
 Remove the snapshot from the VM that was being tested.
Step 2: Remove the snapshot from the VM that was being tested.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.