SAM migration question (new server)

gregatkins

I'd like to start with a fresh SAM database, using a seed file to import the list of nodes (we have about 800).  The only downside is that most of the nodes are named using all lower case plus have the domain tagged onto the end of the name. We have our current SAM setup with uppercase node names (for easy reading), and we get rid of the domain tag on the name.

I've created a new database and the import went fine, but I'm wondering if there is a way to change all the nodes to uppercase to keep the same naming convention.  From what I've seen, the seed file only allows you to import IP address, it doesn't import the node names, locations, zones, etc.   I want to avoid messing with SQL tables .  It looks like we would have to go node by node to change the names with the correct floor, location, zone, etc.

I haven't looked into exporting all maps from Network Atlas and reassociating them with the nodes in the current database.

I'm looking for ideas on the best way to go about this process.   We'd like to start with a fresh database and not creating a massive workload for ourselves

aLTeReGo

Probably the simplest and easiest way would have been to copy the original database and either truncate unnecessary tables or delete everything you didn't want carried over. Unfortunately there are no provisions for changing case or pre-populating  node names. The easiest way to handle this would be directly though the database. If you're not comfortable using the SQL Management Studio you can always use Microsoft Access. Just ensure that all Orion services are stopped before making changes to the database.

You can always export and re-import your custom properties using the Custom Property editor, however importing your Network Atlas maps will require you to manually re-associate the nodes and interfaces, etc. on the maps since these are tied to NodeID and not IP address or hostname.