Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Mobile Admin > Mobile Admin - Knowledgebase Articles > Back up and restore the Mobile Admin database

Back up and restore the Mobile Admin database

Updated May 8, 2017

Overview

This article describes how to back up and restore the Mobile Admin database.

Environment

All Mobile Admin versions

Steps

Back up a Rove IT database

  1. Go to Start > All Programs > Control Panel > Administrative Tools > Services and stop all Mobile Admin services.
  2. Make a copy of the database file C:\Program File\Rove\Mobile Admin\db\MobileAdminDB.sqlite.
    1. Uninstall Rove IT Mobile Admin from Add/Remove Program (uninstall all the Settings if asked during the Uninstall Wizard).
    2. Rename the following folder from C:\Program File\Rove\ to C:\Program File\Rove.old.

Back up a SolarWinds Mobile Admin database

  1. Go to Start > All Programs > Control Panel > Administrative Tools > Services and stop all Mobile Admin services.
  2. Make a copy of database file C:\Program File\SolarWinds\Mobile Admin\db\MobileAdminDB.sqlite.

Restore a SolarWinds Mobile Admin database

  1. Go to Start > All Programs > Control Panel > Administrative Tools > Services and stop all Mobile Admin services.
  2. Move the database backup file to the following folder C:\Program File\SolarWinds\Mobile Admin\db\MobileAdminDB.sqlite.
  3. Restart the services or restart the server.
Last modified

Tags

Classifications

Public