You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the server deployement tool will always generate new configuration files and populate the database with new entries. This process does not allow someone to save the configuration and database for backup to restore it again in the future.
Ideally there should be a tool to create a backup of all subsystems in the instance which includes:
saving the configuration files
saving the system certificates (and keys if using internal NSS database) into PKCS 12 file
saving the LDAP database, schema, and other configuration into LDIF files
And there should be another tool to restore the backup back into a running server.
Other than backup & restore, this feature can also be used for other purposes:
migrating an instance to a different host
migrating an instance to a newer version (after converting the backup files)
minimizing new replica's initial synchronization time
The text was updated successfully, but these errors were encountered:
This issue was migrated from Pagure Issue #2325. Originally filed by edewata (@edewata) on 2016-05-13 03:15:02:
Currently the server deployement tool will always generate new configuration files and populate the database with new entries. This process does not allow someone to save the configuration and database for backup to restore it again in the future.
Ideally there should be a tool to create a backup of all subsystems in the instance which includes:
And there should be another tool to restore the backup back into a running server.
Other than backup & restore, this feature can also be used for other purposes:
The text was updated successfully, but these errors were encountered: