WARNINGS AND LIMITATIONS

While an import rule can import data from an older Altiris version, 6.0 or 7.0 into 7.1 for example, this is not supported by Symantec Technical Support because the database schemas are different. Attempting this results in a very complicated and problematic process that is not recommended or supported. Likewise, Asset Management and CMDB Solutions do not support stand-alone replication rules, so this cannot be an option either.

Instead, it is recommended to use the Data Migration Wizard to bring any desired inventory data from the old server to the new. If the user needs to have this process on-going, a data migration wouldn't be useful then. The best suggestion is to then create a linked
server object to the old server and then make custom reports to view its data on the new server. This is the only supported way to use the old server's data on the new, other than a data migration using the Data Migration Wizard.

Part 1: Create a Data Source to the old Altiris server
 

1. In the Symantec Management Platform Console, click on the Settings button > All Settings.
2. Click to expand Notification Server > Connector > Data Sources.
3. Right click on the Data Sources folder and choose New > OLEDB Data Source.
4. In the Name field, enter a name for the new Data Source, which is by default "New OLEDB Data Source".
5. In the "OLEDB data source" field, leave the value as "MS SQL Server database".
6. In the "DB Server name" field, enter the name of the old Altiris server's database server.
7. In the "Authentication type" field, leave the value as "Windows Authentication" if the Symantec Management Platform's application ID (system ID) can be used to access the old database server. If not, this may need to be changed to "SQL Server Authentication" and specific credentials supplied to continue.
8. In the "DB name" field, select the database to use.
9. In the "Table name" field, select the table to migrate data from. For example, for Computers, select the Item table. Note: Here is where the first complexity occurs at. The user must know which table to import from. A Data Source cannot point to a database view, which is where many related data classes are found in (such as vComputer), but must go to a single specific table. It's very likely that resource data is desired that is not in this table. If so, the user must then create multiple Data Sources and Import Rules going to each necessary table to bring in all desired data for the resources in question. This may then result in a dozen or more Data Sources and Import Rules just to bring in one resource type, from data classes from CMDB, Core, Inventory Solution, etc.
10. In the "Allow import" checkbox, click to enable this.
11. Click on the "View import data" button. If all of the above instructions are set up correctly, a window will appear displaying the contents of the Item table.
12. Click on the "Save changes" button.

Part 2: Create an Import Rule to migrate data from old Altiris server to Symantec Management Platform 7.1 SP2
 

1. In the Symantec Management Platform Console, click on the Settings button > All Settings.
2. Click to expand Notification Server > Connector > Import/Export Rules.
3. Right click on the Data Sources folder and choose New > Resource Import Export Rule.
4. In the Name field, enter a name for the new Import Rule, which is by default "New Resources Import Rule".
5. In the "Data source" field, select the Data Source from Part 1.
6. In the "Resource type" field, select "Computer".
7. In the "Resource lookup key" field, select "Resource Name".
8. In the "Name" field, select "Name".
9. In the "Data class mappings" section, note that most data classes are not automatically set. This is also true of the "Association mappings" and "Reverse association mappings" sections. The user must manually set which data classes to populate based on what fields are being migrated over from the source database and table, in this case, the Item table. Note: Here is where the second complexity occurs at. The user must know what data classes and associations to correctly map. Also, per Part 1, Step 9, the user may not have available the desired data classes. For example, the Item table does not include the Serial Number data class. This cannot therefore be set by this example Data Source and Import Rule, but would require a second set to do this for.
10. Once all data class mappings, associations and reverse associations have been set by the user, click on the "Save changes" button.
11. Click on the "Test rule" button. Do not run the Import Rule until it has been thoroughly tested. Evaluate what is expected to be imported in. If this does not appear correct, adjustments to Step 9 may need to be performed.
12. Once the test run appears to be what is expected, finally click on the "Run now" button. This will import data into the database and commit it. Note: As it is difficult to remove imported data, the user may wish to fully back up their Symantec_CMDB database prior to beginning data migrations from an old Notification Server.

Summary

• Many Data Connector Data Sources and Import Rules will likely be necessary to import a specific resource type, such as Computers.
• The user must understand how the destination and source databases and data classes work to be able to successfully create their Data Sources and Import Rules.
• If the user cannot use the Migration Wizard, and are having a difficult time in setting up server-to-server Import Rules, they may wish to consider the following workaround. Instead of going server-to-server, it is often easier to export the data from the source server to a .csv or .xls file and then import this into the destination server. This has the benefit of being able to export and import the full resource data needed in a single Data Source and Import/Export rule, whereas doing this server-to-server would require many. This works then as the following example demonstrates:
   
  • The old Altiris server uses its own Export Rule to export Computers and necessary data classes to a .csv file.
  • Symantec Management Platform 7.1 SP2 uses its own Data Source and Import Rule to the .csv file to import its data from.

Related Articles

How to create a Data Connector Import Rule to migrate data from an old Notification Server to Symantec Management Platform 7.x
http://www.symantec.com/business/support/index?page=content&id=HOWTO77183

How to import AddRemoveProgram and InstalledSoftware data using a Data Connector import rule
http://www.symantec.com/business/support/index?page=content&id=HOWTO84052

Data Connector Import Rule fails to create foreign keys or association mappings
http://www.symantec.com/business/support/index?page=content&id=TECH191367

Data Connector Import Rule fails to set a foreign key correctly
http://www.symantec.com/business/support/index?page=content&id=TECH192860