# Linux operator guide ## Startup / Shutdown console ##### Start Soffid IAM console ```shell systemctl start soffid-iamconsole.service ``` ##### Stop Soffid IAM console ``` systemctl stop soffid-iamconsole.service ``` ##### Status ```shell systemctl status soffid-iamconsole.service ``` ##### Logs You can find the console logs at: /opt/soffid/iam-console-3/logs ## Startup / Shutdown Synchronization servers ##### Start Sync server ```Powershell systemctl start soffid-iamsync.service ``` ##### Start Sync server ```Powershell systemctl stop soffid-iamsync.service ``` ##### Status ```Powershell systemctl status soffid-iamsync.service ``` ##### Logs You can find the console logs at: /opt/soffid/iam-sync/logs ## System backup Soffid relies on a database to store almost every identity data. So, the first step to perform a daily database backup. - For Maria DB, look at: [Backup and restore overview](https://mariadb.com/kb/en/backup-and-restore-overview/) - For Oracle, look at: [Backing Up The Database](http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV8003) - For SQL Server, look at: [Create a Full Database Backup (SQL Server)](http://msdn.microsoft.com/en-US/en-en/library/ms187510.aspx) Soffid console installation directory should be backed up after every installation or upgrade. Once the upgrade or installation has been done, only the log directory needs to be backed up. Soffid synchronization servers configuration directory (conf) should be backed up just after configuration. In case of system failure, a new synchronization server should be installed and the conf directory can be restored onto it. The conf directory should be backed up on a different media than the database, due to conf directory contains the private keys that can decrypt the data stored in the database.