Applies to:
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 described here: Updates
The following guide will take you step by step to the new Appliance recommended and tested by our Support staff and customers.
Collect (or better check for completeness) the data for the new appliance
Create the new Appliance
Create the new Appliance for vSphere or download one for the Hyper-V in our VM Build Service: Cryptshare Buildservice
Import the delivered Appliance
Install it parallel to your old server in your DMZ
Prepare the Appliance in your Hypervisor (VMware or HyperV)
Check the Virtual Hardware
Refer to the System Requirements.
Add an additional Virtual Disk
Cryptshare uses different storage locations to save
- Temporary files
Temporary files are created during the upload, virus check, encryption process or any other pre-processing tasks. - The transfer payload
The folder where the payload of the system is stored, i.e. the encrypted files and messages that are being transferred from A to B reside in this folder until they are automatically deleted at the end of the retention time. - Backups
The folder into which you can back up your system configuration, transfer meta data and the transfer data itself.
These storage locations should be sized according to your requirements and have to be configured in the Cryptshare Server.
Now add the additional virtual disk with the preferred size to the appliance using the instruction Extending available disk space
To configure the Temp directory refer to System Startup Settings - Temporary Folder
enlarge an existing disk
Please follow this guide to enlarge the harddisk if nessecary:
Next steps with the new Server
- Start the Server
login via PuTTY as root and proceed with this commands:
1. deactivate the Cryptshare servicerccryptshare stop
2. Set the TEMP Folder to the new diskecho "" >> /opt/cryptshare-3/launcher.ini echo "vm.arg.1=-Djava.io.tmpdir=/var/opt/cryptshare-3/tmp" >> /opt/cryptshare-3/launcher.ini
Proceed at the old Cryptshare Server
- create a Backup of the database at the old system with the Name: cs3-MovingBackup
login via PuTTY as root and proceed with this commands:
deactivate the Cryptshare servicerccryptshare stop
Now start the Copyjobs to copy the data from the old Cryptshare Server to the new one
scp /opt/cryptshare-3/upload (or your actually used path)/* root@CRYPTSHARE_NEW:/var/opt/cryptshare-3/uploads
scp /opt/cryptshare-3/backup (or your actually used path)/cs3-MovingBackup.zip root@CRYPTSHARE_NEW:/opt/cryptshare-3/backup
scp /opt/cryptshare-3/lib/security/keystore root@CRYPTSHARE_NEW:/opt/cryptshare-3/lib/security/
scp -r /opt/cryptshare-3/resources/ui root@CRYPTSHARE_NEW:/opt/cryptshare-3/resources
Finishing steps to activate the new Server
login via PuTTY as root and proceed with this commands:
activate the new Cryptshare Serverrccryptshare start
Log in the Administrative Interface and restore the DB-Backup cs3-MovingBackup
Please note! Using this way the database can be restored if one of the following Cryptshare versions is installed on old server:
4.3.0If different versions are used, the web interface will be no more available after the restore.
Attention! Please restore the database only! Do not restore the system data and/or transfers in this way!
Restore database from version 4.2.x
Please use the following steps, to restore the database from Cryptshare 4.2.x
- unpack the backup from the old server into the folder /root/tmp
unzip /opt/cryptshare-3/backup/cs3-MovingBackup.zip -d /root/tmp- change into new directory
cd /root/tmp/cs3-MovingBackup- unpack the database
unzip database/db-cs3-Moving.zip -d cryptshare- stop the Cryptshare service
systemctl stop cryptshare.service- replace the database folder
mv cryptshare /opt/cryptshare-3/orientDB/databases/cryptshare- start the Cryptshare service
systemctl start cryptshare.service- Make sure that all path names in the Administration Interface match the actual file locations:
- Uploads: Check System Settings > Transfer Settings
- Backups: Check Restore/Backup
- Temp: Check System Status > Scroll down and click on Java Runtime Environment
- Disk Space Monitoring: System Settings > System Notifications > Check if all monitored paths are valid
- change the firewall and DNS-Settings (switch to the new IP-address)