#1 Global Leader in Data Protection & Ransomware Recovery

Moving custom attributes through import/export of CSV file

KB ID: 1640
Product: Veeam ONE | 7.0 | 8.0 | 9.0 | 9.5
Published: 2013-03-29
Last Modified: 2021-03-29
mailbox
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

To export custom attributes from one installation of Business View to another, follow these steps:
  1. Click Configuration in the top right corner of the screen and navigate to the Import/Export pane.

  2. (This step is not mandatory) If you want to pre-designate which custom attributes Business View will export, prior to exporting click the Run Wizard button and follow the wizard steps.

  3. Click the Export button and choose location for saving the CSV file.

  4. Copy/move the file to the server where a new installation of Business View is located and open Business View.

  5. Once again, navigate to the Import/Export pane under Configuration and click the Import button. Specify the location of the exported CSV file and click OK.

  6. Check the Categories and Groups panes to ensure the custom atrributes have been successfully imported.

Note: Upon completion of the import operation, you may receive an error stating "0 objects(s) processed" when the data was actually imported.

Cause

The "0 objects(s) processed" error can be caused by incorrect or mismatched vCenter Server names in the vCenterServer column of the exported CSV file (IP and Host Name, Host Name and Fully Qualified Domain Name, etc.)

Solution

To resolve this error, follow these steps:
  1. Open the exported CSV file in excel and press Ctrl+F.

  2. Click the Replace tab and in the Find What field enter the name of your vCenter Server as displayed in the vCenter Servers / VI Management Servers pane of the Configuration menu in your original Business View installation.

  3. In the Replace With field, enter the name of your vCenter server as displayed in the vCenter Servers / VI Management Servers pane of the Configuration menu in your new Business View installation.        

  4. Click the Options button and change By Rows in the Search drop down menu to By Columns, then click the Replace All button.

  5. Save the CSV file with the changes you have made and try to import data from the CSV file to your new Business View installation once again.
     

More Information

Configuration menu in a previous version of Business View:

User-added image

Configuration menu in the current version of Veeam ONE Business View:

User-added image
To submit feedback regarding this article, please click this link: Send Article Feedback
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.

You have selected too large block!

Please try select less.

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.