Providing Cryptshare database backup to Cryptshare Support
Applies to:
Cryptshare Server version 3.12 and higher
Purpose:
This article describes how to create a Cryptshare database backup and provide it to Cryptshare Support via Cryptshare.
Solution:
Proceed as follows to create a database backup:
1. Login to the administrator interface of your Cryptshare server
2. Navigate to the tab Backup/Restore → Backup and select the item Backup Database
3. Back up the database as shown in the picture

4. Go to Restore tab and download the current backup

5. Since the backup contains confidential information, please set a password and provide both to support@pointsharp.com via Cryptshare with the ticket id in the subject.
Related Articles
Activate Backup Rotation on Cryptshare Appliances under openSUSE
Inhaltsverzeichnis 1 Applies to: 2 Symptom: 3 Cause: 4 Solution: Applies to: Cryptshare Appliance from 3.12 Symptom: Automatic backups are not deleted and fill the partition. Cause: With version 3.12 of Cryptshare Server a new cleanup mechanism for ...
Restoring distribution upgrade backup
Inhaltsverzeichnis 1 Applies to: 2 Symptom: 3 Cause: 4 Solution: Applies to: All versions of Cryptshare Appliance Symptom: If the Cryptshare Appliance does not respond after upgrading your system or not automatically loads its service after reboot, ...
Migrating Cryptshare
Applies to: All versions of Cryptshare Server Purpose: This article guides you through a Cryptshare Server migration. Solution: Be sure that your Cryptshare Server is running at least version 4.3.0 before proceeding. If not, please update as ...
Updating Cryptshare manually
Applies to: Cryptshare Server from version 4.2.x Purpose: This is an example of the possibilities for updating Cryptshare manually. Note that manual updates should only be done if a regular update is not possible! Please make sure you have a working ...
Restart the Cryptshare service during update process
Applies To All versions of the Cryptshare Server Problem During the Cryptshare update it is unclear whether the update process is still running. Cause This can happen if the database is large and the update process makes changes to the database after ...