Page History

...

1. Verify that there is a full backup of the CardioLog database on a separate drive.
2. Stop the CardioLog windows services including CardioLog Diagnostics Service and CardioLog Scheduling Service on the CardioLog application server.
3. Stop IIS on the CardioLog application server to stop data collection and HTTP requests to the CardioLog application during the move.
4. Detach the CardioLog database from the origin server.
5. Copy the database files (data + log) to the destination server.
6. Attach the CardioLog database to the destination server.
7. Edit the following CardioLog registry key accordingly:
• 32-bit machine - HKEY_LOCAL_MACHINE\SOFTWARE\Intlock\CardioLog  
• 64-bit machine - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intlock\CardioLog
  
  "DATABASEINSTANCE"="[database server name]"
  [database server name] - Confirm that the database server name is the server that hosts the CardioLog database.
  
  
8. Edit the database connection string in the following configuration files. The files should be located in the CardioLog Installation Folder. The default path is C:\Program Files\Intlock\CardioLog:
   
   • [CardioLog Installation Folder]\CardioLog\Web.config
   • [CardioLog Installation Folder]\CardioLogAPI\Web.config
   • [CardioLog Installation Folder]\CardioLogMonitoringServices\CardioLog.System.Monitoring.Services.exe.config
   • [CardioLog Installation Folder]\CardioLogScheduleServices\CardioLog.Services.exe.config
   • [CardioLog Installation Folder]\EventCollector\Web.config
   • [CardioLog Installation Folder]\VisitorSegments\Web.config
   • [CardioLog Installation Folder]\ADTree\Web.config
   • [CardioLog Installation Folder]\SP20XXTree\Web.config (Where XX is 07 for MOSS 2007; 10 for SharePoint 2010; 13 for SharePoint 2013, 16 for SharePoint 2016)
   • [CardioLog Installation Folder]\VoiceOfCustomer\Web.config
   • [CardioLog Installation Folder]\Optimization\Web.config
   • [CardioLog Installation Folder]\Redirect\Web.config
   • [CardioLog Installation Folder]\WebsiteTree\Web.config
     
     <add key="connStr" value="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name]" />
     
     [database server name] - Edit the database server name to match the new server that now hosts the CardioLog database.
     
     
9. Edit the database connection string in the configuration file located in the CardioLog Installation Folder. The default path is C:\Program Files\Intlock\CardioLog
   
   
   • [CardioLog Installation Folder]\CardioLog\Web.config
     
     
     <add name="VoiceOfCustomerEntities" connectionString="metadata=res://*;provider=System.Data.SqlClient;provider connection string=&quot;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name];MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" />
     
     <add name="CardioLogEntities" connectionString="metadata=res://*;provider=System.Data.SqlClient;provider connection string=&quot;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name];MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" />

     
     [database server name] - Edit the database server name to match the new server that now hosts the CardioLog database.

10. Restart both CardioLog Windows services, CardioLog Diagnostics Service and CardioLog Scheduling Service, on the CardioLog application server.
11. Start IIS on the CardioLog application server.

...