Actions

Backup entire database: Difference between revisions

From LimeSurvey Manual

mNo edit summary
mNo edit summary
Line 1: Line 1:
<languages />
<languages />
<translate>
<translate>
 
<!--T:1-->
=General=  
=General=  


Line 8: Line 8:
<center>[[File:Backup entire database configuration.png]]</center>
<center>[[File:Backup entire database configuration.png]]</center>


<!--T:2-->
After you clicked on it, a window will pop up, asking you where you would like to save the .sql database backup.
After you clicked on it, a window will pop up, asking you where you would like to save the .sql database backup.


<!--T:3-->
For more about its usage, read our wikis on:
For more about its usage, read our wikis on:
* [[Installation#Transferring an installation|how to transfer an LimeSurvey installation]];
* [[Installation#Transferring an installation|how to transfer an LimeSurvey installation]];
* [[Installation#Upgrading from a previous version|how to upgrade an LimeSurvey installation]] (non-ComfortUpdate solution).
* [[Installation#Upgrading from a previous version|how to upgrade an LimeSurvey installation]] (non-ComfortUpdate solution).


<!--T:4-->
This option is also used when changes on different settings (e.g. in the code) are done. You secure in this way your data in the case in which the installation breaks up.
This option is also used when changes on different settings (e.g. in the code) are done. You secure in this way your data in the case in which the installation breaks up.


</translate>
</translate>

Revision as of 14:10, 8 September 2017

General

If you would like to update your installation or transfer it to another location/server, we highly recommend you to back up all your data (questions, participants, responses, etc.). You can use the Backup entire database function in this scope.

After you clicked on it, a window will pop up, asking you where you would like to save the .sql database backup.

For more about its usage, read our wikis on:

This option is also used when changes on different settings (e.g. in the code) are done. You secure in this way your data in the case in which the installation breaks up.