From time to time, customers may need to restore their system from a backup. This could be due to problems encountered while upgrading, or if their system has gotten itself into a corrupt state. For the purposes of this article, installer version 3.4.0 will be used as an example throughout.
Note: you can only restore to the version that you were on already.
IMPORTANT NOTE: please ensure to shut down Analyze fully before attempting an installation or restore. Steps on how to do so can be found here
Failed Upgrade: In the event of a failed upgrade, you'll need to restore your previous version (the one you were upgrading from) before upgrading. You will need the installer of your previous version before undertaking the steps in this article.
Corrupt System: In the event that your system has become corrupt, you'll need the installer for the same version you are on.
Note for Server Users:
>> If possible, go through and delete any old schedules before completing the steps below
>> Select each dataflow and choose "Delete Run Data". Don't do this for runs you need, but if you have older dataflows, it will help reduce the size of the backup if you purge the temp files
STEPS TO RESTORE:
1. Go into the data directory…Data3SixtyAnalyze\data-7731 and take a copy of the recent complete backup that you wish to use for the restore. It will have a .lxp extension. All the backups should be roughly the same size. If one is significantly smaller than it should not be used, as it may be incomplete
2. Move these folders to some other folder (don’t copy and paste):
- <dataDirectory>data-7731 - this folder contains the securityStore.jks file which will be needed later
- <dataDirectory>site-7731 -any added any custom JAR files are kept here, along with your cust.prop and license file
3. Uninstall the application, ensuring all traces of it are removed from your computer. The uninstaller is located in the <installDirectory>
4. Locate the 3.4.0 D360 Analyze installer, right click on it and select Run as Administrator. This will kick off a series of windows which are outlined below
THE INSTALLER WINDOWS:
- License Agreement: Accept the license agreement and click ” Next”
- Data3Sixty Analyze Usage Policy – click “Next”
- Restore from a backup – check the box, and select the .lxp file that you chose in the first step. The window should look like this:
- Select the folder where you would like Analyze to be installed: select a folder and click Next
- Provide the directory location where Analyze configuration files will be installed – input the locations of your choosing, and click Next
- Select the Analyze server port - enter your port and click Next
- License Window - enter your license file and click Next
- Enter the HTTP Start & Stop ports - enter them and click Next
- Security Store password - when the installer asks for the security store password ensure it's the same as the previous one used.
- enter the password and confirm it
- select to store password
- click Next
- The database port – enter it and click Next
- Create a start menu - check the box and click Next
Version 3.4.0 should now be restored. We recommend you open the application and ensure that it works. If it does not, please raise a Support ticket.
NEXT STEPS - PREPARATION FOR UPGRADE
PRE UPGRADE: In the event of a failed upgrade, we recommend you follow these steps before attempting to upgrade again.
- keep a copy of the .lxp from 3.4.0 somewhere safe
- Open Services (Task Manager > Services tab) and scroll down to the Data360 Analyze Services. There are three in total
- On each Data360 Analyze Service, right click and select "properties". The below window should appear
- Under the General tab, change the "Startup type" from 'Automatic' to 'Manual' and hit "Stop" (this needs to be done for all three services individually)
- Ensure the three Services are no longer running
- Reboot your computer
Once these steps are complete, the upgrade can be attempted again.
POST UPGRADE: Before starting the three Services -
- change the Startup type back to Automatic in Services
- inspect your cust.prop file to ensure that any paths are suitable for the new installation (located at site/conf/cust.prop)
- restart the Services