Actions

Transferring an installation/sl: Difference between revisions

From LimeSurvey Manual

(Created page with "Morda niste imeli prave namestitve za izdelavo varnostne kopije, ki bi se ujemala z arhivirano SQL podatkovno zbirko? Čisto možno je, da so se ti ločeni arhivi zamešali al...")
(Updating to match new version of source page)
Line 2: Line 2:
__TOC__
__TOC__


Morda je vaša naloga premik vaše namestitve na nov strežnik. Opravilo bi moralo biti enostavno, vendar se lahko zaplete zaradi drugih dejavnikov. Na tej strani je opisan prenos, na kaj morate biti pozorni in kako izvesti obnovo, če naletite na težavo.
You might get the task of moving the LimeSurvey installation to a new server. The process should be simple, but it can get complicated by other factors. You may find below information on how to do the transfer and what to look out for, and information on how to recover from if you encounter a problem.


V splošnem so edine razlike v primerjavi z novo namestitvijo sledeče:
In general, the only changes from a new and clean installation are the following:
# '''config.php''' se običajno spremeni za shranjevanje osnovnih parametrov za namestitev, kot tudi vse po meri narejene nastavitve
# '''config.php''' is usually changed to store basic installation parameters as well as any custom settings made;
# '''upload/*''' lahko vsebuje običajne predloge ali naložene datoteke
# '''upload/*''' may contain custom templates or uploaded files;
# '''SQL database tables''' bi moral imeti podatke o dodanih tablah, ustvarjenih v času namestitve. Upoštevajte tudi, da so morda bile ustvarjene nekatere nove tabele za shranjevanje kopij žetonov in rezultatov iz preteklih ali trenutno aktivnih anket. Te nove tabele so običajno poimenovane '''lime_survey_nnn...''', '''lime_tokens_nnn...''', lime_oldsurvey_nnn...''' in lime_oldtokens_nnn...'''.
# '''SQL database tables''' should have had data added to the tables created at installation time. Note also that some new tables may have been created to save copies of token and result data from previously or currently active surveys. These new tables are usually named '''lime_survey_nnn...''', '''lime_tokens_nnn...''', '''lime_oldsurvey_nnn...''', and '''lime_oldtokens_nnn...'''.


To so načeloma vse razlike, razen če ste delali še kakšne dodatke za prilagoditev same kode.
Otherwise, unless you went in and made custom patches to the code, changes should be limited to these areas.


Cilj pri prenosu namestitve na nov strežnik je podoben nadgrajevanju. Največja razlika je, da poskušamo zgolj obnoviti obstoječo namestitev na novem računalniku. Če želite obenem še[[Upgrading from a previous version/sl|nadgraditi na novo različico]], naredite to kasneje kot naslednji korak potem, ko ste uspešno prenesli namestitev in preverili, da deluje.
The goal in transferring an installation over to a new system is similar to upgrading. The biggest difference is that we simply try to recreate the existing installation on the new computer. If you wish to [[Upgrading from a previous version|upgrade to a newer version]] also, do this as a later, second step once you have transferred the installation and verified that it works.


=Prenos poljubne različice=
=Prenos poljubne različice=
Line 31: Line 31:
# Končali ste!
# Končali ste!


Če želite nadgraditi na istem strežniku, lahko greste zdaj skozi enak postopek, kot je bil opisan že prej na povezavi [[Upgrading from a previous version/sl|nadgrajevanje na novejšo različico]].
If you wish to upgrade on this machine, you can now go through the same process described in the section related to the [[Upgrading from a previous version|LimeSurvey upgrade to a newer version]].


=Stvari, ki se lahko zalomijo=
=Stvari, ki se lahko zalomijo=


Če prav je nadvse enostavno, se lahko stvari tudi zalomijo. Najprej globoko vdihnite. Nato preverite, če ste sledili vsem korakom. Če še vedno ne odkrijete težave, berite naprej če je mogoče že kdo obvisel pri isti težavi in jo uspešno rešil.
As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed thoroughly the steps. Otherwise, read below to see where other people got hung up along the way.


==Različna namestitev PHP-ja na posameznem strežniku==
==Različna namestitev PHP-ja na posameznem strežniku==
Line 43: Line 43:
==Različna različica LimeSurvey-a (nameščene in varnostne kopije podatkovne baze se ne ujemajo)==
==Različna različica LimeSurvey-a (nameščene in varnostne kopije podatkovne baze se ne ujemajo)==


Morda niste imeli prave namestitve za izdelavo varnostne kopije, ki bi se ujemala z arhivirano SQL podatkovno zbirko? Čisto možno je, da so se ti ločeni arhivi zamešali ali kakorkoli drugače ločili. Na voljo je nekaj stvari, ki vam lahko pomagajo pri ugotavljanju različic posameznega arhiva. Kadar uporabljate '''LimeSurvey-evo''' možnost za pripravo varnostnih kopij SQL podatkovnih zbirk, ima privzeto ustvarjeno ime arhivirane datoteke na koncu datum v imenu. Prav tako, če pobrskate znotraj arhivirane datoteke z SQL podatkovno zbirko, se mora tam nahajati razdelek, ki zgleda podobno kot je prikazano spodaj in kjer je shranjena različica podatkovne zbirke. To vrednost  uporablja namestitveni program na primer, da ugotovi kako uveljavljati spremembe v tabelah pri nadgradnjah.
There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the '''LimeSurvey''' SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:




Line 52: Line 52:
INSERT INTO lime_settings_global VALUES("DBVersion","126");
INSERT INTO lime_settings_global VALUES("DBVersion","126");
....</syntaxhighlight>
....</syntaxhighlight>
'''This value is used by the installer to determine how to apply changes to tables when upgrading.'''

Revision as of 12:25, 7 August 2017

You might get the task of moving the LimeSurvey installation to a new server. The process should be simple, but it can get complicated by other factors. You may find below information on how to do the transfer and what to look out for, and information on how to recover from if you encounter a problem.

In general, the only changes from a new and clean installation are the following:

  1. config.php is usually changed to store basic installation parameters as well as any custom settings made;
  2. upload/* may contain custom templates or uploaded files;
  3. SQL database tables should have had data added to the tables created at installation time. Note also that some new tables may have been created to save copies of token and result data from previously or currently active surveys. These new tables are usually named lime_survey_nnn..., lime_tokens_nnn..., lime_oldsurvey_nnn..., and lime_oldtokens_nnn....

Otherwise, unless you went in and made custom patches to the code, changes should be limited to these areas.

The goal in transferring an installation over to a new system is similar to upgrading. The biggest difference is that we simply try to recreate the existing installation on the new computer. If you wish to upgrade to a newer version also, do this as a later, second step once you have transferred the installation and verified that it works.

Prenos poljubne različice

  1. Pripravi in ustvari kopije trenutne namestitve
    1. Ustvari kopije map, datotek in SQL podatkovne zbirke.
      1. V ukaznem oknu ustvarite .zip ali podoben arhiv celotne namestitve (datotek in mapne strukture).
      2. Z uporabo phpMyAdmin ali podobnega orodja izvozite vse tabele; ali uporabite ustrezen gumb za LimeSurvey-eve skrbnike za izdelavo kopije celotne podatkovne zbirke
    2. Posebej kopirajte vašo datoteko config.php za lažji dostop in urejanje datoteke
  2. Kopirajte shranjeno izdajo na nov server
    1. Razpakirajte vaše namestitvene datoteke
      1. Ustvarite vašo novo namestiveno mapo (najboj primerna je izbira istega imena)
      2. Razpakirajte (unzip) namestitvene datoteke v mapo, kamor se bile shranjene pred tem
    2. Namestite svojo SQL zbirko podatkov
      1. Ustvarite nove zbirko podatkov z uporabo phpMyAdmin ali ukaznega vmesnika
      2. Naložite shranjeno SQL bazo podatkov, da boste ponovno izdelali tabele in vsebino
  3. Uredite datoteko config.php, da bo odražala spremembe glede na staro verzijo in preverite vašo namestitev
    1. Bodite pozorni, da boste preverili ime podatkovne zbirke, uporabniško ime ni geslo, kot tudi ime nameščenega serverja, URL pot, in fizično pot do nameščenih map
    2. Obiščite anketno skrbniško stran ali stran aktivne ankete in preverite, če vse deluje kot mora.
  4. Končali ste!

If you wish to upgrade on this machine, you can now go through the same process described in the section related to the LimeSurvey upgrade to a newer version.

Stvari, ki se lahko zalomijo

As simple as this appears, things do seem to go wrong sometimes. Take a deep breath. Verify that you followed thoroughly the steps. Otherwise, read below to see where other people got hung up along the way.

Različna namestitev PHP-ja na posameznem strežniku

Različna SQL podatkovna zbirka med strežnikoma

Različna različica LimeSurvey-a (nameščene in varnostne kopije podatkovne baze se ne ujemajo)

There is a possibility that you did not have the correct installation backup code to match the backed-up SQL database. It could be easy to get these separate backups confused, out of sync, or otherwise separated. There are a few things that can help you find out what version each backup may be. When using the LimeSurvey SQL backup option, the default file name it creates has the date of the backup in the name. Also, if you search inside the SQL database backup file, you will find a section that looks similar to the example provided below where the database version is stored:


#-----------------------------------------------------------------------
# Table data for lime_settings_global
#-----------------------------------------------------------------------
INSERT INTO lime_settings_global VALUES("DBVersion","126");
....

This value is used by the installer to determine how to apply changes to tables when upgrading.