CA Visual Infrastructure - Best practices for data migration between CA VI servers.

Document created by NestorFalcon Employee on Jan 9, 2015Last modified by Melissa Potvin on Jul 13, 2016
Version 3Show Document
  • View in full screen mode

There are basically 2 ways to migrate data from one VI server to another:
-. Full DB and APP export and import: This mechanism migrates the full server including users, configuration and data. It is not covered in this document.

-. Building or Floor migration: This procedure migrates only a part of the source server data (a building, a floor,...) but it can also be used to migrate all the DC buildings. This method is covered in this document.

 

Migrating a DC Floor or a Building between two CA VI servers.

 

 

2 high level steps:

a. Migration of the Building/Floor layout: This comprises the skeleton of the building/floor: areas, walls and building definitions.

b. Migration of the assets: Export of all the devices and relationships from the source server and Import on the target server.

 

Migration of the Building/Floor layout


BUILDING AND FLOOR EXPORT:

1. Login as “vdc” in the source server.

2. Run the command “/opt/VDC/bin/exportfloor” and specify option (2).

3. Specify the “City Name”, “Building Name” and “Floor name”.

Sample output:

/opt/VDC/bin/exportfloor

################

1) Export Floor

2) Export Floor with building

3) Import Floor

4) Import Floor with bulding

5) Update Building Location

x) Exit

################

Enter Your Selection: 2

Start export floor.

Specify the City Name:New York

Specify the Building Name:MainDC

Specify the Floor Name:basement1

...

Export building end.


4. Floor and building have been exported to a folder called “floor” under /opt/VDC/data in the source server.
5. Copy this folder to a different location or to your local computer and rename it to something that will allow you to identify the exported data, for instance, “Building MainDC and basement1”.
     It is very important to copy this “floor” folder out of /opt/VDC/data because next commands will overwrite the folder.
6. Run again the command “exportfloor” as “vdc” user, but specify option (1) (the building has already been exported, now we are going to export the floors).
7. Specify the “City Name”, “Building Name” and “Floor name”.

Sample output:
/opt/VDC/bin/exportfloor
################
1) Export Floor
2) Export Floor with building
3) Import Floor
4) Import Floor with bulding
5) Update Building Location
x) Exit
################
Enter Your Selection: 1
Start export floor.
Specify the City Name:New York
Specify the Building Name:MainDC
Specify the Floor Name:F1
...

 

Export floor end

 

 

8. One more time, copy the folder /opt/VDC/data/floor to your local computer and rename it indicating the name of the exported floor, for instance, “Floor1”.

9. Repeat steps 6 and 7 until all floors have been exported to different folders. The Building and Floor export have been completed.

 

 

BUILDING AND FLOOR IMPORT

1. The import of a building + floor must be done floor by floor.

2. Start with the folder that contains the building first (e.g. “Building MainDC and basement1” exported in first place before).

3. Place the folder in the target server under /opt/VDC/data and rename it to “floor”.

4. Run the command “exportfloor” as “vdc” user and specify option (4) to import building and floor.

5. Specify the floor index (where index -1 is the basement, index 1 is floor0, index 2 is floor1 and so on).

Sample output:

/opt/VDC/bin/exportfloor

################

1) Export Floor

2) Export Floor with building

3) Import Floor

4) Import Floor with bulding

5) Update Building Location

x) Exit

################

Enter Your Selection: 4

...

Specify the Floor Index:-1

...

Import building end.

 

 

6. At this point, the building and one floor (basement -1 in this example) have been imported to the target VI server.

7. Proceed with another floor. Place the folder under /opt/VDC/data and rename it to “floor”.

8. Run again “/opt/VDC/bin/exportfloor” but this time choose option (3) because the building has already been imported.

Specify the “City Name”, “Building Name” and “Floor index” where the floor will be imported.

Sample output:

/opt/VDC/bin/exportfloor
################
1) Export Floor
2) Export Floor with building
3) Import Floor
4) Import Floor with bulding
5) Update Building Location
x) Exit
################
Enter Your Selection: 3

Specify the City Name:New York
Specify the Building Name:MainDC
Import to building:MainDC
Specify the Floor Index:1
...
Import floor end.

 

8. Repeat steps 7 and 8 until all floors have been imported.

 

IMPORTANT NOTE: Basement and Floor 1 might overlap if there is no ground defined.
To fix this, open location studio from the 3D client and double click on the “ground floor” of your building. This is the flat surface separating the basement from ground floor.

Give it a name, upload an image for it and define a default floor.

This should define a ground separator between the basement and the F1.

 

 

 

 

 

 

Migration of the assets

 

This step consist on exporting of all the devices and relationships from the source server and import them on the target server.

The migration of the building/floor must be completed before doing this step.

 

1. Decide which assets are to be migrated from source to target server.

2. Export them all using the standard excel spreadsheet export.

3. Follow the best practices described in CA Visual Infrastructure - Best practices to model a datacenter using spreadsheet import  to import the assets into the target server.

Attachments

    Outcomes