Changeset 3713
- Timestamp:
- Sep 7, 2007, 11:23:47 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2.4-stable/doc/src/docbook/admindoc/installation_upgrade.xml
r3689 r3713 48 48 <para> 49 49 The first time installation is only to be performed once, 50 optionally followed by a migration. The migration can only be 51 done to a pristine (empty) BASE 2 server, and migration from 52 several BASE 1 installations to one BASE 2 server is not 53 supported. 50 optionally followed by a migration. The migration can only be done 51 to a pristine (empty) BASE 2 server with one exception; The 52 migration can be restarted if it fails during the RawBioAssaysData 53 transfer, for all other failure points the migration has to be 54 restarted with an empty database. Migration from several BASE 1 55 installations to one BASE 2 server is not supported. 54 56 </para> 55 57 … … 1008 1010 <xref linkend="user_administration"/>. 1009 1011 </para> 1012 <para> 1013 If you are planning to perform a migration of data from 1014 BASE 1.2.x please perform the steps in 1015 <xref linkend="installation_upgrade.migration"/> before 1016 doing anything else with your new BASE installation. 1017 </para> 1010 1018 </listitem> 1011 1019 </varlistentry> … … 1059 1067 1060 1068 <para> 1061 There is currently no way to restart a migration. The behaviour 1062 of migration is controlled 1063 through <filename>migration.properties</filename> file (see <xref linkend="appendix.migrate.properties"/>), but you 1064 should know what you do when you change parameters in this file. 1069 The behaviour of migration is controlled 1070 through <filename>migration.properties</filename> file (see 1071 <xref linkend="appendix.migrate.properties"/>), but you should 1072 know what you do when you change parameters in this file. 1073 </para> 1074 1075 <para> 1076 Migration can be restarted in one specific case only; If the 1077 migration fails during the RawBioAssaysData transfer simply 1078 restart the migration and the script will ask you to verify that 1079 a restart should be attempted. For all other failure points the 1080 migration has to be restarted with an empty database. 1065 1081 </para> 1066 1082 … … 1138 1154 ./migrate_from_1.2.sh</programlisting> 1139 1155 </para> 1156 <para> 1157 If the migration fails during the RawBioAssaysData 1158 transfer you can restart the migration at the point of 1159 failure. Simply restart the migration and the script will 1160 ask you to verify that a restart should be attempted. For 1161 all other failure points the migration has to be restarted 1162 with an empty database. 1163 </para> 1140 1164 </listitem> 1141 1165
Note: See TracChangeset
for help on using the changeset viewer.