Skip to end of metadata
Go to start of metadata

Backups

Information

For automation (and backup scripts), please refer to automated backups

If backing up immediately prior to an upgrade, lock the endpoints.  Select all Clients and choose 'Lock'.  If you already have locked clients that need to remain this way after migrating or upgrading, consider making an Inventory Query based upon FileWave Client Name and FileWave Client Locked, to obtain a list of already locked clients.



For general backups, locking the Clients is not necessary, however an alternate or external drive should be considered for either direct backups or copying backups

Download and run the backup script from the above link(requires admin rights):

macOS and Linux:

/[path to script]/backup_server.sh   run  "/Volumes/backupFolder" manual

Windows:

/[path to script]\backup.bat "D:\backupFolder" now


Restore a Backup

Copy Backup

Lock all Clients and stop the server (All commands require Admin rights).

fwcontrol server stop

Unzip the chosen backup.

Three folders may exist in the backups:

  • certs
  • ipa
  • media

For any of these folders that exist in the backups folder, rename the equivalent in:

macOS and Linux:

/usr/local/filewave

Windows:

C:\ProgramData\FileWave\FWServer\


Once renamed, copy these folders from the backup to the this location.

Rename the /fwxserver/Data Folder and copy the backup 'Data Folder' to:

macOS and Linux:

/usr/local/filewave/fwxserver/

Windows:

C:\Program Data\FileWave\FWServer\


Rename the passwords file in the below path and copy the backup passwords file to:

macOS and Linux:

/usr/local/filewave/apache/passwd/

Windows:

C:\Program Files (x86)\FileWave\apache\passwd\


Rename the .conf files in the below path and copy the backup .conf files to:

macOS and Linux:

/usr/local/filewave/apache/conf/

Windows:

C:\Program Files (x86)\FileWave\apache\conf\


Pre version 11: 

Rename the .sqlite files in the below path and copy the backup .sqlite files to:

macOS and Linux:

/fwxserver/DB/

Windows:

C:\Program Data\FileWave\FWServer\DB


Start postgreSQL.

fwcontrol postgres start


PostgreSQL Restore

Remove the current MDM database, create a fresh empty MDM database and restore:

macOS and Linux:

/usr/local/filewave/postgresql/bin/psql -U postgres -d postgres -c 'drop database mdm;'
/usr/local/filewave/postgresql/bin/psql -U postgres -d postgres -c "create database mdm template=template0 encoding='utf8';"
/usr/local/filewave/postgresql/bin/psql -U django -d mdm -f /[unzipped backup path]/DB/mdm-dump.sql

Windows:

> C:\"program files (x86)"\FileWave\postgresql\bin\psql.exe -d postgres -c 'drop database mdm;'
> C:\"program files (x86)"\FileWave\postgresql\bin\psql.exe -d postgres -c "create database mdm template=template0 encoding='utf8';"
> C:\"program files (x86)"\FileWave\postgresql\bin\psql.exe -d mdm -f /[unzipped backup path]/DB/mdm-dump.sql


Start Server

Once completed, ensure ALL copied folders and files have matching owners and groups to the original files.

Start the server.

fwcontrol server start


Log into the Admin console, choose a test computer Client and Unlock this Client.  Confirm the client is responding as expected.

Broaden the test to further Clients, including mobile devices.

Once confirmed, Unlock all Clients.  Once satisfied, remove all renamed files and folders, which are no longer required.


Migration

Information

Considerations before commencing.

Windows Admin

The FileWave installation will have files belonging to the original account that installed the software.  Subsequent upgrades will require the same admin account.  

Consider, therefore, using a local admin account.

DNS

All computers will have their preferences set to communicate either by IP or DNS record of the server.  We strongly recommend that all clients are set to communicate using FQDN.  If agents are not set in this way, migrations may involve having to gain local access to some or all Clients to amend their settings.

All mobile devices will be configured to communicate with the servers FQDN.  Choosing a new alternate DNS name for the server will have a knock-on-effect of losing contact with all mobile devices, requiring all devices to be re-enrolled.


Installation and Backup Copy

Install the same version of FileWave Server software, on the new server to be migrated to as your current server (or download the matching version pre-built VM from the FileWave Downloads page), and copy the zipped backup to this new server.

Ensure this new server version has the latest patches, by running the following command:

/usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc apply_patch


Lock all Clients, create a fresh backup from the current server and stop both servers (All commands require Admin rights).

fwcontrol server stop


Unzip the copied backup on the new server.

Three folders may exist in the backups:

  • certs
  • ipa
  • media

Copy the above backup folders to the destination server, replacing those in the following locations, ensuring ownership and permissions match the original:

macOS and Linux:

/usr/local/filewave

Windows:

C:\ProgramData\FileWave\FWServer\


Copy the backup /fwxserver/Data Folder, replacing the one in:

macOS and Linux:

/usr/local/filewave/fwxserver/

Windows:

C:\Program Data\FileWave\FWServer\


Copy the backup passwords file, replacing the one in:

macOS and Linux:

/usr/local/filewave/apache/passwd

Windows:

C:\Program Files (x86)\FileWave\apache\passwd\


Copy the .conf files replacing the ones in:

macOS and Linux:

/usr/local/filewave/apache/conf

For Windows, only replace the mdm_auth.conf, replacing:

C:\Program Files (x86)\FileWave\apache\conf\mdm_auth.conf


Additionally, copy the following file from the original server to the new server:

/usr/local/etc/fwxcodes


Pre version 11: 


Copy the .sqlite files from the backup DB folder, replace those in:

macOS and Linux:

/fwxserver/DB/

Windows:

C:\Program Data\FileWave\FWServer\DB


Start postgreSQL.

fwcontrol postgres start


PostgreSQL Restore


Remove the current MDM database, create a fresh empty MDM database and restore:

macOS and Linux:

/usr/local/filewave/postgresql/bin/psql -U postgres -d postgres -c 'drop database mdm;'
/usr/local/filewave/postgresql/bin/psql -U postgres -d postgres -c "create database mdm template=template0 encoding='utf8';"
/usr/local/filewave/postgresql/bin/psql -U django -d mdm -f /[unzipped backup path]/DB/mdm-dump.sql

Windows:

> C:\"program files (x86)"\FileWave\postgresql\bin\psql.exe -d postgres -c 'drop database mdm;'
> C:\"program files (x86)"\FileWave\postgresql\bin\psql.exe -d postgres -c "create database mdm template=template0 encoding='utf8';"
> C:\"program files (x86)"\FileWave\postgresql\bin\psql.exe -d mdm -f /[unzipped backup path]/DB/mdm-dump.sql


Start Server


Once completed, ensure ALL copied folders and files have matching owners and groups to the original files.  On the old, original server, stop the FileWave Server process and change its name and IP:

Stop the old server:

fwcontrol server stop


Edit the hosts file of the new server and add the FQDN of the FileWave server name as an additional entry for the 127.0.0.1 entry.

Rename this server and configure the IP such that the new server takes on the network identity of the old, original server

Start the new server.

fwcontrol server start


Log into the Admin console, choose a test computer Client and Unlock this Client.  Confirm the client is responding as expected.

Test any further Clients you wish.  Once satisfied, unlock Clients appropriately.


Upgrade

Backup and Lock

Before commencing, follow the backup procedure outlined above, including locking clients.  Once locked, Update Model, stop the FileWave Server Service and then take a VM snapshot.

Installation

Components should be upgraded in the following order:

  • Server
  • Admin console(s)
  • Boosters and IVS if used
  • Clients

All Admin users should be logged out

Server:

Run the FileWave Server installer on the current server, as per the instructions on the download page.

Admin:

Run the FileWave Admin installer on any computer

Run the Admin console.  You may be prompted regarding the updated server fingerprint and also to Update Model

IF THIS FAILS IN ANY WAY, PLEASE CONTACT SUPPORT

Booster:

Run the FileWave Booster installer on any boosters.

Clients:

Choose a test computer Client and Unlock this Client.  Confirm the client is responding as expected, prior to Client upgrade.

To update the Clients will require a Fileset.  Download the matching Fileset from the support site and drag it to the Admin console.  Wait for it to complete uploading (it will remain bright red until complete).  Uploads can be monitored at the bottom of the Admin console window:


Associate the Fileset to your test Computer and again confirm the agent is responding as expected after it has updated.

Test any further Clients you wish.  Once satisfied, Unlock all Clients.

Upgrade any other Admin consoles.