Navigate
or
Contact Us
Subscribe Download PDF

WaspTime: How to backup, move and restore the database and service to a new machine

Max Holden
2023-01-20
in Software

If you need to backup, move and restore the WaspTime database and service to a new machine, do the following:

 

Follow these steps to move and restore the database to a new server.  Be sure to install the program on the new server machine and choose the options to install the Database and Client tools if you are installing Pro or Enterprise.

 

1. Run the installation on the new machine to install the Database, Time Service, and Client. This will set it up with a blank database.

2. Create a backup of the existing database.

  • Click on Start > Programs > Microsoft SQL Server > SQL Server Management Studio.
  • Login with username sa password Wasp$07Wasp$07 hit connect (using SQL Authentication).
  • Expand Databases on the left and right click on WaspTime > go to Tasks > Backup.

wt1.PNG

 

  • Notice the location path and name of the backup file in the lower Destination section of the Back Up Database - WaspTime window.

 

wt2.PNG

 

  • Copy the backup file to C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.WASPDBEXPRESS\MSSQL\Backup on the new server, or the appropriate backup folder if you are using Enterprise and have installed the database to a different SQL instance.

If the machine is running 32 bit version of Windows, it will be C:\Program Files\. If the machine is running SQL 2005 rather than the SQL 2008 installed by the installation of WaspTime 7, it will be MSSQL.1 rather than MSSQL10_50.WASPDBEXPRESS. As long as the backup file is placed into the backup folder in the default SQL path, you will be able to restore it by entering the filename to the restore box.

 

3. Stop the WaspTimeServer Service

  • After ensuring that the backup file was created, go to Control Panel > Administrative Tools > Services. Scroll down to WaspTimeServer, right click and go to Properties. Change the Startup Type to Disabled, then click Stop. Once it is stopped, click OK.

wt8.PNG



4. Restore the backup

  • Restore the backup using SQL Server Management Studio.

 

  • Click on Start > Programs > Microsoft SQL Server > SQL Server Management Studio.
  • Login with username sa password Wasp$07Wasp$07 hit connect (using SQL Authentication).
  • Expand Databases on the left and right click on WaspTime > go to Tasks > Restore > Database.. 
  • Select the 'From device' option and click on the browse (...) button > click on the 'Add' button > change the 'Files of type' drop down to All Files.
  • Navigate to the folder containing your database backup and select the file > click on OK > click on OK.

 

 wt4.PNG

 

  • In the lower 'Select the backup sets to restore' section of the Restore Database window, check the box next to the database set displayed.

 

wt5.PNG

 

  • Click on 'Options' on the left of the window and check the box that says 'Overwrite the existing database'

 

wt7.PNG

  • Finally click on OK at the bottom and the backup should start restoring.

 

wt6.PNG

  • After the Restore completes, you will need to execute the script C:\Program Files (x86)\Wasp Technologies\WaspTime\Database\FixUpRestoredUsers.sql

Prior to running the client, open the Services list and make sure WaspTimeServer shows startus Started.

When opening the client program on any other client machines, they will attempt to poll your network to find the location of the new WaspTimeServer service when they first run and are unable to connect to the old server. If the polling is successful, the program will open without further prompt. 

If the polling returns multiple results, you will be prompted for which server to connect with. If it fails to connect to any new server, you will receive a message giving possible reasons it failed to connect, and the option to edit the service settings. If you manually enter the new server name and it still fails to connect, you will need to ensure that the WaspTimeServer service is still Started on the new server and you have the correct server name, and if there is a firewall running on the new server, try disabling it.