Navigate
or
Contact Us
Subscribe Download PDF

Cloud On-Premise: How to backup and restore the database

Sicaro Burnett
2025-02-11
in Cloud

This article describes how to create and restore a Wasp OnPremise (AssetCloud OnPrem or InventoryCloud OnPrem) backup with SQL Server Management Studio.  

Follow these steps to move and restore the database to a new server.  

Note: Install  AssetCloud or InventoryCloud On Prem software on new Server prior to performing the steps below.  Ensure you are able to login.  If needed, see the article linked below in Related Pages: Cloud On-Premise installation: Summary & Prerequisites.

 If you do not have SQL Server Management Studio installed you can download the latest version from the link below

https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16#download-ssms

1. Create a backup of the existing database.

  • Log into SQL.  Click on the Windows Logo> Microsoft SQL Server > SQL Server Management Studio.1595970502680.png
  • Login using Windows Authentication1595970572557.png
  • Once in SSMS you will expand Databases.  In there you will see two databases that need to be backed up,  WaspAuth and WaspTrack.  

1596726491070.png

  • Right-click the  database you need to backup and select Tasks, then choose Back Up.

1595970663688.png

  • Next to the lower Destination section of the Back Up Database -  click Remove to remove anything currently shown in the box. 

1595970869401.png

  • Click Add. It will display the folder path for the installation. At the end of the path, add a filename for the backup that will be unique, like ServerMove.bak. Click OK on both windows to create the backup.

1595970921788.png

1595970717080.png

1595970782165.png

1595970995015.png


1595971044304.png

1595971072335.png

 Make note of the Backup location.

  • Transfer the two files to the destination server, via flash drive, network copy, or other method to transfer the backup files to the new server.  On the new server, open Windows Explorer and copy the backup files to C:\Program Files\Microsoft SQL Server\MSSQL14.WASPDATA\MSSQL\Backup.

Note: It is important to copy the files to the Backup folder to ensure they receive the correct permissions so SQL can read them.

1596726730339.png



2. Restore the backup on the new server

  • Log into SQL.  Click on Start > Programs > Microsoft SQL Server > SQL Server Management Studio.

1596036979459.png

  • Login using Windows Authentication

1596037027402.png

  • Expand Databases on the left and right click on WaspAuth > go to Tasks > Restore > Database.. 

1595971507243.png

  • Select the 'From device' option and click on the browse (...) button

1596037134894.png

  •  Click on the 'Add' button 

1596037181078.png

  • This should open up to the correct backup folder containing your database backup and select the file > click on OK > click on OK.

1596037230923.png

1596037259107.png

1596037353609.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. 1596037402759.png
  • Click on 'Options' on the left of the window and check the box that says 'Overwrite the existing database' Note: If Tail-Log backup is checked, uncheck this box

1596732025189.png


  • Finally click on OK at the bottom and the backup should start restoring.
  • After the progress bar on the left reaches 100% the restore should be complete.
  • If your un into a "Database in Use" error message, check "Close Existing Connections to destination database" and click Ok again.

Repeat the restore steps for the WaspTrack database.


3. Fixing the Writer and Reader SQL Users using the Wasp Config Tool

  • After restoring both database backups, open the Wasp Config Tool as Admin and Validate SQL and update the Reader and Writer passwords.
  • If you do not have the shortcut on your desktop for the Wasp Config Tool, it should be located here:
    C:\Program Files\Wasp Barcode Technologies\Wasp On-Premises Software\License\configure\Wasp.Installer.Configure.exe

  • 1682440120047.png
  • Click "Validate Config DB", then in the popup select "Yes"
  • Then use the following to update the writer and reader user passwords
    dbo_Writer      db0-Wr1ter_P455w0rd
    dbo_Reader      db0_Re4der-P455w0rd
  • When you update the passwords, it may give you an error message and ask if you would like to fix it, say "Yes":
    1682440255014.png
  • Keep pressing "Yes" to fix until the results read "updated successfully"
    1682440338485.png
  • Do this for both the reader and the writer. It may be possible that you will see an error message here as many as 4 times. If you get this error more than 5 times, there may be some other issue that requires troubleshooting.
  • Once both return "update successful", save and exit the Wasp Config Tool.


4. Updating the Databases

  • If you're moving from an older version of the applicaiton to a newer version, you can run some commands to update the databases. If the application versions have not changed, this step can be skipped. However, there is also no harm in running this script even if the versions are the same.
  • Open CMD as Amin
    1682440654841.png
  • Then copy/paste the following lines one at a time:
    cd C:\ProgramData\Wasp Barcode Technologies\MobileAssetWeb\Database\Tools\
    Update.op.bat
  • This will run the code to update the databases.
  • Once complete, you can close the command prompt.

5.  Stop and then restart all the services (Bounce)

6.  Attachments are not stored in the database, the knowledge base article below has the steps to move attachemnts

    https://support.waspbarcode.com/kb/articles/cloud-on-premise-attachments-are-no-longer-visible-after-moving-the-database-to-a-new-server


Once the above has been completed, you should be able to successfully navigate to your OP URL and log in.


Related Pages