Migrate vScope

You can move vScope to a different volume on the same server, or to a different server. When you move to a different server, you choose how much of the existing installation to bring with you: everything, everything except inventory data, or only selected parts.

The installer sets the reference path to vScope’s data, saved in the vScopeData folder. If you need to move this folder, rerun the installer to set the new data location. Here’s how to handle common migration cases.

---

Move to a Different Volume or Location on the Same Server

1. Stop the vScope service.

2. Run the vScope installer and specify the new location for the vScopeData folder (e.g., D:\vScopeData). Complete the installation.

3. Stop the vScope service again (as it will restart automatically after installation).

4. Delete the newly created vScopeData folder in the new location.

5. Move the original vScopeData folder to the new location.

6. Start the vScope service.

---

Move to a Different Server

Install vScope on the new server first, then migrate the data you want to keep. The installation is the same for all three options below.

Before you begin

1. Download the latest vScope installer and run it on the new server. When prompted, select the location for the vScopeData folder.

2. Choose what to migrate:

   If you want to…	Use
   Make the new server identical to the old one, including inventory data and history	Option 1
   Start with a clean inventory but keep content, users, Discovery scope, and settings	Option 2
   Move only specific parts, such as the Discovery scope	Option 3

---

Option 1: Migrate Everything

This includes inventory data, tags, history, settings, users, and the Discovery scope.

1. Stop the vScope service on the old and the new server.

2. Copy the vScopeData folder (e.g., C:\vScopeData) from the old server to the same location on the new server, replacing what is there.

3. Start the vScope service on the new server.

4. Complete the steps after migrating.

---

Option 2: Migrate Content, Users, Discovery Scope, and Settings Only

This includes content, user accounts, the Discovery scope, tags, and settings.

Caution

This option will exclude inventoried assets, data, and history. Also Manual Tags that have been added to assets based on their UUID will be lost.

1. Stop the vScope service on the old and the new server.

2. Copy the vScopeData folder, excluding C:\vScopeData\projects\default\modeldb, from the old server to the same location on the new server, replacing what is there.

3. Start the vScope service on the new server.

4. Complete the steps after migrating.

---

Option 3: Migrate Selected Parts Only

Use this option to move only specific parts of your configuration, for example the Discovery scope and user accounts, without bringing over everything else.

Caution

Some parts depend on others. If you migrate a part without the parts it depends on, it may be incomplete or unusable on the new server.

1. Look up the parts you want to migrate in vScopeData Folder Locations. Note the location and the dependencies of each part.

2. Add the parts your selection depends on. For example, if you migrate content, also migrate user accounts, and the user-created rule-based tags if the content uses them.

3. Stop the vScope service on the old and the new server.

4. Copy the selected files and folders from the old server to the same path in the new vScopeData folder, replacing what is there.

5. Start the vScope service on the new server.

6. Complete the steps after migrating.

---

After migrating

1. Log in to the License & Billing Account and activate a valid license.

   If no license is available, contact support for assistance.

2. Verify that all targets and credentials are accessible from the new server.