Hi Marilou,
in case of new installation of 7.6 release on a new hardware with new database creation, it will requires all necessary data migration from existing 7.6 environment to a new 7.6 environment, using different methods, such as stand-alone replications or export/import, DS drivers adding and re-creation of WinPE, NS and Site Servers settings chaging, migration of packages using "SWD replicator" tool and physical packages migration using "Migration Wizard"
Asset Management Solution data with their associations should be also migrated but there were problems that Data Connector wasn't able to do this - You can check this discussion about similar case: https://www-secure.symantec.com/connect/forums/partial-migrate-data-old-ns-new . And stand-alone replication rule will not be able to replicate asset data, since asset resources aren't replicable.
******************************************************************************************
Seems like a better way will be to just take backup of currently running "Symantec_CMDB" database from both 7.6 servers and use them for a new 7.6 installation on a new hardware, to avoid manual migration of asset management data as well as for software packages, reports, tasks, etc.
1. Take "Symantec_CMDB" databases backup from current SQL Servers - 7.6 environment and download these backups on a new SQL Server(s) - Hardware
This KB has information about "Symantec_CMDB" database backup/restore from SQL Server to SQL Server
Notes:
- Make sure that a new SQL Server has supported version for 7.6 release and it's version isn't lower than SQL Server where you took "Symantec_CMDB" database backup.
- Make sure that a new SQL Server has same SQL Collation as previous SQL Server where you took "Symantec_CMDB" database backup, otherwise if SQL Collation is different between new SQL Server and database backup, then you will not be able to use it for 7.6 installation.
2. Install "Symantec Installation Manager" on new NS - hardware and choose 7.6 release for installation.
- On step of "Install Readiness Check" you will MigrationPackage (If you don't have it, then please ask tech support to provide it for you)
- On step where to specify SQL Server and database name, choose your new SQL Server instance where you've restored "Symantec_CMDB" database backup and choose "Use existing Database" ⇒ start 7.6 installation.
Once 7.6 will be installed/configured on new NS hardware and using existing "Symantec_CMDB" database 7.6 on a new SQL Server hardware, then install required 7.6 Hot Fix.
3. Now you will have all same data available with their asset associations, etc on a new hardware. Just don't forget to configure/modify other things, like:
- Pay attention that now on new 7.6 NS you have "old" Package Server(s) and Task Server(s) which are connected and working with an old 7.6 NS! So you have to remove unnecessary Site Server(s) from new 7.6 NS and install a new Package Server(s) and Task Server(s) which will be working with a new 7.6 NS and will serve managed client computers. Otherwise, if you will have "non-existing" Site Server(s) available on Site Server Management page of new 7.6 NS, then other new Site Servers and managed clients will try to communicate with them with no success.
- Once you have new Package Server(s) installed for new 7.6 NS, you have to copy all physical packages/images from previous 7.6 NS to a new 7.6 NS environment (You can use "Migration Wizard" to get all physical packages from "Software Management Solution" and "Patch Management Solution" and export them into a "Store.adb" file, which can be delivered to a new 7.6 NS and imported there). Make sure that when all physical packages are downloaded on a new 7.6 NS, you have run "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" and "NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}" scheduled tasks to update their information in database.
- Review and modify "Site Server(s)" and their settings, because in a new location you have different subnets, etc so otherwise setup required Site Services to manage/serve client computers from a new 7.6 environment. Don't forget that if you will don't remove Site Servers
- Check that your NS settings, such as proxy, mail smtp, etc are correct.
Note:
Check that you have correct "Communication Profile" specified in "Agent install" page! If there is a "Communication Profile" of previous 7.6 NS, then change it to a new profile of a new 7.6 NS, otherwise all push installation of SMA will redirect clients to an old NS 7.6 server.
4. For existing managed client computers redirection, you can export "Communication Profile" of new 7.6 NS and import it on old 7.6 NS machine, then create separate "Targeted Agent Settings" and choose there a new 7.6 NS communication profile ⇒ once managed clients will receive new settings, they will try to connect and register with a new 7.6 NS machine.
Thanks,
IP.