История страницы

Во время процесса обновления, описанного ниже, данные настроек Архива будут сохранены (если не указано обратное). Но не смотря на это, бывают случаи, когда настройки терялись из-за проблем с блокировкой и тому подобных. Поэтому всегда приветствуется делать вручную бэкап настроек сервера (большей частью хранящихся в файле server.conf) перед тем, как приступать к обновлению системы. 

The directory locations for Архива's program files, configuration files, program data and logs have changed since previous versions. Please familiarize yourself with File System Layout.

Available Upgrade Paths

Standard Version 3.x Upgrade Path

...

Older Version Upgrade Paths

• From Архива V2 / Архива Open Source Edition to Архива V3
• From Open Source Edition to Newer Version Open Source Edition
• From Open Source Edition to V2

...

There are three easy ways to upgrade Архива:

• Manual Upgrade Standard - Download the latest distribution from the Download Center.  Run the setup over your existing version. (surefire, slower manual method!)
• Manual Upgrade Shortcut (V3 and higher) - Download a small WAR file and unpack it in the webapps folder (fast download!)
• Auto Update Run the auto update (convenient!)

...

The standard way to upgrade Архива is to download the latest version and run the installer over the existing version (do not uninstall the existing version). During the upgrade procedure, the install script will always try to preserve your server's configuration settings.

1. Stop the existing EE server
2. Login to the Архива website using your credentials and locate the Download Center.
3. Download the latest version of Архива appropriate your platform.
4. Run the setup / install script
5. Be sure to point the install path to the exact location where the existing version of Архива is installed

...

tar -xzvf mailarchiva_server_enterprise_linux_v2_7_2.tar.gz
cd mailarchiva_dist
./install

Manual Upgrade Shortcut (for V3 and higher only)

1. Download the WAR file from the Download Center.
2. Delete the contents of [main application]\webapps\ROOT
3. Unzip the contents of the downloaded WAR file into [main application]\webapps\ROOT
4. Restart the server

 Auto Update

1. Login to the Архива console
2. Visit Configuration->Auto Update
3. Click the Update button

...

The directory locations for Архива's program files, configuration files, program data and logs have changed since previous versions. Please familiarize yourself with File System Layout.

...

Important Safety Tip №2: Make sure your volume store directories are not placed anywhere under the Архива program directory (e.g.  C:\Program Files\Архива or /usr/local/mailarchiva) as the directory will be recursively deleted during the upgrade process. Your volume stores should always reside outside the Архива program directory.

...

a) In Configuration->Journal Accounts, uncheck Enabled for all connections
b) In Configuration->Listeners, disable SMTP and Milter listeners

...

a) Windows - unpack the distribution zip file containing the main setup executable. Double click the installer and follow the installer prompts.

b) Linux - run the installer as indicated below and follow the installer prompts

tar -xzvf mailarchiva_server_linux_v3_0_0.tar.gz
cd mailarchiva_dist
./install

During the install, you wil be prompted to enter the desired heap size. Refer to Memory Settings for guidance on this issue.

1. The server should be started and listening on port 8090. If not, start the server as follows:

   Code Block
   /opt/mailarchiva/server/startserver (Linux)

   Start Архива service by double clicking the Архива task tray icon, clicking Start or starting from Control Panel->Windows Services (Windows)

   Note
   Program Location Change: On Linux, the startserver script location has changed. Please familiarize yourself with the new File System Layout.

2. Since your browser may have cached copies of the old Архива interface, when logging to Архива console for the first time, be sure to refresh your browser cache (i.e. in Firefox presss Shift+Refresh). 

3. Retest your Journal Account client connections and check your SMTP / Milter listeners for correctness

   Note
   Connections Missing: If the Connections menu is missing, edit the Administrator role in Configuration->Roles and ensure that the Connections permission is assigned to it.

4. Close the old volume and create a new one for archiving. 

...

Архива v3 uses both a new volume store format and a new index format. While, Архива V3 can read and write old V1/V2 volumes, it cannot read old volume indexes. Thus, a reindex is required at minimum. Converting old volumes is a slow process and can take several days to complete on a large volume. Converting an old volume is at least x10 slower than performing a reindex.

When converting an old volume, for safety sake, the old volume will not be deleted. Thus, before converting ensure that you have at least as much free space available as is used by your current volumes. Due to the length of time volume conversion can take, we strongly recommend reindexing your old volume, as opposed to converting them to the new format. 

If upgrading from Архива OSE or Архива v2.1 and lower, please follow steps in Kerberos -> NTLM v2 Authentication Engine Change to reconfigure your Active Directory settings.

...

1. Stop the existing OSE server|
2. If necessary, rename Архива webapp directory (Архива preferences the Архива webapp name to named be ROOT).
   rename C:\Program Files\MailArchiva\server\webapps\mailarchiva to C:\Program Files\MailArchiva\server\webapps\ROOT (Windows) [if necessary]
   mv /usr/local/mailarchiva/server/webapps/mailarchiva to /usr/local/mailarchiva/server/webapps/ROOT (Linux) [if necessary]
3. Note: Performing this action will mean that you no longer access the console via http://localhost:8090/mailarchiva but simply http://localhost:8090
4. Login to the Архива website using your credentials. Click the Download Center.
5. Download the latest version of Архива appropriate your platform.

...

tar -xzvf mailarchiva_server_enterprise_linux_v2_7_2.tar.gz
cd mailarchiva_dist
./install

...

 Open Source Edition -> Newer Version Open Source Edition

1. Stop the existing OSE server
2. Login to the Sourceforge website using your credentials and locate the Архива OSE download page.
3. Download the latest version of Архива OSE appropriate your platform.
4. Run the setup / install script

...

tar -xzvf mailarchiva_server_opensource_linux_v1_5_0.tar.gz
cd mailarchiva_dist
./install.sh

Follow the steps in the v2.6 Administration Guide to redefine your AD settings. In summary, you will need to run a vbs script to create a computer account in AD and setup a password on the account. Once the VBS script is completed, it will output all the parameters that are needed for Архива's new AD settings.

...

1. The safest reindex procedure is as follows:
2. In Configuration->Volumes, write down the location of the index directory corresponding with each of your volumes
3. To ensure that all index file locks are eliminated, stop the Архива server
   a) Windows: Stop the Архива server from the Архива system tray or alternatively from the Windows services applet
   b) Linux: type /etc/init.d/mailarchiva stop
4. Backup your existing volume index directories to another location (to ensure you can get them back if the reindex process goes awry)
5. Manually delete all volume index directories (not volume store directories).
6. Run the installer over your existing copy of Архива.
7. Start the server.
8. Login to the Архива Console. Click Reindex All button in Configuration->Volumes.
   Note: Depending on your I/O constraints and how many messages you have in your archive, the reindex process can take a while to complete. Although, due to indexing operations, server performance will be degraded, the server should still be useable for normal archiving and searching activities.
9. To obtain the status of the Reindex, click Status->Processes. You should see the reindex process running there.
   A large archive can take several days to complete reindexing. Архива uses very aggressive reindexing algorithms. If your reindex appears slow, it is most likely due to I/O resource constraints. It is generally a bad idea to store your indexes on a remote drive. It is better to store them locally and on a separate drive to volume store paths

Расположение папок программных файлов Архива, файлов настроек, программных данных и логов изменилось по сравнению с предыдущей версией. Ознакомьтесь с новым расположением папок в Разделах файловой системы. 

Стандартное обновление вручную

Стандартный способ обновить Архива  - скачать последнюю версию системы и запустить установщик поверх существующей версии (не удаляя при этом установленную версию). В процессе обновления скрипт установки будет всегда стараться сохранить системные настройки вашего сервера. 

1. Остановите существующий сервис. 
2. Скачайте последнюю версию Архива для вашей операционной системы.
3. Запустите установщик или скрипт установки. 
4. Не забудьте указать путь установки именно в то месторасположение на диске, куда установлена предыдущая версия Архива.

tar -xzvf archiva_server_enterprise_linux_v8_11_30.tar.gz
cd archiva_dist
./install

Обновление WAR

1. Скачайте WAR файл,
2. Остановите сервис Архива,
3. Удалите содержимое основного приложения (/var/opt/mailarchiva/tomcat/ROOT), не удаляйте папку ROOT!!!
4. Unzip скаченный WAR файл в /var/opt/mailarchiva/tomcat/ROOT,
5. Запустите сервис Архива.