wiki.IPBRICK.COM - User contributions [en]

Users accounts Server/Work-Area Migration - Expediting the Migration Process

2018-08-16T17:24:15Z

Amachado: Created page with "'''NOTE: This tutorial is provided for systems administrators, it requires strong knowledge of linux command-line environment. One must proceed with caution. ''' = Summary =..."

'''NOTE: This tutorial is provided for systems administrators, it requires strong knowledge of linux command-line environment. One must proceed with caution. '''

= Summary =
This procedure helps expediting the migration process of users accounts from one server/workarea to another server/workarea. This is valid for migrating from one server to another (MASTER to SLAVE, or from SLAVE_A to SLAVE_B, or from SLAVE to MASTER).

A sample scenario is that of one standard/basic migration that lasted for several hours with direct impact on users access for all these several hours, can now be accomplished with less than 5 (five) minutes real impact on user.

== Standard Migration ==
The basic/standard IPBRICK (web interface) procedure consists in:
* PHASE 1 - change location information in database (IPBRICK.OS MASTER database, and system/LDAP database)
* PHASE 2 - move user's data files (personal files and maildir) from source to destination

Sometime this procedure may take a long time in "PHASE 2" (moving the data files from source to destination). In some reported scenarios this resulted in several hours per user.
This depends on several factors, such as:
* size of user's data files
** size in bytes
** size in number of individual files
* performance of system infrastructure:
** overall performance of source server, storage/disk, network bandwidth
** overall performance of destination server, storage/disk, network bandwidth

Meanwhile during the migration process the user may found himself locked out - with no access to his/hers data files (personal files nor maildir).

This is the problem: impact on user's access to its own data files.

== NEW - Assisted Migration ==
With this procedure we reduce the impact to the minimum time required to perform a simple file sync - less than 5 minutes per user.

Here we will be using a cheat procedure - user's data files migration will be done entirely in a manual procedure, we will ensure that the standard IPBRICK (web interface) will be in charge of migrating an empty folder (instantaneous migration).

Step by step description:
* ON-LINE - no impact on users access
** initial copy/synchronization of user's data files from real source user folder (source server / work-area / user folder) to temporary destination folder located at destination filesystem (destination server / work-area) - this may be a long process, may last for several hours but with no user is locked off
** intermediate synchronization - after finishing the first initial copy you may perform one or more regular intermediate synchronizations, you may register how long this intermediate synchronizations take, this is a very real measure of how long it will take to perform the last synchronization, this is the time the user will be kept off-line (impact on user)
* OFF-LINE - now it is time to perform the real migration, user will be locked off access to its data files
** last synchronization - rename real source folder to a temporary folder in the same source filesystem, perform last synchronization from this temporary source folder to the temporary destination folder - synchronization is now complete
** create an empty source folder for user
** go to IPBRICK web interface and instruct to move user to the select destination server and destination work area, Apply Configurations - Updated Successfuly
** go to destination server, destination work area, confirm that there is an empty folder for the selected user, remove that folder, rename previous temporary destination folder to the correct username
* ON-LINE - the procedure is now complete

= Requirements =

== CAUTION / ATTENTION ==
''' This tutorial is provided "as is" for systems administrators, it requires strong knowledge of linux command-line environment. You must proceed with caution and at your own risk.'''

'''We recommend you to read this procedure in advance before you start any intervention in your server. If you don't feel comfortable with the procedures stated here, we recommend you to halt your intervention and opt to request official support from our technicians at support@ipbrick.com .'''

'''NOTE: You have been warned!'''

== Backup ==
Before you start this process you must confirm that your backup is up to date. You will be messing around with your users data files, if something brokes or fails, the backup is your only best friend.

== IPBRICK versions ==
This procedure is valid for IPBRICK.OS up to the current IPBRICK.OS version - at this time v6.3u1.

== File System space availability ==
Please ensure that the destination filesystem has enough available space to accommodate all of the users data files.

= Sample Procedure =
'''NOTE: This tutorial is provided for systems administrators, it requires strong knowledge of linux command-line environment. One must proceed with caution. '''

== Source / Destination ==
In this example for instruction demonstration we will assume the following:
* username: jack
* source
** server IP: 192.168.10.1
** work area: Work Area 1
* destination
** server IP: 192.168.10.2
** work area: Work Area 2

== Folders ==
The folders that we will be working with are:
* REAL source user's account folder - located in source server <code>192.168.10.1</code> : <code>/home1/_accounts/jack</code>
* TEMPORARY destination folder - to be created in destination server <code>192.168.10.2</code> : <code>/home2/_accounts/_TEMP_jack</code>
* TEMPORARY source foldername - to be used only in the last synchronization in source server <code>192.168.10.1</code> : <code>/home1/_accounts/_DELETEME_jack</code>
* BLANK destination folder - to be used in destination server, only after last apply configurations : <code>192.168.10.2</code> : <code>/home2/_accounts/_BLANK_jack</code>
* TEMPORARY destination mount folder - to be used in destination server, only for temporary mounts for copy/synchronization : <code>192.168.10.2</code> : <code>/mnt/REAL_jack</code>

== Sync Mechanism ==
In this procedure, for matter of simplicity, we will be using NFS and RSYNC.

'''NOTE:''' You may use other advanced options such as RSYNC over SSH.

== Detailed technical procedure ==

=== ON-LINE ===
The procedures in this section allows the user to continue normal access to its own files and maildir.

==== Initial/First Copy ====
Initial/first copy - only at DESTINATION SERVER <code>192.168.10.2</code>
* create destination folders
<pre>
~# mkdir /mnt/REAL_jack
~# mkdir /home2/_accounts/_TEMP_jack
</pre>
* mount source folder at destination server mount point
<pre>
~# mount 192.168.10.1:/home1/_accounts/jack /mnt/REAL_jack
</pre>
* start first copy/synchronization
<pre>
~# rsync -avu --delete /mnt/REAL_jack/ /home2/_accounts/_TEMP_jack/ > /root/jack_rsync.log 2> /root/jack_rsync.err
</pre>
* clean up after first copy/synchronization
<pre>
~# umount /mnt/REAL_jack/
~# rmdir /mnt/REAL_jack/
</pre>

==== Intermediate Synchronization(s) ====
After finishing the first initial copy you may perform one or more regular intermediate synchronizations, you may register how long this intermediate synchronizations take, this is a very real measure of how long it will take to perform the last synchronization, this is the time the user will be kept off-line (impact on user)

We continue to work only at DESTINATION SERVER <code>192.168.10.2</code>
* preparing mount point
<pre>
~# mkdir /mnt/REAL_jack
</pre>
* mount source folder at destination server mount point
<pre>
~# mount 192.168.10.1:/home1/_accounts/jack /mnt/REAL_jack
</pre>
* start intermediate synchronization
<pre>
~# date ; rsync -avu --delete /mnt/REAL_jack/ /home2/_accounts/_TEMP_jack/ > /root/jack_rsync.log 2> /root/jack_rsync.err ; date
</pre>
* clean up after synchronization
<pre>
~# umount /mnt/REAL_jack/
~# rmdir /mnt/REAL_jack/
</pre>

Please take notice of the time lapse in the rsync command. This is the duration of the intermediate synchronization. This is the estimate time for the final synchronization.

'''NOTE:''' You may perform this step multiple times before the final/last synchronization. We recommend you to perform at least one intermediate synchronization immediately before going to the next OFF-LINE step.

=== OFF-LINE ===
The procedures in this section require the user to be off-line, this is required to ensure that there is no data lost.

'''ATTENTION: this section includes procedures to be executed in the source and in the destination server.'''

==== User is put OFF-LINE ====
To execute at SOURCE SERVER : <code>192.168.10.1</code>
* rename real source folder to a temporary folder
<pre>
~# mv /home1/_accounts/jack /home1/_accounts/_DELETEME_jack
</pre>
* create temporary source empty user folder
<pre>
~# mkdir /home1/_accounts/jack
</pre>
* list/confirm the empty folder (empty listing)
<pre>
~# ls /home1/_accounts/jack
</pre>

==== LAST Synchronization ====
To execute at DESTINATION SERVER : <code>192.168.10.2</code>
* preparing mount point
<pre>
~# mkdir /mnt/REAL_jack
</pre>
* mount source folder at destination server mount point
<pre>
~# mount 192.168.10.1:/home1/_accounts/_DELETEME_jack /mnt/REAL_jack
</pre>
* start last synchronization
<pre>
~# rsync -avu --delete /mnt/REAL_jack/ /home2/_accounts/_TEMP_jack/ > /root/jack_rsync.log 2> /root/jack_rsync.err
</pre>
* clean up after synchronization
<pre>
~# umount /mnt/REAL_jack/
~# rmdir /mnt/REAL_jack/
</pre>

==== Efective IPBRICK/System Migration ====
Go to IPBRICK web interface and instruct to move user (jack) to the select destination server (192.168.10.2) and destination work area (Work Area 2), Apply Configurations.

Updated Successfuly.

To execute at DESTINATION SERVER, <code>192.168.10.2</code>
* confirm empty user folder successful migration (in the listing bellow you should get an empty folder)
<pre>
~# ls /home2/_accounts/jack
</pre>
* rename temporary empty folder to final blank folder
<pre>
~# mv /home2/_accounts/jack /home2/_accounts/_BLANK_jack
</pre>
* rename REAL destination user folder to the final name
<pre>
~# mv /home2/_accounts/_TEMP_jack /home2/_accounts/jack
</pre>

=== ON-LINE - Finish ===
The procedure is now complete. The user may now access to its own personal files and maildir.

=== Last Clean-up ===
After all validations its now time to perform global cleanup of temporary files/folders, and free space on the source file system/server.

* To execute at DESTINATION SERVER : <code>192.168.10.2</code> - remove temporary empty folder
<pre>
~# rmdir /home2/_accounts/_BLANK_jack
</pre>
* To execute at SOURCE SERVER : <code>192.168.10.1</code> - remove source copy of users folders/files
** '''ATTENTION: this is a permanent deletion of users files, please proceed with extreme caution'''
<pre>
~# rm -rf /home1/_accounts/_DELETEME_jack
</pre>

IPBRICK.OS v6.3 - Security-Update02 - Pidgin SSL issues

2018-07-12T16:13:14Z

Amachado:

After installing Security-Update-02 for IPBRICK.OS v6.3, Pidgin users (XMPP client, instant messaging desktop application) may report difficulties connecting to the server. In such scenario please adjust Pidgin settings, one must enforce a stronger encription preferences. Proceed as follows:
# in the Tools menu select Plugins
# in the plugins list, select and activate the "NSS Preferences" plugin, then click on "Configure Plugin"
# in the ciphers list, select and activate "TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)", ok to confirm, and close all windows
# restart the connection to the server

[[File:Pidgin-sec-up-01-v63.png]]

File:Pidgin-sec-up-01-v63.png

2018-07-12T16:12:37Z

Amachado:

IPBRICK.OS v6.3 - Security-Update02 - Pidgin SSL issues

2018-07-12T16:11:58Z

Amachado: Created page with "After installing Security-Update-02 for IPBRICK.OS v6.3, Pidgin users (XMPP client, instant messaging desktop application) may report difficulties connecting to the server. In..."

Mail Archiving

2018-05-16T16:46:39Z

Amachado:

Passos de configuração de sistema de mail externo a IPBRICK.OS com iPortalDoc.

= Descrição global =
* O servidor de mail deverá efectuar cópia/filtro (Bcc) das mensagens a serem processadas/analisadas/arquivadas pelo sistema de gestão documental iPortalDoc (ver regras de filtro sugeridas);
* O servidor IPBRICK/iPortalDoc vai descarregar via POP3 as mensagens copiadas/filtradas .

= Implementação =

== Servidor de mail do cliente ==
* Criar conta de ligação - exemplo: ipdoc-filtro
* Habilitar acesso POP3 à conta ipdoc-filtro;
** indicar dados de acesso à conta POP3: endereço do servidor POP3, login, senha;
* Criar filtros de mail - recomendação - copiar em Bcc para o endereço "ipdoc-filtro@dominio.pt" os mails abaixo indicados;
** Mails associados (Ref<codigo_doc>) : copiar em Bcc todas as mensagens enviadas/recebidas com padrão "Ref<" no corpo ou no assunto;
** dbdocmails (email@dominio.pt) : copiar em Bcc todas as mensagens recebidas para (To, Cc) conta "email@dominio.pt" - ver mais detalhe na descrição do mecanismo "dbdocmails"
** Arquivo de mails (*@dominio.pt) : mail archiving :
*** copiar em Bcc todas as mensagens enviadas a partir do endereço (From: *@dominio.pt);
*** copiar em Bcc todas as mensagens recebidas no endereço (To: / Cc: *@dominio.pt).

== Servidor IPBRICK.OS/IPortalDoc ==
* Configurar serviço de ligação POP3
** Fetchmail - ALTERAÇÃO MANUAL
*** servidor POP3 : mail.dominio.pt
*** login: "ipdoc-filtro"
*** senha: ****
*** entregar mensagens em conta local "receivedmail@ipbrick.dominio.pt" (receivedmail@FQDN)
* Manutenção automática caixa local "receivedmail" -
** activar Cópia de mensagens recebidas
** activar Eliminar automaticamente cópia ao fim de 1 (um) dia

= NOTAS de parametrização =
* Mails associados : "Ref<" : a sigla "REF" é parametrizável no iPortalDoc, ajustar à sigla definida/em uso na instalação do cliente;
* dbdocmails : os endereços de email afectos ao serviço "dbdocmails" devem existir no servidor de correio do cliente, o cliente deverá assegurar a manutenção destas caixas/contas no seu servidor de mail;
* Arquivo de mails / mail archiving : os endereços associados ao serviço mail archiving devem ser explicitados, podem ser "todos", ou endereços individuais - a regra acima "*@dominio.pt" deverá ser ajustada aos endereços efectivamente pretendidos;
* Mails dos workflows - "workflow@iportaldoc.dominio.pt" - este mecanismo deve ser preterido em favor da funcionalidade "dbdocmails", passar a usar endereços "email@dominio.pt" - implica parametrização no servidor iPortalDoc;
* FETCHMAIL/ligação POP3 - este mecanismo corre com intervalos de 5 minutos, pode ser alterado MANUALMENTE para intervalos menores - exemplo: 60s.

Mail Archiving

2018-05-16T16:45:51Z

Amachado:

Passos de configuração de sistema de mail externo a IPBRICK.OS com iPortalDoc.

= Descrição global =
* O servidor de mail deverá efectuar cópia/filtro (Bcc) das mensagens a serem processadas/analisadas/arquivadas pelo sistema de gestão documental iPortalDoc (ver regras de filtro sugeridas);
* O servidor IPBRICK/iPortalDoc vai descarregar via POP3 as mensagens copiadas/filtradas .

= Modo de implementação =

== Servidor de mail do cliente ==
* Criar conta de ligação - exemplo: ipdoc-filtro
* Habilitar acesso POP3 à conta ipdoc-filtro;
** indicar dados de acesso à conta POP3: endereço do servidor POP3, login, senha;
* Criar filtros de mail - recomendação - copiar em Bcc para o endereço "ipdoc-filtro@dominio.pt" os mails abaixo indicados;
** Mails associados (Ref<codigo_doc>) : copiar em Bcc todas as mensagens enviadas/recebidas com padrão "Ref<" no corpo ou no assunto;
** dbdocmails (email@dominio.pt) : copiar em Bcc todas as mensagens recebidas para (To, Cc) conta "email@dominio.pt" - ver mais detalhe na descrição do mecanismo "dbdocmails"
** Arquivo de mails (*@dominio.pt) : mail archiving :
*** copiar em Bcc todas as mensagens enviadas a partir do endereço (From: *@dominio.pt);
*** copiar em Bcc todas as mensagens recebidas no endereço (To: / Cc: *@dominio.pt).

== Servidor IPBRICK.OS/IPortalDoc ==
* Configurar serviço de ligação POP3
** Fetchmail - ALTERAÇÃO MANUAL
*** servidor POP3 : mail.dominio.pt
*** login: "ipdoc-filtro"
*** senha: ****
*** entregar mensagens em conta local "receivedmail@ipbrick.dominio.pt" (receivedmail@FQDN)
* Manutenção automática caixa local "receivedmail" -
** activar Cópia de mensagens recebidas
** activar Eliminar automaticamente cópia ao fim de 1 (um) dia

= NOTAS de parametrização =
* Mails associados : "Ref<" : a sigla "REF" é parametrizável no iPortalDoc, ajustar à sigla definida/em uso na instalação do cliente;
* dbdocmails : os endereços de email afectos ao serviço "dbdocmails" devem existir no servidor de correio do cliente, o cliente deverá assegurar a manutenção destas caixas/contas no seu servidor de mail;
* Arquivo de mails / mail archiving : os endereços associados ao serviço mail archiving devem ser explicitados, podem ser "todos", ou endereços individuais - a regra acima "*@dominio.pt" deverá ser ajustada aos endereços efectivamente pretendidos;
* Mails dos workflows - "workflow@iportaldoc.dominio.pt" - este mecanismo deve ser preterido em favor da funcionalidade "dbdocmails", passar a usar endereços "email@dominio.pt" - implica parametrização no servidor iPortalDoc;
* FETCHMAIL/ligação POP3 - este mecanismo corre com intervalos de 5 minutos, pode ser alterado MANUALMENTE para intervalos menores - exemplo: 60s.

IPortalDoc use multiple volumes

2018-04-23T17:59:04Z

Amachado: Created page with "= Motivation = How to rearrange filestorage of an IPBRICK.OS with IPortalDoc. == Ojectives == * to separate DATA from Operating System (OS) * to allocate filestorage warehous..."

= Motivation =
How to rearrange filestorage of an IPBRICK.OS with IPortalDoc.

== Ojectives ==
* to separate DATA from Operating System (OS)
* to allocate filestorage warehouse to a separate volume, a new volume that can grow dynamically
* to allocate database binaries to a separate volume, a new volume that can grow dynamically, preferencially utilize faster disks

== More Info - LVM ==
Before proceed we recommed you to read the [[Map new LVM]] section.

= Technical Procedure =
Overview of the procedure:
* on-line - without stoping the services
** to prepare the new volumes (recommendation see [[MAP new LVM]])
** initial and intermediate synchronizatione the contents from the old to the new volume
* off-line - stop services and perform the final synchronization
** stop the services
** perform final synchronization of contents
** to replace mount point
** to restart services
* validation and final maintenance
** validate that all services are performing as expected
** do system maintenance, clean data not used, free old space

== Start Point ==
For the purpose of this section, we will assume the existence of the following volumes:
* /dev/sda :: operating system installation
** Volume Group : /dev/vgsystem1/ : lvdata1 lvos lvswap lvvar
* /dev/sdb :: disk to be used by database binaries (postgresql)
** Volume Group : /dev/vgipdocdb/ : lvipdocdb [ext4]
* /dev/sdc :: disk to be used by warehouse
** Volume Group : /dev/vgipdocarm/ : lvipdocarm [ext4]

For more information on the preparation of the new LVM volumes/filesystem please refer to [[MAP new LVM]].

== On-Line ==
These steps may be executed with the system on-line, in production state.

*TODO*

== Off-Line ==
These steps imply that service is not available, stop services for final synchronization.

*TODO*

== Final Maintenance ==
*Todo*

Map new LVM

2018-04-23T17:17:50Z

Amachado: /* FSTAB - Mount at boot time */

= Presentation =
IPBRICK.OS v6.3 installed in LVM. Clients decides to map a new HDD to migrate users data. Here we describe the process to prepare a new LVM volume and move an existing homedirs/workareas to the new LVM filesystem.

== NOTE ==
'''IMPORTANT''' : this procedure is to be executed at IPBRICK.OS linux command line as super-user (su - root). This procedure is to be executed by a system administrator with some linux console knowledge. The instructions here presented were collected from a real scenario, meanwhile you are required to check, verifiy and adapt to your own installation.

== Contents ==
In the following sections you'll find:
* Scenarios - list of typical applications
* Technical procedures

= Scenarios =
The typical scenario is:
* one disk for operating system
* one disk for users data
* one disk for database binaries

These apply to:
* FileServer - users data separated from the operating system (OS) installation
* MailServer - users data separated from the OS
* iPortalDoc - data warehouse separated from the OS, database binaries in an independente volume

= Technical Procedures =
In this section we will be working with the following setup:
* IPBRICK.OS v6.3
* OS installation using LVM
* HDD setup:
** sda - the first HDD - OS installation
** sdb - the second HDD - for user data
** sdc - the third HDD - for user data

We will be working with LVM. All physical disks are to be grouped in one new volume group.

== Identify Blocks/Disks ==
LSBLK : helps you identify physical disks and their current assignment
<pre>
ipbrick:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 1.9G 0 part
└─sda2 8:2 0 48.1G 0 part
├─vgsystem1-lvos (dm-0) 254:0 0 15G 0 lvm /
├─vgsystem1-lvswap (dm-1) 254:1 0 2G 0 lvm [SWAP]
├─vgsystem1-lvvar (dm-2) 254:2 0 20G 0 lvm /var
└─vgsystem1-lvdata1 (dm-3) 254:3 0 11.1G 0 lvm /srv/data1
sdb 8:16 0 2T 0 disk
sdc 8:32 0 2T 0 disk
sr0 11:0 1 1024M 0 rom
ipbrick:~#
</pre>

== Partitioning ==
PARTED : the tool to create partition table and partitions
<pre>
ipbrick:~# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mktable gpt
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 1
End? 2199GB
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB

(parted) select /dev/sdc
Using /dev/sdc
(parted) print
Error: /dev/sdc: unrecognised disk label
(parted) mktable gpt
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 1
End? 2199GB
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB

(parted) quit
Information: You may need to update /etc/fstab.

ipbrick:~#
</pre>
Check the new blocks:
<pre>
ipbrick:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 1.9G 0 part
└─sda2 8:2 0 48.1G 0 part
├─vgsystem1-lvos (dm-0) 254:0 0 15G 0 lvm /
├─vgsystem1-lvswap (dm-1) 254:1 0 2G 0 lvm [SWAP]
├─vgsystem1-lvvar (dm-2) 254:2 0 20G 0 lvm /var
└─vgsystem1-lvdata1 (dm-3) 254:3 0 11.1G 0 lvm /srv/data1
sdb 8:16 0 2T 0 disk
└─sdb1 8:17 0 2T 0 part
sdc 8:32 0 2T 0 disk
└─sdc1 8:33 0 2T 0 part
sr0 11:0 1 1024M 0 rom
ipbrick:~#
</pre>

== LVM configuration ==
'''PVCREATE''' : initialize the physical volumes
<pre>
ipbrick:~# pvcreate /dev/sdb1 /dev/sdc1
Writing physical volume data to disk "/dev/sdb1"
Physical volume "/dev/sdb1" successfully created
Writing physical volume data to disk "/dev/sdc1"
Physical volume "/dev/sdc1" successfully created
ipbrick:~#
</pre>
'''VGCREATE''' : initialize the volume group
<pre>
ipbrick:~# vgcreate vgshares /dev/sdb1 /dev/sdc1
Volume group "vgshares" successfully created
ipbrick:~#
</pre>
'''VGDISPLAY''' : displays information on the volume groups
<pre>
ipbrick:~# vgdisplay vgshares
--- Volume group ---
VG Name vgshares
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 2
Act PV 2
VG Size 4.00 TiB
PE Size 4.00 MiB
Total PE 1048574
Alloc PE / Size 0 / 0
Free PE / Size 1048574 / 4.00 TiB
VG UUID 3htRDP-4EEE-xG24-VBrj-cUYP-dkUW-m1h8Ya

ipbrick:~#
</pre>
'''LVCREATE''' : creates logical volume
<pre>
ipbrick:~# lvcreate -l 100%FREE -n lvshares vgshares
Logical volume "lvshares" created
ipbrick:~#
</pre>
'''LVDISPLAY''' : displays information on the logical volume
<pre>
ipbrick:~# lvdisplay vgshares
--- Logical volume ---
LV Path /dev/vgshares/lvshares
LV Name lvshares
VG Name vgshares
LV UUID JrTaAv-WYtf-SDCe-tzHl-6e0Z-VAJF-rjV5dn
LV Write Access read/write
LV Creation host, time gestdoc, 2018-04-20 18:02:24 +0100
LV Status available
# open 0
LV Size 4.00 TiB
Current LE 1048574
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:4

ipbrick:~#
</pre>

== FileSystem Configuration ==
'''MKFS.EXT4''' : initialize filesystem with EXT4 format
<pre>
ipbrick:~# mkfs.ext4 /dev/vgshares/lvshares
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
268435456 inodes, 1073739776 blocks
53686988 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
32768 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

ipbrick:~#
</pre>
Test-drive the new filesystem:
<pre>
ipbrick:~# mount /dev/vgshares/lvshares /mnt/
ipbrick:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 4.6G 9.4G 33% /
udev 10M 0 10M 0% /dev
tmpfs 1.6G 964K 1.6G 1% /run
/dev/mapper/vgsystem1-lvos 15G 4.6G 9.4G 33% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 0 3.2G 0% /run/shm
/dev/mapper/vgsystem1-lvvar 20G 1.5G 18G 8% /var
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /srv/data1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home2
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /var/spool/hylafax
/dev/mapper/vgshares-lvshares 4.0T 67M 3.8T 1% /mnt
ipbrick:~# umount /mnt
ipbrick:~#
</pre>

== FSTAB - Mount at boot time ==
The final step of this procedure is to register the mountpoint in the fstab file. In this section we provide a samples scenario, you may need to adapt to your own needs. From the manual:
<pre>
NAME:
static information about the filesystems
NAME
fstab - static information about the filesystems

SYNOPSIS
/etc/fstab

DESCRIPTION
The file fstab contains descriptive information about the various file systems.
fstab is only read by programs, and not written; it is the duty of the system
administrator to properly create and maintain this file. Each filesystem is described
on a separate line; fields on each line are separated by tabs or spaces.
Lines starting with '#' are comments, blank lines are ignored. The order of records
in fstab is important because fsck(8), mount(8), and umount(8) sequentially
iterate through fstab doing their thing.
</pre>

'''BLKID''' : identify blocks id
<pre>
ipbrick:~# blkid
/dev/sda2: UUID="exMrHD-qgY3-c8cy-Ao0t-Z6TG-JNiG-L2boKk" TYPE="LVM2_member"
/dev/mapper/vgsystem1-lvos: LABEL="LVOS" UUID="7f1dd815-0e0e-4148-bf55-e3b443de0afd" TYPE="ext4"
/dev/mapper/vgsystem1-lvswap: UUID="b6de4b36-9f16-432b-9475-636008e5efed" TYPE="swap"
/dev/mapper/vgsystem1-lvvar: LABEL="LVVAR" UUID="69a75bac-56e9-4ec6-b3a8-3f31b91019a3" TYPE="ext4"
/dev/mapper/vgsystem1-lvdata1: LABEL="LVDATA1" UUID="c8c681b9-6cd5-40a1-a075-279b7745ccce" TYPE="ext4"
/dev/sdc1: UUID="qXYDO1-oExh-O1Bb-3swI-exLi-o8YC-ReAPQb" TYPE="LVM2_member"
/dev/sdb1: UUID="cuECJ4-w5Hl-PzMd-btZ3-8I49-tcye-VBkS4x" TYPE="LVM2_member"
/dev/mapper/vgshares-lvshares: UUID="31875c98-c036-4718-ba3e-1d4212fe091b" TYPE="ext4"
ipbrick:~#
</pre>
'''FSTAB''' : filesystem fstab file
<pre>
ipbrick:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vgsystem1-lvos / ext4 errors=remount-ro 0 1
/dev/vgsystem1/lvswap none swap sw 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/mapper/vgsystem1-lvvar /var ext4 defaults 0 2
/dev/mapper/vgsystem1-lvdata1 /srv/data1 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
/srv/data1/home1 /home1 none bind 0 0
/srv/data1/home2 /home2 none bind 0 0
LABEL=ipbrick-D /opt/system/backupDB auto user,noauto 0 0
/home1/_fax /var/spool/hylafax none bind 0 0
ipbrick:~#
</pre>

Create mount point, update fstab and do the mount.
<pre>
ipbrick:~# mkdir /home3
ipbrick:~# echo "/dev/mapper/vgshares-lvshares /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2" >> /etc/fstab
ipbrick:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vgsystem1-lvos / ext4 errors=remount-ro 0 1
/dev/vgsystem1/lvswap none swap sw 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/mapper/vgsystem1-lvvar /var ext4 defaults 0 2
/dev/mapper/vgsystem1-lvdata1 /srv/data1 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
/srv/data1/home1 /home1 none bind 0 0
/srv/data1/home2 /home2 none bind 0 0
LABEL=ipbrick-D /opt/system/backupDB auto user,noauto 0 0
/home1/_fax /var/spool/hylafax none bind 0 0
/dev/mapper/vgshares-lvshares /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
ipbrick:~# mount /home3
ipbrick:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 4.6G 9.4G 33% /
udev 10M 0 10M 0% /dev
tmpfs 1.6G 964K 1.6G 1% /run
/dev/mapper/vgsystem1-lvos 15G 4.6G 9.4G 33% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 0 3.2G 0% /run/shm
/dev/mapper/vgsystem1-lvvar 20G 1.5G 18G 8% /var
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /srv/data1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home2
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /var/spool/hylafax
/dev/mapper/vgshares-lvshares 4.0T 67M 3.8T 1% /home3
ipbrick:~#
</pre>
Initialize basic structure:
<pre>
ipbrick:~# cd /home3/
ipbrick:/home3# mkdir _accounts _shares
ipbrick:/home3# ls -al
total 32
drwxr-xr-x 5 root root 4096 Apr 20 18:15 .
drwxr-xr-x 29 root root 4096 Apr 20 18:12 ..
drwxr-xr-x 2 root root 4096 Apr 20 18:15 _accounts
drwx------ 2 root root 16384 Apr 20 18:05 lost+found
drwxr-xr-x 2 root root 4096 Apr 20 18:15 _shares
ipbrick:/home3#
</pre>

Map new LVM

2018-04-23T17:16:40Z

Amachado: /* FSTAB - Mount at boot time */

= Presentation =
IPBRICK.OS v6.3 installed in LVM. Clients decides to map a new HDD to migrate users data. Here we describe the process to prepare a new LVM volume and move an existing homedirs/workareas to the new LVM filesystem.

== NOTE ==
'''IMPORTANT''' : this procedure is to be executed at IPBRICK.OS linux command line as super-user (su - root). This procedure is to be executed by a system administrator with some linux console knowledge. The instructions here presented were collected from a real scenario, meanwhile you are required to check, verifiy and adapt to your own installation.

== Contents ==
In the following sections you'll find:
* Scenarios - list of typical applications
* Technical procedures

= Scenarios =
The typical scenario is:
* one disk for operating system
* one disk for users data
* one disk for database binaries

These apply to:
* FileServer - users data separated from the operating system (OS) installation
* MailServer - users data separated from the OS
* iPortalDoc - data warehouse separated from the OS, database binaries in an independente volume

= Technical Procedures =
In this section we will be working with the following setup:
* IPBRICK.OS v6.3
* OS installation using LVM
* HDD setup:
** sda - the first HDD - OS installation
** sdb - the second HDD - for user data
** sdc - the third HDD - for user data

We will be working with LVM. All physical disks are to be grouped in one new volume group.

== Identify Blocks/Disks ==
LSBLK : helps you identify physical disks and their current assignment
<pre>
ipbrick:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 1.9G 0 part
└─sda2 8:2 0 48.1G 0 part
├─vgsystem1-lvos (dm-0) 254:0 0 15G 0 lvm /
├─vgsystem1-lvswap (dm-1) 254:1 0 2G 0 lvm [SWAP]
├─vgsystem1-lvvar (dm-2) 254:2 0 20G 0 lvm /var
└─vgsystem1-lvdata1 (dm-3) 254:3 0 11.1G 0 lvm /srv/data1
sdb 8:16 0 2T 0 disk
sdc 8:32 0 2T 0 disk
sr0 11:0 1 1024M 0 rom
ipbrick:~#
</pre>

== Partitioning ==
PARTED : the tool to create partition table and partitions
<pre>
ipbrick:~# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mktable gpt
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 1
End? 2199GB
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB

(parted) select /dev/sdc
Using /dev/sdc
(parted) print
Error: /dev/sdc: unrecognised disk label
(parted) mktable gpt
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 1
End? 2199GB
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB

(parted) quit
Information: You may need to update /etc/fstab.

ipbrick:~#
</pre>
Check the new blocks:
<pre>
ipbrick:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 1.9G 0 part
└─sda2 8:2 0 48.1G 0 part
├─vgsystem1-lvos (dm-0) 254:0 0 15G 0 lvm /
├─vgsystem1-lvswap (dm-1) 254:1 0 2G 0 lvm [SWAP]
├─vgsystem1-lvvar (dm-2) 254:2 0 20G 0 lvm /var
└─vgsystem1-lvdata1 (dm-3) 254:3 0 11.1G 0 lvm /srv/data1
sdb 8:16 0 2T 0 disk
└─sdb1 8:17 0 2T 0 part
sdc 8:32 0 2T 0 disk
└─sdc1 8:33 0 2T 0 part
sr0 11:0 1 1024M 0 rom
ipbrick:~#
</pre>

== LVM configuration ==
'''PVCREATE''' : initialize the physical volumes
<pre>
ipbrick:~# pvcreate /dev/sdb1 /dev/sdc1
Writing physical volume data to disk "/dev/sdb1"
Physical volume "/dev/sdb1" successfully created
Writing physical volume data to disk "/dev/sdc1"
Physical volume "/dev/sdc1" successfully created
ipbrick:~#
</pre>
'''VGCREATE''' : initialize the volume group
<pre>
ipbrick:~# vgcreate vgshares /dev/sdb1 /dev/sdc1
Volume group "vgshares" successfully created
ipbrick:~#
</pre>
'''VGDISPLAY''' : displays information on the volume groups
<pre>
ipbrick:~# vgdisplay vgshares
--- Volume group ---
VG Name vgshares
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 2
Act PV 2
VG Size 4.00 TiB
PE Size 4.00 MiB
Total PE 1048574
Alloc PE / Size 0 / 0
Free PE / Size 1048574 / 4.00 TiB
VG UUID 3htRDP-4EEE-xG24-VBrj-cUYP-dkUW-m1h8Ya

ipbrick:~#
</pre>
'''LVCREATE''' : creates logical volume
<pre>
ipbrick:~# lvcreate -l 100%FREE -n lvshares vgshares
Logical volume "lvshares" created
ipbrick:~#
</pre>
'''LVDISPLAY''' : displays information on the logical volume
<pre>
ipbrick:~# lvdisplay vgshares
--- Logical volume ---
LV Path /dev/vgshares/lvshares
LV Name lvshares
VG Name vgshares
LV UUID JrTaAv-WYtf-SDCe-tzHl-6e0Z-VAJF-rjV5dn
LV Write Access read/write
LV Creation host, time gestdoc, 2018-04-20 18:02:24 +0100
LV Status available
# open 0
LV Size 4.00 TiB
Current LE 1048574
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:4

ipbrick:~#
</pre>

== FileSystem Configuration ==
'''MKFS.EXT4''' : initialize filesystem with EXT4 format
<pre>
ipbrick:~# mkfs.ext4 /dev/vgshares/lvshares
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
268435456 inodes, 1073739776 blocks
53686988 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
32768 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

ipbrick:~#
</pre>
Test-drive the new filesystem:
<pre>
ipbrick:~# mount /dev/vgshares/lvshares /mnt/
ipbrick:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 4.6G 9.4G 33% /
udev 10M 0 10M 0% /dev
tmpfs 1.6G 964K 1.6G 1% /run
/dev/mapper/vgsystem1-lvos 15G 4.6G 9.4G 33% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 0 3.2G 0% /run/shm
/dev/mapper/vgsystem1-lvvar 20G 1.5G 18G 8% /var
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /srv/data1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home2
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /var/spool/hylafax
/dev/mapper/vgshares-lvshares 4.0T 67M 3.8T 1% /mnt
ipbrick:~# umount /mnt
ipbrick:~#
</pre>

== FSTAB - Mount at boot time ==
The final step of this procedure is to register the mountpoint in the fstab file. In this section we provide a samples scenario, you may need to adapt to your own needs. From the manual:
<pre>
NAME:
static information about the filesystems
NAME
fstab - static information about the filesystems

SYNOPSIS
/etc/fstab

DESCRIPTION
The file fstab contains descriptive information about the various file systems.
fstab is only read by programs, and not written; it is the duty of the system
administrator to properly create and maintain this file. Each filesystem is described
on a separate line; fields on each line are separated by tabs or spaces.
Lines starting with '#' are comments, blank lines are ignored. The order of records
in fstab is important because fsck(8), mount(8), and umount(8) sequentially
iterate through fstab doing their thing.
</pre>
T

'''BLKID''' : identify blocks id
<pre>
ipbrick:~# blkid
/dev/sda2: UUID="exMrHD-qgY3-c8cy-Ao0t-Z6TG-JNiG-L2boKk" TYPE="LVM2_member"
/dev/mapper/vgsystem1-lvos: LABEL="LVOS" UUID="7f1dd815-0e0e-4148-bf55-e3b443de0afd" TYPE="ext4"
/dev/mapper/vgsystem1-lvswap: UUID="b6de4b36-9f16-432b-9475-636008e5efed" TYPE="swap"
/dev/mapper/vgsystem1-lvvar: LABEL="LVVAR" UUID="69a75bac-56e9-4ec6-b3a8-3f31b91019a3" TYPE="ext4"
/dev/mapper/vgsystem1-lvdata1: LABEL="LVDATA1" UUID="c8c681b9-6cd5-40a1-a075-279b7745ccce" TYPE="ext4"
/dev/sdc1: UUID="qXYDO1-oExh-O1Bb-3swI-exLi-o8YC-ReAPQb" TYPE="LVM2_member"
/dev/sdb1: UUID="cuECJ4-w5Hl-PzMd-btZ3-8I49-tcye-VBkS4x" TYPE="LVM2_member"
/dev/mapper/vgshares-lvshares: UUID="31875c98-c036-4718-ba3e-1d4212fe091b" TYPE="ext4"
ipbrick:~#
</pre>
'''FSTAB''' : filesystem fstab file
<pre>
ipbrick:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vgsystem1-lvos / ext4 errors=remount-ro 0 1
/dev/vgsystem1/lvswap none swap sw 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/mapper/vgsystem1-lvvar /var ext4 defaults 0 2
/dev/mapper/vgsystem1-lvdata1 /srv/data1 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
/srv/data1/home1 /home1 none bind 0 0
/srv/data1/home2 /home2 none bind 0 0
LABEL=ipbrick-D /opt/system/backupDB auto user,noauto 0 0
/home1/_fax /var/spool/hylafax none bind 0 0
ipbrick:~#
</pre>

Create mount point, update fstab and do the mount.
<pre>
ipbrick:~# mkdir /home3
ipbrick:~# echo "/dev/mapper/vgshares-lvshares /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2" >> /etc/fstab
ipbrick:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vgsystem1-lvos / ext4 errors=remount-ro 0 1
/dev/vgsystem1/lvswap none swap sw 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/mapper/vgsystem1-lvvar /var ext4 defaults 0 2
/dev/mapper/vgsystem1-lvdata1 /srv/data1 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
/srv/data1/home1 /home1 none bind 0 0
/srv/data1/home2 /home2 none bind 0 0
LABEL=ipbrick-D /opt/system/backupDB auto user,noauto 0 0
/home1/_fax /var/spool/hylafax none bind 0 0
/dev/mapper/vgshares-lvshares /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
ipbrick:~# mount /home3
ipbrick:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 4.6G 9.4G 33% /
udev 10M 0 10M 0% /dev
tmpfs 1.6G 964K 1.6G 1% /run
/dev/mapper/vgsystem1-lvos 15G 4.6G 9.4G 33% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 0 3.2G 0% /run/shm
/dev/mapper/vgsystem1-lvvar 20G 1.5G 18G 8% /var
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /srv/data1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home2
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /var/spool/hylafax
/dev/mapper/vgshares-lvshares 4.0T 67M 3.8T 1% /home3
ipbrick:~#
</pre>
Initialize basic structure:
<pre>
ipbrick:~# cd /home3/
ipbrick:/home3# mkdir _accounts _shares
ipbrick:/home3# ls -al
total 32
drwxr-xr-x 5 root root 4096 Apr 20 18:15 .
drwxr-xr-x 29 root root 4096 Apr 20 18:12 ..
drwxr-xr-x 2 root root 4096 Apr 20 18:15 _accounts
drwx------ 2 root root 16384 Apr 20 18:05 lost+found
drwxr-xr-x 2 root root 4096 Apr 20 18:15 _shares
ipbrick:/home3#
</pre>

Map new LVM

2018-04-20T17:54:30Z

Amachado: Created page with "= Presentation = IPBRICK.OS v6.3 installed in LVM. Clients decides to map a new HDD to migrate users data. Here we describe the process to prepare a new LVM volume and move an..."

= Presentation =
IPBRICK.OS v6.3 installed in LVM. Clients decides to map a new HDD to migrate users data. Here we describe the process to prepare a new LVM volume and move an existing homedirs/workareas to the new LVM filesystem.

== NOTE ==
'''IMPORTANT''' : this procedure is to be executed at IPBRICK.OS linux command line as super-user (su - root). This procedure is to be executed by a system administrator with some linux console knowledge. The instructions here presented were collected from a real scenario, meanwhile you are required to check, verifiy and adapt to your own installation.

== Contents ==
In the following sections you'll find:
* Scenarios - list of typical applications
* Technical procedures

= Scenarios =
The typical scenario is:
* one disk for operating system
* one disk for users data
* one disk for database binaries

These apply to:
* FileServer - users data separated from the operating system (OS) installation
* MailServer - users data separated from the OS
* iPortalDoc - data warehouse separated from the OS, database binaries in an independente volume

= Technical Procedures =
In this section we will be working with the following setup:
* IPBRICK.OS v6.3
* OS installation using LVM
* HDD setup:
** sda - the first HDD - OS installation
** sdb - the second HDD - for user data
** sdc - the third HDD - for user data

We will be working with LVM. All physical disks are to be grouped in one new volume group.

== Identify Blocks/Disks ==
LSBLK : helps you identify physical disks and their current assignment
<pre>
ipbrick:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 1.9G 0 part
└─sda2 8:2 0 48.1G 0 part
├─vgsystem1-lvos (dm-0) 254:0 0 15G 0 lvm /
├─vgsystem1-lvswap (dm-1) 254:1 0 2G 0 lvm [SWAP]
├─vgsystem1-lvvar (dm-2) 254:2 0 20G 0 lvm /var
└─vgsystem1-lvdata1 (dm-3) 254:3 0 11.1G 0 lvm /srv/data1
sdb 8:16 0 2T 0 disk
sdc 8:32 0 2T 0 disk
sr0 11:0 1 1024M 0 rom
ipbrick:~#
</pre>

== Partitioning ==
PARTED : the tool to create partition table and partitions
<pre>
ipbrick:~# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mktable gpt
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 1
End? 2199GB
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB

(parted) select /dev/sdc
Using /dev/sdc
(parted) print
Error: /dev/sdc: unrecognised disk label
(parted) mktable gpt
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 1
End? 2199GB
(parted) print
Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 2199GB 2199GB

(parted) quit
Information: You may need to update /etc/fstab.

ipbrick:~#
</pre>
Check the new blocks:
<pre>
ipbrick:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 1.9G 0 part
└─sda2 8:2 0 48.1G 0 part
├─vgsystem1-lvos (dm-0) 254:0 0 15G 0 lvm /
├─vgsystem1-lvswap (dm-1) 254:1 0 2G 0 lvm [SWAP]
├─vgsystem1-lvvar (dm-2) 254:2 0 20G 0 lvm /var
└─vgsystem1-lvdata1 (dm-3) 254:3 0 11.1G 0 lvm /srv/data1
sdb 8:16 0 2T 0 disk
└─sdb1 8:17 0 2T 0 part
sdc 8:32 0 2T 0 disk
└─sdc1 8:33 0 2T 0 part
sr0 11:0 1 1024M 0 rom
ipbrick:~#
</pre>

== LVM configuration ==
'''PVCREATE''' : initialize the physical volumes
<pre>
ipbrick:~# pvcreate /dev/sdb1 /dev/sdc1
Writing physical volume data to disk "/dev/sdb1"
Physical volume "/dev/sdb1" successfully created
Writing physical volume data to disk "/dev/sdc1"
Physical volume "/dev/sdc1" successfully created
ipbrick:~#
</pre>
'''VGCREATE''' : initialize the volume group
<pre>
ipbrick:~# vgcreate vgshares /dev/sdb1 /dev/sdc1
Volume group "vgshares" successfully created
ipbrick:~#
</pre>
'''VGDISPLAY''' : displays information on the volume groups
<pre>
ipbrick:~# vgdisplay vgshares
--- Volume group ---
VG Name vgshares
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 2
Act PV 2
VG Size 4.00 TiB
PE Size 4.00 MiB
Total PE 1048574
Alloc PE / Size 0 / 0
Free PE / Size 1048574 / 4.00 TiB
VG UUID 3htRDP-4EEE-xG24-VBrj-cUYP-dkUW-m1h8Ya

ipbrick:~#
</pre>
'''LVCREATE''' : creates logical volume
<pre>
ipbrick:~# lvcreate -l 100%FREE -n lvshares vgshares
Logical volume "lvshares" created
ipbrick:~#
</pre>
'''LVDISPLAY''' : displays information on the logical volume
<pre>
ipbrick:~# lvdisplay vgshares
--- Logical volume ---
LV Path /dev/vgshares/lvshares
LV Name lvshares
VG Name vgshares
LV UUID JrTaAv-WYtf-SDCe-tzHl-6e0Z-VAJF-rjV5dn
LV Write Access read/write
LV Creation host, time gestdoc, 2018-04-20 18:02:24 +0100
LV Status available
# open 0
LV Size 4.00 TiB
Current LE 1048574
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:4

ipbrick:~#
</pre>

== FileSystem Configuration ==
'''MKFS.EXT4''' : initialize filesystem with EXT4 format
<pre>
ipbrick:~# mkfs.ext4 /dev/vgshares/lvshares
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
268435456 inodes, 1073739776 blocks
53686988 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
32768 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

ipbrick:~#
</pre>
Test-drive the new filesystem:
<pre>
ipbrick:~# mount /dev/vgshares/lvshares /mnt/
ipbrick:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 4.6G 9.4G 33% /
udev 10M 0 10M 0% /dev
tmpfs 1.6G 964K 1.6G 1% /run
/dev/mapper/vgsystem1-lvos 15G 4.6G 9.4G 33% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 0 3.2G 0% /run/shm
/dev/mapper/vgsystem1-lvvar 20G 1.5G 18G 8% /var
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /srv/data1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home2
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /var/spool/hylafax
/dev/mapper/vgshares-lvshares 4.0T 67M 3.8T 1% /mnt
ipbrick:~# umount /mnt
ipbrick:~#
</pre>

== FSTAB - Mount at boot time ==
'''BLKID''' : identify blocks id
<pre>
ipbrick:~# blkid
/dev/sda2: UUID="exMrHD-qgY3-c8cy-Ao0t-Z6TG-JNiG-L2boKk" TYPE="LVM2_member"
/dev/mapper/vgsystem1-lvos: LABEL="LVOS" UUID="7f1dd815-0e0e-4148-bf55-e3b443de0afd" TYPE="ext4"
/dev/mapper/vgsystem1-lvswap: UUID="b6de4b36-9f16-432b-9475-636008e5efed" TYPE="swap"
/dev/mapper/vgsystem1-lvvar: LABEL="LVVAR" UUID="69a75bac-56e9-4ec6-b3a8-3f31b91019a3" TYPE="ext4"
/dev/mapper/vgsystem1-lvdata1: LABEL="LVDATA1" UUID="c8c681b9-6cd5-40a1-a075-279b7745ccce" TYPE="ext4"
/dev/sdc1: UUID="qXYDO1-oExh-O1Bb-3swI-exLi-o8YC-ReAPQb" TYPE="LVM2_member"
/dev/sdb1: UUID="cuECJ4-w5Hl-PzMd-btZ3-8I49-tcye-VBkS4x" TYPE="LVM2_member"
/dev/mapper/vgshares-lvshares: UUID="31875c98-c036-4718-ba3e-1d4212fe091b" TYPE="ext4"
ipbrick:~#
</pre>
'''FSTAB''' : filesystem fstab file
<pre>
ipbrick:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vgsystem1-lvos / ext4 errors=remount-ro 0 1
/dev/vgsystem1/lvswap none swap sw 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/mapper/vgsystem1-lvvar /var ext4 defaults 0 2
/dev/mapper/vgsystem1-lvdata1 /srv/data1 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
/srv/data1/home1 /home1 none bind 0 0
/srv/data1/home2 /home2 none bind 0 0
LABEL=ipbrick-D /opt/system/backupDB auto user,noauto 0 0
/home1/_fax /var/spool/hylafax none bind 0 0
ipbrick:~#
</pre>

Create mount point, update fstab and do the mount.
<pre>
ipbrick:~# mkdir /home3
ipbrick:~# echo "/dev/mapper/vgshares-lvshares /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2" >> /etc/fstab
ipbrick:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vgsystem1-lvos / ext4 errors=remount-ro 0 1
/dev/vgsystem1/lvswap none swap sw 0 0
/dev/fd0 /floppy auto user,noauto 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0
/dev/mapper/vgsystem1-lvvar /var ext4 defaults 0 2
/dev/mapper/vgsystem1-lvdata1 /srv/data1 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
/srv/data1/home1 /home1 none bind 0 0
/srv/data1/home2 /home2 none bind 0 0
LABEL=ipbrick-D /opt/system/backupDB auto user,noauto 0 0
/home1/_fax /var/spool/hylafax none bind 0 0
/dev/mapper/vgshares-lvshares /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2
ipbrick:~# mount /home3
ipbrick:~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 15G 4.6G 9.4G 33% /
udev 10M 0 10M 0% /dev
tmpfs 1.6G 964K 1.6G 1% /run
/dev/mapper/vgsystem1-lvos 15G 4.6G 9.4G 33% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.2G 0 3.2G 0% /run/shm
/dev/mapper/vgsystem1-lvvar 20G 1.5G 18G 8% /var
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /srv/data1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home1
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /home2
/dev/mapper/vgsystem1-lvdata1 11G 44M 11G 1% /var/spool/hylafax
/dev/mapper/vgshares-lvshares 4.0T 67M 3.8T 1% /home3
ipbrick:~#
</pre>
Initialize basic structure:
<pre>
ipbrick:~# cd /home3/
ipbrick:/home3# mkdir _accounts _shares
ipbrick:/home3# ls -al
total 32
drwxr-xr-x 5 root root 4096 Apr 20 18:15 .
drwxr-xr-x 29 root root 4096 Apr 20 18:12 ..
drwxr-xr-x 2 root root 4096 Apr 20 18:15 _accounts
drwx------ 2 root root 16384 Apr 20 18:05 lost+found
drwxr-xr-x 2 root root 4096 Apr 20 18:15 _shares
ipbrick:/home3#
</pre>

Generate Let's Encrypts certs for IPBrick

2018-03-01T18:33:42Z

Amachado: Created page with "To generate a certificate you must do the following: 1 Install certbot-auto (eg. on /home1/_locals/operator) wget https://dl.eff.org/certbot-auto chmod a+x certbot-au..."

To generate a certificate you must do the following:

1 Install certbot-auto (eg. on /home1/_locals/operator)
wget https://dl.eff.org/certbot-auto
chmod a+x certbot-auto

More info on https://certbot.eff.org/#debianwheezy-other

2 Change the virtualhosts that will require certificates and write protect them:
eg. 200-200-light.domain.com
Insert lines:
SSLCertificateFile /etc/letsencrypt/live/ucoip.domain.com/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/ucoip.domain.com/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/ucoip.domain.com/chain.pem

Write protect the files: eg. chattr +i 200-200-light.domain.com

3 If you want to use CAFE Phone or UCoIP Page WebPhone you need:
Change file /etc/webrtc2sip/config.xml
Modify ssl-certificates section:
<ssl-certificates>
/etc/letsencrypt/live/ucoip.domain.com/privkey.pem;
/etc/letsencrypt/live/ucoip.domain.com/cert.pem;
*;
</ssl-certificates>

Restart service webrtc2sip:
/etc/init.d/webrtc2sip stop
/etc/init.d/webrtc2sip start

Write protect the file: eg. chattr +i /etc/webrtc2sip/config.xml

4 If you want to use UCoIP/CAFE Video Conference (WebRTC ) you need:
Copy certs into folder /opt/ucoip/site/rtc/signalmaster/ssl and create an empty ca.crt
cp /etc/letsencrypt/live/ucoip.domain/privkey.pem /opt/ucoip/site/rtc/signalmaster/ssl/private.key
cp /etc/letsencrypt/live/ucoip.domain.com/cert.pem /opt/ucoip/site/rtc/signalmaster/ssl/certificate.crt
touch /opt/ucoip/site/rtc/signalmaster/ssl/ca.crt

Change permissons and restart service:
chown webrtc.webrtc /opt/ucoip/site/rtc/signalmaster/ssl/*
/etc/init.d/webrtc_signal stop
/etc/init.d/webrtc_signal start

5 Generate the certs with the command:
/etc/init.d/apache2 stop
/home1/_locals/operator/certbot-auto certonly --standalone -d ucoip.domain.com -d webrtcproxy.domain.com -d .....
/etc/init.d/apache2 start
The cert will be created on folder: /etc/letsencrypt/live

6 Create a script to renew the cert and call the command on cron.d (Certificates valid for 90 days)
Script (eg. /home1/_locals/operator/renewcerts.sh)
#!/bin/sh
echo "***********" $(date +"%m-%d-%Y - %H:%M") >> /var/log/le-renew.log
/etc/init.d/apache2 stop >> /var/log/le-renew.log
/home1/_locals/operator/certbot-auto renew >> /var/log/le-renew.log
cp /etc/letsencrypt/live/ucoip.domain.com/privkey.pem /opt/ucoip/site/rtc/signalmaster/ssl/private.key >> /var/log/le-renew.log
cp /etc/letsencrypt/live/ucoip.domain.com/cert.pem /opt/ucoip/site/rtc/signalmaster/ssl/certificate.crt >> /var/log/le-renew.log
/etc/init.d/apache2 start >> /var/log/le-renew.log
/etc/init.d/webrtc_signal stop >> /var/log/le-renew.log
/etc/init.d/webrtc_signal start >> /var/log/le-renew.log

7. Place the script in cron.d and add execution permissions to this script
vi /etc/cron.d/letsencrypt
01 04 */15 * * root /home1/_locals/operator/renewcerts.sh
ipbrick:~# ls -la /etc/cron.d/letsencrypt
-rw-r--r-- 1 root root 58 Feb 23 16:15 /etc/cron.d/letsencrypt

chmod 755 /home1/_locals/operator/renewcerts.sh

IPortalDoc External MailServer Integration

2018-01-16T18:38:35Z

Amachado:

This page goal is to demonstrate how to integrate iPortalDoc with another mailserver.

= Introduction =

== iPortalDoc e-mail integration features ==
iPortalDoc supports the following email integration features:
* workflows - ''WORKFLOW_NAME@iportaldoc.yourdomain.com''
** start a new document workflow using the attached file in the incoming e-mail to the WORKFLOW_NAME
* associated e-mails - default ''REF<document_code>''
** all e-mails transported through yourcompany mail server, that have ''REF<document_code>'' in the subject and/or in the body, should be copied, archived in iPortalDoc and associated to the document with ''document_code''
* DBDOCMAILS module
** selected emails are to be processed by iPortalDoc - to be used to start a new document workflow
* MAIL ARCHIVING
** all emails from selected mailboxes are to be processed/archived by iPortalDoc

== Scenarios ==
We will analyse the following scenarios:
* INTERNAL - mailserver is in the LAN, or it is in a private routed network, it has connectivity with the iPortalDoc server
** SMTP route - it is feasible to implement a SMTP route, so we will prefer this connection type
* EXTERNAL - mailserver is not in a private routed network, it does not have connectivity with the iPortalDoc server - generic or cloud scenarios
** POP Connector / fetchmail - mails are delivered in a specific mailbox, iPortalDoc server will download the messages using fetchmail

= INTERNAL - SMTP Route =
In this scenario we will configure a SMTP route for iPortalDoc.
# all mails destinated to "@iportaldoc.yourdomain.com" are to be smtp routed to iPortalDoc server

== Filters ==
* workflows - this feature is automatically resolved by the smtp routed defined above, no additional settings are required
* associated e-mails - create an e-mail filter for:
** e-mails that have expression REF< in the subject or in the body are to be BCC copied to "receivedmail@iportaldoc.yourdomain.com"

IPortalDoc External MailServer Integration

2018-01-16T18:06:37Z

Amachado:

This page goal is to demonstrate how to integrate iPortalDoc with another mailserver.

== Scenarios ==
We will analyse the following scenarios:
* INTERNAL - mailserver is in the LAN, or it is in a private routed network, it has connectivity with the iPortalDoc server
** SMTP route - it is feasible to implement a SMTP route
* EXTERNAL - mailserver is not in a private routed network, it does not have connectivity with the iPortalDoc server - generic or cloud scenarios
** POP Connector / fetchmail - mails are delivered in a specific mailbox and download , SMTP route is not an option, it is not feasible to implement a SMTP route

= INTERNAL - SMTP Route =
In this scenario we will configure a SMTP route for iPortalDoc.
# all mails destinated to "@iportaldoc.yourdomain.com" are to be smtp routed to iPortalDoc server

== Filters ==

IPortalDoc External MailServer Integration

2018-01-16T17:59:29Z

Amachado:

This page goal is to demonstrate how to integrate iPortalDoc with another mailserver.

== Scenarios ==
We will analyse the following scenarios:
* INTERNAL - mailserver is in the LAN, or it is in a private routed network, it has connectivity with the iPortalDoc server
** SMTP route - it is feasible to implement a SMTP route
* EXTERNAL - mailserver is not in a private routed network, it does not have connectivity with the iPortalDoc server - generic or cloud scenarios
** SMTP route - it is not feasible to implement a SMTP route

= INTERNAL - SMTP Route =
In this scenario we will configure a SMTP route for iPortalDoc.
# all mails destinated to "@iportaldoc.yourdomain.com" are to be smtp routed to iPortalDoc server
#

IPortalDoc External MailServer Integration

2018-01-16T13:59:46Z

Amachado: Created page with "This page goal is to demonstrate how to integrate iPortalDoc with another mailserver. == Scenarios == We will analyse the following scenarios: * INTERNAL - mailserver is in t..."

Migrating an iPortalDoc from IPBRICK 5.x to 6.1

2017-09-29T15:35:28Z

Amachado:

''' ***PAGE ON CONSTRUCTION*** '''

'''NOTE:''' This procedure is also valid for upgrades from IPBRICK v5.x to v6.1 or greater.

This next procedure will explain how to update an IPBrick version 5.x with iPortalDoc to an IPBrick version 6.1 with iPortalDoc.
After this migration, iPortalDoc will be in version 4.2.1 running on top of IPBrick version 6.1. After this procedure is fully completed, you can update iPortalDoc to its newer version.

== Before Migrating: ==

Check iPortalDoc's version: iPortalDoc needs to be at least in version 4.2.1 (or greater) before the migration to an IPBrick version 6.1 or greater.

In this procedure, we will assume three possible scenarios in IPBrick version 5.3:

'''Scenario A - iPortalDoc is installed with version 4.0.1'''

* IPD-400000 | iPortalDoc v4.0
* IPD-400001 | iPortalDoc v4.0.u1

'''Scenario B - iPortalDoc is installed with version 4.2.1'''

* IPD-420000 | iPortalDoc v4.2
* IPD-420001 | iPortalDoc v4.2.u1

'''Scenario C - UCoIP is installed with version 3.0'''

* IPD-400000 | iPortalDoc v4.0
* BIL-200000 | ipbrick-billing - Billing Software v2.0.
* UFI-300000 | ucoip4iportaldoc - UCoIP for iPortalDoc

=== Scenarios A and B ===

'''If iPortalDoc is installed with version 4.0.1 (Scenario A) start by installing the necessary updates until it reaches version 4.2.1.'''

* Install:
# iPortalDoc version 4.0 update 2: iportaldoc-v4_0-2.deb
# iPortalDoc version 4.0 update 3: iportaldoc-v4_0-3.deb
# iPortalDoc version 4.0 update 4: iportaldoc-v4_0-4.deb
# iPortalDoc version 4.0 update 5: iportaldoc-v4_0-5.deb
#* Apply configurations
# iPortalDoc version 4.2: iportaldoc-v4_2.deb
#* Apply configurations
# iPortalDoc version 4.2 update 1: iportaldoc-v4_2-1.deb (available here: [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_44_108&products_id=784])
#* Apply configurations

'''If your iPortalDoc is already in version 4.2.1 (Scenario B), or if you have just updated it to this version (Scenario A), you can continue from this point on, without having to install any more updates.'''

* Check IP Contacts version: It needs to be at least in version 4.9 before the migration to an IPBrick version 6.1 (please find the download link on the bottom of this page).

Note: If Contacts is already in version 5.0.1 you don't need to apply any update.

* Backup iPortalDoc's DB (command [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5])

Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path

* If there's an iPortalDoc Light, update to version 3.2, please follow this by backing up the data

Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file dump_file_path

* Before migrating IPBrick 5.3 we recommend that you update IPBrick version at least till update 11, since this update will install Groupware version 1.2.11-2:
** IPBrick v5.3 - update 11 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_73_6_38&products_id=581]

'''NOTE: Check your browser's version if you are using Internet Explorer. iPortalDoc is fully compatible with Internet Explorer version 9 or higher.'''

''' iPortalDoc is also compatible with Google Chrome and Mozilla Firefox.'''

=== Scenario C - UCoIP is installed with iPortalDoc version 4.0 ===

* Install:
# iPortalDoc version 4.0 update 1: iportaldoc-v4_0-1.deb
# iPortalDoc version 4.0 update 2: iportaldoc-v4_0-2.deb
# iPortalDoc version 4.0 update 3: iportaldoc-v4_0-3.deb
# iPortalDoc version 4.0 update 4: iportaldoc-v4_0-4.deb
# iPortalDoc version 4.0 update 5: iportaldoc-v4_0-5.deb
#* Apply configurations
# UCoIP Recording version 4 (you may find its link on the bottom of the page)
#* Apply configurations
# iPortalDoc version 4.2 update 1: iportaldoc-v4_2-1.deb (available here: [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_44_108&products_id=784])
#* Apply configurations

* Check IP Contacts version: It needs to be at least in version 4.9 before the migration to an IPBrick version 6.1 (please find the download link on the bottom of this page).

Note: If Contacts is already in version 5.0.1 you don't need to apply any update.

* Backup iPortalDoc's DB (command [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5])

Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path

* If there's an iPortalDoc Light, update to version 3.2, please follow this by backing up the data

Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file dump_file_path

* Before migrating IPBrick 5.3 we recommend that you update IPBrick version at least till update 11, since this update will install Groupware version 1.2.11-2:
** IPBrick v5.3 - update 11 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_73_6_38&products_id=581]

'''NOTE: Check your browser's version if you are using Internet Explorer. iPortalDoc is fully compatible with Internet Explorer version 9 or higher.'''

''' iPortalDoc is also compatible with Google Chrome and Mozilla Firefox.'''

== After the installation of IPBrick version 6.1: ==

* Install iPortalDoc v4.2 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_85&products_id=694]
'''Note:''' If you have UCoIP, please install UCoIP Recording version 4.0 and skip the step above, since the UCoIP Recording package already includes iPortalDoc v4.2; you may find its link on the bottom of the page.

* Install update 1 for iPortalDoc v4.2 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_44_108&products_id=802]

Note: If you had any other updates for iPortalDoc installed in version 5.x, you now need to install them again in IPBrick version 6.1.

* If IPBrick 5.x had IP Contacts version 5.0.1 installed, you can update it now to the same version but for IPBrick version 6.1 (please find the link on the bottom of the page).

* Replace IPBrick's configurations that were migrated to IPBrick 6.1.

* Restore iPortalDoc's DB [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6]

Eg:
./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql

* If there is an iPortalDoc Light, restore the DB

Eg:
./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump

* Rebuild iPortalDoc workflow accounts:
a) Definitions Menu -> Configuration Interface
b) Poplist on the right (Menu) -> Workflows
c) Click on the Rebuild button

* Rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
a) Access Share: Definitions -> Configuration Interface-> Build Global FS
b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS
(This task is scheduled to be executed at midnight);

* Contacts application: rebuild entities and contacts
a) Administration -> Rebuild Contacts

* Update iPortalDoc till the last official update

== Useful links: ==

IPContacts v4.8 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/wiki/ipbrick-contacts_4.8_all.deb]

IPContacts v4.9 update to install in an IPBrick v5 [[Media:Ipbrick-contacts_4.9_all.deb |[7]]]

IPContacts v5.0.1 update to install in an IPBrick v6.1 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_73_35&products_id=891]

UCoIP Recording v4.0 update to install in an IPBrick v5 [[http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_51&products_id=799[8]]]

Script ipbrickdb_ipb5: [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5 |[9]]

md5sum: 7339475f75c10cd7b54347f0cf6a5361

Script ipbrickdb_ipb6: [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6 |[10]]

md5sum: 5d071c63f9a0a9a23802682a45f9e9fa

UCoIP DNS/firewall configuration

2017-07-19T09:52:02Z

Amachado: /* DNS configuration */

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001.domain.com. IN A 85.86.87.88
voip.domain.com. IN A 85.86.87.88
webrtc.domain.com. IN A 85.86.87.88
cafe.domain.com. IN A 85.86.87.88
ucoip.domain.com. IN A 85.86.87.88
im.domain.com. IN A 85.86.87.88
iportaldoc.domain.com. IN A 85.86.87.88
</pre>

CNAME records:

<pre>
contacts.domain.com. IN CNAME srv001.domain.com.
jwchat.domain.com. IN CNAME srv001.domain.com.
light.domain.com. IN CNAME srv001.domain.com.
webphone.domain.com. IN CNAME srv001.domain.com.
groupware.domain.com. IN CNAME srv001.domain.com.
webmail.domain.com. IN CNAME srv001.domain.com.
webrtcproxy.domain.com. IN CNAME srv001.domain.com.
autoconfig.domain.com. IN CNAME srv001.domain.com.
autodiscover.domain.com. IN CNAME srv001.domain.com.
*.domain.com. IN CNAME ucoip.domain.com.
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

SPF - Sender Policy Framework
<pre>
domain.com IN TXT "v=spf1 mx ip4:85.86.87.88 -all"
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:
<pre>
88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.
</pre>

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP-client - 5222 TCP
XMPP-server - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

UCoIP DNS/firewall configuration

2017-07-19T09:51:26Z

Amachado: /* DNS configuration */

Configurations for OpenVPN client

2016-10-04T14:45:24Z

Amachado: /* Linux - Native openVPN client */

= SSL =

Each user needs its own certificate. These are generated in the IPBrick communications server.
Next, we will see the configuration data necessary for several devices.

NOTE: The attached configuration is protected by a unique password for each certificate/user.

== Smartphones/tablets - install OpenVPN client ==

=== iOS IPhone/IPad : Apple Store (iTunes) : OpenVPN Connect ===

* Download and install the application from:
** https://itunes.apple.com/pt/app/openvpn-connect/id590379981?mt=8
* Install the certificate: the certificado.zip needs to be handled and rewritten so it fits all together in a single .ovpn file (see an example here: [[How_to_rewrite_an_OpenVPN_file|How to rewrite an OpenVPN file]]);
* Send the .ovpn file to the device, click to open and it will be automatically associated to the openVPN APP.

=== Android : Google Play : OpenVPN Connect ===

* Download and install the application from:
** https://play.google.com/store/apps/details?id=net.openvpn.openvpn
* Install the certificate: the certificado.zip needs to be handled and rewritten so it fits all together in a single .ovpn file;
* Send the .ovpn file to the device, click to open and it will be automatically associated to the openVPN APP.

== PCs / Laptops ==

=== MAC OS - TunnelBlick ===

* Download and install the client application from:
** https://tunnelblick.net/downloads.html
* Install certificate: decompress the certified file to the folder "certificado", change the name of the folder for "certificado.tblk" (add the extension .tblk) and you'll notice that, when the folder's name is being changed, the icon of the folder will also change to one associated to tunnelblick, so you'll only have to click on this icon and it will appear an option to install;
* Start connection: click on the tunnelblick icon in the upper right-hand corner (near the clock) and connect - insert the password of the certificate (as an option, you may save the password by clicking in the keys).

=== Windows XP/7/Vista/8/10 - openVPN ===
* Download and install the client application from:
** https://openvpn.net/index.php/download/community-downloads.html
* Install and configure the desktop shortcut to execute always as an Administrator;
* Install certificate: decompress the certificado.zip to the folder %programfiles%\openvpn\config\ (check and adjust the path according to the installation);
* Start connection:

=== Linux - Native openVPN client ===

* openvpn, network-manager-openvpn
* Ubuntu, Debian : apt-get install network-manager-openvpn-gnome

After installing the client application, it's necessary to "double-click" on the attached file, which contains all the information on VPN configurations.

After completing the configuration, every time you wish to start the VPN connection, you just have to initiate the client application and give instructions to establish the recorded connection. It is also possible to memorize the credentials (password) to open the certificate.

UCoIP DNS/firewall configuration

2016-08-09T16:29:20Z

Amachado:

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001.domain.com. IN A 85.86.87.88
voip.domain.com. IN A 85.86.87.88
webrtc.domain.com. IN A 85.86.87.88
cafe.domain.com. IN A 85.86.87.88
ucoip.domain.com. IN A 85.86.87.88
im.domain.com. IN A 85.86.87.88
</pre>

CNAME records:

<pre>
jwchat.domain.com. IN CNAME srv001.domain.com.
webphone.domain.com. IN CNAME srv001.domain.com.
groupware.domain.com. IN CNAME srv001.domain.com.
webmail.domain.com. IN CNAME srv001.domain.com.
webrtcproxy.domain.com. IN CNAME srv001.domain.com.
*.domain.com. IN CNAME ucoip.domain.com.
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

SPF - Sender Policy Framework
<pre>
domain.com IN TXT "v=spf1 mx ip4:85.86.87.88 -all"
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:
<pre>
88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.
</pre>

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP-client - 5222 TCP
XMPP-server - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

UCoIP DNS/firewall configuration

2016-08-09T16:28:42Z

Amachado:

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001.domain.com. IN A 85.86.87.88
voip.domain.com. IN A 85.86.87.88
webrtc.domain.com. IN A 85.86.87.88
cafe.domain.com. IN A 85.86.87.88
ucoip.domain.com. IN A 85.86.87.88
im.domain.com. IN A 85.86.87.88
</pre>

CNAME records:

<pre>
jwchat.domain.com. IN CNAME srv001.domain.com.
webphone.domain.com. IN CNAME srv001.domain.com.
groupware.domain.com. IN CNAME srv001.domain.com.
webmail.domain.com. IN CNAME srv001.domain.com.
webrtcproxy.domain.com. IN CNAME srv001.domain.com.
*.domain.com. IN CNAME srv001.domain.com.
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

SPF - Sender Policy Framework
<pre>
domain.com IN TXT "v=spf1 mx ip4:85.86.87.88 -all"
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:
<pre>
88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.
</pre>

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP-client - 5222 TCP
XMPP-server - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

UCoIP DNS/firewall configuration

2016-08-09T16:16:10Z

Amachado: /* DNS configuration */

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001.domain.com. IN A 85.86.87.88
voip.domain.com. IN A 85.86.87.88
webrtc.domain.com. IN A 85.86.87.88
cafe.domain.com. IN A 85.86.87.88
ucoip.domain.com. IN A 85.86.87.88
im.domain.com. IN A 85.86.87.88
</pre>

CNAME records:

<pre>
jwchat.domain.com. IN CNAME srv001.domain.com.
webphone.domain.com. IN CNAME srv001.domain.com.
groupware.domain.com. IN CNAME srv001.domain.com.
webmail.domain.com. IN CNAME srv001.domain.com.
jsmith.domain.com. IN CNAME srv001.domain.com.
webrtcproxy.domain.com. IN CNAME srv001.domain.com.
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

SPF - Sender Policy Framework
<pre>
domain.com IN TXT "v=spf1 mx ip4:85.86.87.88 -all"
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:
<pre>
88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.
</pre>

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP-client - 5222 TCP
XMPP-server - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

UCoIP DNS/firewall configuration

2016-08-09T16:12:57Z

Amachado:

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001.domain.com. IN A 85.86.87.88
voip.domain.com. IN A 85.86.87.88
webrtc.domain.com. IN A 85.86.87.88
cafe.domain.com. IN A 85.86.87.88
ucoip.domain.com. IN A 85.86.87.88
im.domain.com. IN A 85.86.87.88
</pre>

CNAME records:

<pre>
jwchat.domain.com. IN CNAME srv001.domain.com.
webphone.domain.com. IN CNAME srv001.domain.com.
groupware.domain.com. IN CNAME srv001.domain.com.
webmail.domain.com. IN CNAME srv001.domain.com.
jsmith.domain.com. IN CNAME srv001.domain.com.
webrtcproxy.domain.com. IN CNAME srv001.domain.com.
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:

88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP-client - 5222 TCP
XMPP-server - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

UCoIP DNS/firewall configuration

2016-08-09T16:12:37Z

Amachado:

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001.domain.com. IN A 85.86.87.88
voip.domain.com. IN A 85.86.87.88
webrtc.domain.com. IN A 85.86.87.88
cafe.domain.com. IN A 85.86.87.88
ucoip.domain.com. IN A 85.86.87.88
im.domain.com. IN A 85.86.87.88
</pre>

CNAME records:

<pre>
jwchat.domain.com. IN CNAME srv001.domain.com.
webphone.domain.com. IN CNAME srv001.domain.com.
groupware.domain.com. IN CNAME srv001.domain.com.
webmail.domain.com. IN CNAME srv001.domain.com.
jsmith.domain.com. IN CNAME srv001.domain.com.
webrtcproxy.domain.com. IN CNAME srv001.domain.com.
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:

88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP-client - 5222 TCP
XMPP-server - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

Migrating an iPortalDoc from IPBRICK 5.x to 6

2016-06-20T12:02:11Z

Amachado:

= Before Migrating: =

- You need to have IPBrick configurations migrated to version 6.0. Please send the last configuration file of IPBrick server v5.x to support@ipbrick.com and wait for the reply with a configurations file ready to be uploaded to version 6.0.

- Check iPortalDoc version: iPortalDoc need to be in version 4.2.1 (or greater) before the migration to an IPBrick version 6.0 or greater.

iPortalDoc update 1 for IPbrick versions 5.x is available here: [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_44_108&products_id=784]

Note: If iPortalDoc is in version 4.2.1 you don't need to apply any update now.

- Check IPBRICK Contacts version: Contacts need to be in version 4.3 before the migration to an IPBrick version 6.0.

Note: If Contacts is in version 4.4 or greater you don't need to apply any update now.

- Backup the DB (command [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5])

Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path

- If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data

Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file dump_file_path

'''NOTE: Check your browsers version if you are using Internet Explorer. iPortalDoc is fully compatible with Internet Explorer version 9 or greater.'''

iPortalDoc is compatible with Google Chrome and Mozilla Firefox.

= After the installation of IPBrick version 6.0: =

- Install iPortalDoc v4.2 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_85&products_id=694]

- Install update 1 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_44_108&products_id=785]

After the installation of IPBrick v6.0 and iPortalDoc v4.2.1 the next step will be to replace IPBrick configurations file that you have previous received from our support. Please upload that configrations file and replace those configurations.

If there are any updates that need to be installed in order to have a successful configuration replacement, you will be presented with that information. Follow the instructions given and install all the necessary updates.

- Restore the dbdoc DB [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6]

Eg:
./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql

- If there is an iPortalDoc Light, restore the DB

Eg:
./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump

- Rebuild iPortalDoc workflow accounts:
a) Definitions Menu -> Configuration Interface
b) Poplist on the right (Menu) -> Workflows
c) Click on the Rebuild button

- Rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
a) Access Share: Definitions -> Configuration Interface-> Build Global FS
b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS
(This task is scheduled to be executed at midnight);

= Useful links: =

IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]

IPContacts v4.4 update to install in an IPBrick v6.0 [http://downloads3.ipbrick.com/wiki/contacts4ipbrick_4.4_all.deb]

IPContacts v4.5 update to install in an IPBrick v6.0 [http://downloads3.ipbrick.com/wiki/contacts4ipbrick_4.5_all.deb]

IPContacts v4.6 update to install in an IPBrick v6.0 [http://downloads3.ipbrick.com/wiki/contacts4ipbrick_4.6_all.deb]

IPContacts v4.7 update to install in an IPBrick v6.0 [http://downloads3.ipbrick.com/wiki/contacts4ipbrick_4.7_all.deb]

IPContacts v4.8 update to install in an IPBrick v6.0 [http://downloads3.ipbrick.com/wiki/contacts4ipbrick_4.8_all.deb]

Script ipbrickdb_ipb5: [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5]

md5sum: 7339475f75c10cd7b54347f0cf6a5361

Script ipbrickdb_ipb6: [http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6]

md5sum: 5d071c63f9a0a9a23802682a45f9e9fa

= Known Issues =

== Licence Error ==
Problem: After restoring /home1/_dbdoc and the database dump, when you try to access IPortalDoc web interface you get an error in IPortalDoc homepage.

Solution: remove the old licence files, delete files:
* /home1/_dbdoc/ficheiros/erro_acesso1.php
* /home1/_dbdoc/ficheiros/erro_acesso2.php

Example:
root@ipbrick:~# rm /home1/_dbdoc/ficheiros/erro_acesso1.php
root@ipbrick:~# rm /home1/_dbdoc/ficheiros/erro_acesso2.php

Afterwards you can access to IPortalDoc web interface, you are now prompted to insert a new valid licence. Please refer to IPortalDoc Installation manual, licence activation procedure.

== Other Issues ==
If you get different error messages, please report to support@iportaldoc.com

In case of the foll

IPBrick Disk migration

2016-05-12T17:54:43Z

Amachado: /* Procedure */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=

== Second server installation ==
Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
** NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates

'''NOTE - Licence Activation''' - during this procedure you will need to reactivate your product, please send file.dat to email address support@ipbrick.com requesting licence activation - to (re)activate a licence you are required to have a valid maintenance/software assurance contract.

== Procedure ==
EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rh1.log 2> rh1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rh2.log 2> rh2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> databases -> and replace the last one.

== IPortalDoc ==
If you have IPortalDoc installed, you must now restore the database backup separatelly. This procedure is now executed in the new server (NOTE that after replacing configurations this server is now called ipbrick2, just like the original server.)
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.3, 5.4 or 5.5 - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

Go to IPortalDoc Web interface, login with an administrator account,
* rebuild iPortalDoc workflow accounts:
** a) Definitions Menu -> Configuration Interface
** b) Poplist on the right (Menu) -> Workflows
** c) Click on the Rebuild button
* rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
** a) Access Share: Definitions -> Configuration Interface-> Build Global FS
** b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS
*** (This task is scheduled to be executed at midnight);

Go to IPContacts application, login with an administrator account
* rebuild entities and contacts
** a) Administration -> Rebuild Contacts

= Finish =
Now it is time to test and check all services.

IPBrick Disk migration

2016-05-12T17:43:29Z

Amachado: /* Scenario 2 - two server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=

== Second server installation ==
Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
** NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates

'''NOTE - Licence Activation''' - during this procedure you will need to reactivate your product, please send file.dat to email address support@ipbrick.com requesting licence activation - to (re)activate a licence you are required to have a valid maintenance/software assurance contract.

== Procedure ==
EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rh1.log 2> rh1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rh2.log 2> rh2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> databases -> and replace the last one.

== IPortalDoc ==
If you have IPortalDoc installed, you must now restore the database backup separatelly. This procedure is now executed in the new server (NOTE that after replacing configurations this server is now called ipbrick2, just like the original server.)
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.3, 5.4 or 5.5 - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

Go to IPortalDoc Web interface, login with an administrator account,
* rebuild iPortalDoc workflow accounts:
** a) Definitions Menu -> Configuration Interface
** b) Poplist on the right (Menu) -> Workflows
** c) Click on the Rebuild button
* rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
** a) Access Share: Definitions -> Configuration Interface-> Build Global FS
** b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS
*** (This task is scheduled to be executed at midnight);

Go to IPContacts application, login with an administrator account
* rebuild entities and contacts
** a) Administration -> Rebuild Contacts

= Finish =
Now it is time to test and check all services.

IPBrick Disk migration

2016-05-12T17:43:00Z

Amachado: /* Scenario 2 - two server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=

== Second server installation ==
Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
** NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates

'''NOTE - Licence Activation''' - during this procedure you will need to reactivate your product, please send file.dat to email address support@ipbrick.com requesting licence activation - to (re)activate a licence you are required to have a valid maintenance/software assurance contract.

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rh1.log 2> rh1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rh2.log 2> rh2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> databases -> and replace the last one.

== IPortalDoc ==
If you have IPortalDoc installed, you must now restore the database backup separatelly. This procedure is now executed in the new server (NOTE that after replacing configurations this server is now called ipbrick2, just like the original server.)
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.3, 5.4 or 5.5 - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

Go to IPortalDoc Web interface, login with an administrator account,
* rebuild iPortalDoc workflow accounts:
** a) Definitions Menu -> Configuration Interface
** b) Poplist on the right (Menu) -> Workflows
** c) Click on the Rebuild button
* rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
** a) Access Share: Definitions -> Configuration Interface-> Build Global FS
** b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS
*** (This task is scheduled to be executed at midnight);

Go to IPContacts application, login with an administrator account
* rebuild entities and contacts
** a) Administration -> Rebuild Contacts

= Finish =
Now it is time to test and check all services.

IPBrick Disk migration

2016-05-12T17:38:01Z

Amachado: /* Scenario 2 - two server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rh1.log 2> rh1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rh2.log 2> rh2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> databases -> and replace the last one.

== IPortalDoc ==
If you have IPortalDoc installed, you must now restore the database backup separatelly. This procedure is now executed in the new server (NOTE that after replacing configurations this server is now called ipbrick2, just like the original server.)
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.3, 5.4 or 5.5 - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --restore --dbname dbdoc --file /home2/_backup_db_dbdoc/dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

Go to IPortalDoc Web interface, login with an administrator account,
* rebuild iPortalDoc workflow accounts:
** a) Definitions Menu -> Configuration Interface
** b) Poplist on the right (Menu) -> Workflows
** c) Click on the Rebuild button
* rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
** a) Access Share: Definitions -> Configuration Interface-> Build Global FS
** b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS
*** (This task is scheduled to be executed at midnight);

Go to IPContacts application, login with an administrator account
* rebuild entities and contacts
** a) Administration -> Rebuild Contacts

= Finish =
Now it is time to test and check all services.

IPBrick Disk migration

2016-05-12T17:33:06Z

Amachado: /* IPortalDoc */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick2:~# mkdir /home2/_backup_db_dbdoc
ipbrick2:~# cd /home2/_backup_db_dbdoc
ipbrick2:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick2:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick2:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick2:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rh1.log 2> rh1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rh2.log 2> rh2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> databases -> and replace the last one.

== IPortalDoc ==
If you have IPortalDoc installed, you must now restore the database backup separatelly. This procedure is now executed in the new server (NOTE that after replacing configurations this server is now called ipbrick2, just like the original server.)
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ip
</pre>
* IPBRICK.IC version 5.3, 5.4 or 5.5 - use '''ipbrickdb_ipb5'''
<pre>
</pre>

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-12T17:32:33Z

Amachado: /* Scenario 2 - two server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick1:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick1:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pC
tg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynRe
aiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZP
VkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rh1.log 2> rh1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rh2.log 2> rh2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> databases -> and replace the last one.

== IPortalDoc ==
If you have IPortalDoc installed, you must now restore the database backup separatelly. This procedure is now executed in the new server (NOTE that after replacing configurations this server is now called ipbrick2, just like the original server.)
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ip
</pre>
* IPBRICK.IC version 5.3, 5.4 or 5.5 - use '''ipbrickdb_ipb5'''
<pre>
</pre>

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-12T17:27:23Z

Amachado: /* IPortalDoc */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick1:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al dbdoc_20160512_1700.sql
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
ipbrick1:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-12T17:26:27Z

Amachado: /* IPortalDoc */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above - use '''ipbrickdb_ipb6'''
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al
total 557380
drwxr-xr-x 3 root root 4096 May 12 17:17 .
drwxr-xr-x 10 root root 4096 May 12 17:16 ..
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
drwxr-xr-x 4 root root 4096 May 12 17:17 ipbrick_db
-rw-r--r-- 1 root root 41386 Mar 18 2015 ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x - use '''ipbrickdb_ipb5'''
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb5
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb5 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al
total 557380
drwxr-xr-x 3 root root 4096 May 12 17:17 .
drwxr-xr-x 10 root root 4096 May 12 17:16 ..
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
drwxr-xr-x 4 root root 4096 May 12 17:17 ipbrick_db
-rw-r--r-- 1 root root 41386 Mar 18 2015 ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc#
</pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-12T17:24:13Z

Amachado: /* IPortalDoc */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al
total 557380
drwxr-xr-x 3 root root 4096 May 12 17:17 .
drwxr-xr-x 10 root root 4096 May 12 17:16 ..
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
drwxr-xr-x 4 root root 4096 May 12 17:17 ipbrick_db
-rw-r--r-- 1 root root 41386 Mar 18 2015 ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc#
</pre>
* IPBRICK.IC version 5.x

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-12T17:23:54Z

Amachado: /* On the original server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the databases.
* IPBRICK.OS version 6.x or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

== IPortalDoc ==
If you have IPortalDoc installed, you must backup this database separatelly.
* IPBRICK.OS version 6.x or above
<pre>
ipbrick1:~# mkdir /home2/_backup_db_dbdoc
ipbrick1:~# cd /home2/_backup_db_dbdoc
ipbrick1:/home2/_backup_db_dbdoc# wget http://downloads3.ipbrick.com/wiki/ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc# php5 ipbrickdb_ipb6 --dump --dbname dbdoc --file dbdoc_20160512_1700.sql

STARTING DUMP OF DATABASE dbdoc TO FILE dbdoc_20160512_1717.sql

ipbrick1:/home2/_backup_db_dbdoc# ls -al
total 557380
drwxr-xr-x 3 root root 4096 May 12 17:17 .
drwxr-xr-x 10 root root 4096 May 12 17:16 ..
-rw-r--r-- 1 root root 570695550 May 12 17:20 dbdoc_20160512_1700.sql
drwxr-xr-x 4 root root 4096 May 12 17:17 ipbrick_db
-rw-r--r-- 1 root root 41386 Mar 18 2015 ipbrickdb_ipb6
ipbrick1:/home2/_backup_db_dbdoc#
* IPBRICK.IC version 5.x

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-12T16:48:14Z

Amachado: /* Scenario 2 - two server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the data bases.
* IPBRICK.IC version v6.0 or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)
* NOTE: you must install exactly the same software version, this means that you must use the same IPBRICK.OS version and the exact same list of IPBRICK packages and/or updates
* Afterwards you can proceed with the procedure

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-09T16:30:56Z

Amachado: /* On the original server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/systemmonitor stop
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the data bases.
* IPBRICK.IC version v6.0 or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

IPBrick Disk migration

2016-05-06T09:35:59Z

Amachado: /* Scenario 2 - two server machine */

This guide is to assist the IT IPBRICK administrator in the process of migrating a running IPBRICK installation from:
* scenario 1 : one server machine - one disk to another disk on the same server machine
* scenario 2 : two server machine - one disk to another disk on a different server machine

'''ATTENTION: This is an advanced procedure. The tasks described bellow are to be performed by an IT technician familiar with IPBRICK.IC operating system architecture and linux command line interface. This guide refers to the IPBRICK installation manual and the disaster recovery procedure. Before starting please make sure that you have an up to date backup of all data files, databases and configurations. Proceed at your own risk.'''

=On the original server machine=
On the original installation, apply configurations and download/save a backup copy configurations file to your Desktop. (Advanced Configurations -> Disaster Recovery -> Download : select the last one with the current timestamp).

Just stop the the services you use.
<pre>
/etc/init.d/asterisk stop
/etc/init.d/apache2 stop
/etc/init.d/ejabberd stop
/etc/init.d/qmail stop
...
</pre>

Execute this command to backup all the data bases.
* IPBRICK.IC version v6.0 or above
<pre>php5 /opt/system/backupSYS/backup_DBs.php </pre>
* IPBRICK.IC versions: 5.3, 5.4 or 5.5
<pre>php5 /opt/ipbox/backupSYS/backup_DBs.php </pre>

=Scenario 1 - only one server machine=
Procedure:
* shutdown the server machine
* remove/detach the original (old) disk from the server
* install/attach the replacement (new) disk
* install the IPBRICK.IC operating system (please refer to IPBRICK.IC installation manual)
** perform the first boot, proceed with initial setup (FQDN, IP)
** after finishing installation and initial configuration proceed to the next step
* with the server power on, connect the old (original) disk using a USB connector
** now at the command line you can check for the disks
<pre>
fdisk -l
</pre>
* confirm that you have 2 (two) disks: sda (new internal disk) and sdb (old disk connected via usb)
** you shoudl be able to identify the partition tables
* create two temporary folders to map/mount the work areas from the old disk
<pre>
mkdir /old_home1
mkdir /old_home2
ls /old_home* -al
</pre>
* Then we need to mount the partitions we need to copy.
<pre>
mount /dev/sdb7 /old_home1
mount /dev/sdb8 /old_home2
</pre>
* Now lets start the rsync
<pre>
rsync -aAuv /old_home1/ /home1/ > /tmp/rsync_home1.log 2> /tmp/rsync_home1.err &
rsync -aAuv /old_home2/ /home2/ > /tmp/rsync_home2.log 2> /tmp/rsync_home2.err &
</pre>
* You can see the logs in these files (log is normal output, err is for status warning)
<pre>
tail /tmp/rsync_home1.log
tail /tmp/rsync_home1.err
tail /tmp/rsync_home2.log
tail /tmp/rsync_home2.err
</pre>
* When the rsync process finishes, you can unmap/unmount the old disk
<pre>
umount /old_home1
umount /old_home2
</pre>
* after successfull unmount you can disconnect the old disk (usb)
** NOTE: we recommend you to keep the old disk safe until this procedure is completly finished (backup procedure)
* Now please access to web interface, insert and replace the configurations file that you have previously saved on your desktop
** Please refer to the installation manual and/or disaster recover procedure in order to perform settings replacement
** The server machine performs a reboot
* After the server boot up, go to IPBRICK web interface, Advanced configurations -> Disaster Recovery -> Aplications -> Databases : for each database, click on the database name, then you get a listing of all the available backups, click on the last timestamp (click on the timestamp, not on the download link), and click on Restore to proceed to restore.
* When this Finnish test the services you have on IPBrick
* For the last step you need to re-activate your license - Advanced configurations -> IPBrick -> Web Access : License activation (please refer to the installation manual, license activation)

=Scenario 2 - two server machine=
Procedure
* Install the IPBrick on the new machine (refer to IPBRICK.IC installation manual)

EX: IPBrick1 New (192.168.69.199) and IPBrick2 OLD (192.168.69.200)

On machine IPBrick1 generate ssh key:
<pre>
ipbrick1:~# cd /root
ipbrick1:~# ssh-keygen -t rsa
#assume default location /root/.ssh/id_rsa
#enter empty passphrase
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
3d:90:bf:f3:95:b3:96:6f:9d:90:95:98:69:fd:fb:0b root@ipbrick1
The key's randomart image is:
+--[ RSA 2048]----+
| |
| . |
| o = .|
| + = + |
| S + . o .|
| o o ..|
| o E=.+|
| o .+=o|
| ...+=|
+-----------------+
ipbrick1:~#
</pre>

Copy contents of public key from IPBrick1 to IPBrick2.
<pre>
ipbrick1:~# cat /root/ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1
ipbrick1:~#
</pre>
Select and copy the output/contents of file id_rsa.pub from IPBrick1 as example above, install it on IPBrick2. Example:
<pre>
ipbrick2:~# mkdir -p /home1/_ssh/root/.ssh
ipbrick2:~# echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCRRerZEo0cyzCP3JxTabRAG8uPe4DVnAuduIUUayn+r64mrpy1RFcu1qQLGiKFyOgxCg3m+pCtg79yxvWfrx/XR/SIXh1uuLSmG/SOnFmn5WQJLXSCNBYGp/2BOQ1e4p6J2GFzmJF5/QnUXWCbLyIG/j7+klidLhktv/8+gHJClehMm6H31KynReaiuSyNiPFoG9+q5EmF+7Ibjqk5ZG6XeGodgINpfnNNFNLTmG+RyCK0vttGwVyKbnz2s3ypAbHpjQcNm7vG9iq73KjPaH1Y2r/09XoV3Bw15/0ZPVkkvlNHSwBpnsHrCAL8KT3m7qgDy2WT3cuArXRpm/PGTMXH root@ipbrick1" >> /home1/_ssh/root/.ssh/authorized_keys
ipbrick2:~#
</pre>

Now for the first root ssh access from ipbrick1 to ipbrick2 using the ssh key.
<pre>
ipbrick1:~# ssh -i /root/.ssh/id_rsa root@192.168.69.200
The authenticity of host '192' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? ^C
atlas:~# ssh -i /root/.ssh/id_rsa root@localhost
The authenticity of host '192.168.69.200 (192.168.69.200)' can't be established.
RSA key fingerprint is 2d:b9:97:b6:c0:e9:1e:b7:c4:51:01:ab:e9:21:12:51.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.69.200' (RSA) to the list of known hosts.

++++++++++++++++++++++++++++++: System Info :+++++++++++++++++++++++++++++++++
+ FQDN = ipbrick2.domain.com
+ IP address = 192.168.69.200
+ Kernel = 3.2.0-4-amd64
+ Uptime = 10:05:02 up 458 days, 32 min, 10 users, load average: 3.04, 2.51, 2.20
+ Total CPUs = 4 x Architecture x86_64 @ 2399.734 Hz
+ Total Memory = 16470664 kB
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ipbrick2:~# logout
Connection to 192.168.69.200 closed.
ipbrick1:~#
</pre>

Now you can access as root from ipbrick1 (NEW, 192.168.69.199) to ipbrick2 (OLD, 192.168.69.200).

Now lets start the rsync on IPBrick1.

<pre>
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home1/ /home1/ > rsync_home1.log 2> rsync_home1.err
ipbrick1:~# rsync -avu --delete --rsh="ssh -l root -i /root/.ssh/id_rsa " 192.168.69.200:/home2/ /home2/ > rsync_home2.log 2> rsync_home2.err
</pre>

You can see the logs in this file -> rsync_home1.log
Or the errors in this file -> rsync_home1.err

Wen the rsync is finish access to web interface and then insert and replace the configuration that you save on your desktop.

After replacing, go to Advanced configuration -> disaster recovery -> aplication -> data bases -> and replace the last one.

Wen this Finnish test the services you have on IPBrick.

UCoIP DNS/firewall configuration

2016-04-13T17:04:07Z

Amachado:

=DNS configuration=

In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.

Next is given an example for the public DNS zone configuration. In that example lets suppose that:

<pre>
DNS domain: domain.com
IPBrick FQDN: srv001.domain.com
Public IP associated to IPBrick: 85.86.87.88
User UCoIP page to create: jsmith.domain.com
</pre>

So in this case we need to configure the following DNS records:

A records:

<pre>
srv001 IN A 85.86.87.88
voip IN A 85.86.87.88
webrtc IN A 85.86.87.88
cafe IN A 85.86.87.88
ucoip IN A 85.86.87.88
im IN A 85.86.87.88
</pre>

CNAME records:

<pre>
jwchat IN CNAME srv001
webphone IN CNAME srv001
groupware IN CNAME srv001
webmail IN CNAME srv001
jsmith IN CNAME srv001
webrtcproxy IN CNAME srv001
</pre>

SRV records for VoIP (SIP):

<pre>
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com.
_sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com.
_sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
</pre>

SRV records for chat (Jabber/XMPP):

<pre>
_jabber._tcp.domain.com. 86400 IN SRV 5 0 5269 im.domain.com.
_xmpp-server._tcp.domain.com. 86400 IN SRV 5 0 5269 im.domain.com.
_xmpp-client._tcp.domain.com. 86400 IN SRV 5 0 5222 im.domain.com.
</pre>

SRV record for UCoIP:

<pre>
_ucoip._tcp.domain.com. 86400 IN SRV 1 0 80 ucoip.domain.com.
</pre>

SRV record for CAFE:

<pre>
_cafe._tcp.domain.com. 86400 IN SRV 1 0 443 cafe.domain.com.
</pre>

SRV record for WebRTC:

<pre>
_webrtc._tcp.domain.com. 86400 IN SRV 1 0 8888 webrtc.domain.com.
</pre>

If IPBrick will be the email server, we need to modify/add the MX record:

<pre>
domain.com. IN MX 5 srv001.domain.com.
</pre>

Costumer ISP must add this PTR record at reverse DNS zone:

88.87.86.85.in-addr.arpa. IN PTR srv001.domain.com.

=Firewall/Router configuration=

UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).

But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:

<pre>
HTTP - 80 TCP
HTTPS - 443 TCP
SMTP - 25 TCP
SIP - 5060 UDP/TCP
SIPS - 5061 TCP
RTP - 40000:45000 UDP
RTP - 50000:55000 UDP
RTP - 60000:65000 UDP
XMPP - 5222 TCP
XMPP - 5269 TCP
XMPPS - 5223 TCP
WebRTC - 8888 TCP
Webphone - 10060 UDP/TCP
Webphone - 10062 TCP
</pre>

NOTE: With update04_6.1, it's crucial too to have a Wildcard SSL Certificate. More information here:

[http://eshop.ipbrick.com/eshop/software_info.php?cPath=7_74_16&products_id=907&language=en Update04 security guide]

[https://wiki.ipbrick.com/index.php/How_to_buy_and_configure_a_SSL_certificate_at_IPBrick_6.1 How to buy and configure a SSL certificate at IPBrick]

ISCSI

2016-01-26T16:58:06Z

Amachado: /* Discover and Map */

== Introduction ==

iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.

iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.

It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

== Requirements ==

IPBrick v6.0

Connection to the Internet

== Installation ==

The installation process is done via sources list update.

Access the console:

NOTE: This procedure is done directly at the server's console as a root user.

ipbrick:~# vi /etc/apt/sources.list

#deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60
deb http://ftp.pt.debian.org/debian wheezy main contrib non-free
deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Still at the console, run these commands:

ipbrick:~# apt-get update
...

ipbrick:~# apt-get install open-iscsi

== Configuration ==

In order to configure an iSCSI interface please follow these steps:

NOTE: The service configuration is done directly at the server's console as a root user.

The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.

Usually its name is composed by these elements:

iqn + . + year-month + . + server_name + : + custom_string

E.g:
cat /etc/iscsi/initiatorname.iscsi

GenerateName=no
InitiatorName=iqn.2015-12.com.domain.ipbrick:fileserver

The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:

...
node.startup = automatic
...

And also the authentication parameters:

- '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:

...
#node.session.auth *
#discovery.sendtargets.auth *
...

- '''WITH AUTHENTICATION - CHAP''':

...
node.session.auth.authmethod = CHAP
...
node.session.auth.username = username
node.session.auth.password = password
...
discovery.sendtargets.auth.authmethod = CHAP
...
discovery.sendtargets.auth.username = username
discovery.sendtargets.auth.password = password
...

NOTE: Please replace username and password by the username and password of your iSCSI Target.

Proceed by stopping and then restarting the iSCSI service - execute:

/etc/init.d/open-iscsi stop
/etc/init.d/open-iscsi start

==Discover and Map==

Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15

Example:

ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78

Map the Target

ipbrick:~# iscsiadm -m node -l -T "iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78"
Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78,
portal: 192.168.69.15,3260]
Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful

With a dmesg command it's now possible to see the new disc as a device sdb:

Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
scsi1 : iSCSI Initiator over TCP/IP
scsi2 : iSCSI Initiator over TCP/IP
scsi3 : iSCSI Initiator over TCP/IP
scsi4 : iSCSI Initiator over TCP/IP
scsi5 : iSCSI Initiator over TCP/IP
scsi6 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access QNAP
iSCSI Storage 3.1 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:
(53.6 GB/50.0 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 5:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk

If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:

mkfs.ext4 /dev/sdb

fstab mapping is done by device and it can be captured via /dev/sdb unique identifier:

To find the unique identifier (UUID) run:
blkid
...
/dev/sdb: UUID="46c2c071-ffb3-400e-8239-5f53c81a0b72" TYPE="ext4"

It will be necessary to inscribe it at /etc/fstab

Assuming that this new volume will be used as home3, create its mount point:

mkdir /home3

Map /etc/fstab by executing the nano editor:

nano /etc/fstab

Inscribe the following:

UUID=46c2c071-ffb3-400e-8239-5f53c81a0b72 /home3 ext4 defaults,_netdev,usrquota,grpquota,user_xattr,acl 0

NOTE:
* we have the **_netdev** option to state that this device is a network dependent device
* the last column was removed, this entry has only 5 columns - the sixth column is removed so it will not try to run automatic fsck (filesystem check) on boot (this is done before network is available, so it would fail and stop the boot up sequence)

Now, you need to run this script so as home3 can be added to the IPBRICK web interface.

/opt/system/scripts/system_add_new_workareas.php 1

You will get the following notification:

Work Area 3 was successfully inserted!
Don't forget to Apply Configurations to commit the changes.

== Firewall ==

Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:

Advanced Configurations -> Network -> Firewall

Click on Insert and create a rule of this type:

Type of configuration to insert: General Settings
Rule: INPUT
Interface: ETHx (The NIC used in the iSCSI connection)
Protocol ALL
Origin IP: [Storage IPs]
Policy: ACCEPT

Click on the Insert button to create the rule

== Manage iSCSI ==

Some useful commands to manage iSCSI on IPBrick:

Restart the openiscsi: /etc/init.d/open-iscsi restart
Check the session status: /etc/init.d/open-iscsi status
Use the dmesg command to find the disc's device;

ISCSI

2016-01-26T16:29:49Z

Amachado: /* Discover and Map */

== Introduction ==

iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.

iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.

It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

== Requirements ==

IPBrick v6.0

Connection to the Internet

== Installation ==

The installation process is done via sources list update.

Access the console:

NOTE: This procedure is done directly at the server's console as a root user.

ipbrick:~# vi /etc/apt/sources.list

#deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60
deb http://ftp.pt.debian.org/debian wheezy main contrib non-free
deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Still at the console, run these commands:

ipbrick:~# apt-get update
...

ipbrick:~# apt-get install open-iscsi

== Configuration ==

In order to configure an iSCSI interface please follow these steps:

NOTE: The service configuration is done directly at the server's console as a root user.

The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.

Usually its name is composed by these elements:

iqn + . + year-month + . + server_name + : + custom_string

E.g:
cat /etc/iscsi/initiatorname.iscsi

GenerateName=no
InitiatorName=iqn.2015-12.com.domain.ipbrick:fileserver

The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:

...
node.startup = automatic
...

And also the authentication parameters:

- '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:

...
#node.session.auth *
#discovery.sendtargets.auth *
...

- '''WITH AUTHENTICATION - CHAP''':

...
node.session.auth.authmethod = CHAP
...
node.session.auth.username = username
node.session.auth.password = password
...
discovery.sendtargets.auth.authmethod = CHAP
...
discovery.sendtargets.auth.username = username
discovery.sendtargets.auth.password = password
...

NOTE: Please replace username and password by the username and password of your iSCSI Target.

Proceed by stopping and then restarting the iSCSI service - execute:

/etc/init.d/open-iscsi stop
/etc/init.d/open-iscsi start

==Discover and Map==

Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15

Example:

ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78

Map the Target

ipbrick:~# iscsiadm -m node -l -T "iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78"
Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78,
portal: 192.168.69.15,3260]
Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful

With a dmesg command it's now possible to see the new disc as a device sdb:

Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
scsi1 : iSCSI Initiator over TCP/IP
scsi2 : iSCSI Initiator over TCP/IP
scsi3 : iSCSI Initiator over TCP/IP
scsi4 : iSCSI Initiator over TCP/IP
scsi5 : iSCSI Initiator over TCP/IP
scsi6 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access QNAP
iSCSI Storage 3.1 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:
(53.6 GB/50.0 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 5:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk

If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:

mkfs.ext4 /dev/sdb

fstab mapping is done by device and it can be captured via /dev/sdb

It will be necessary to inscribe it at /etc/fstab

Assuming that this new volume will be used as home3, create its mount point:

mkdir /home3

Map /etc/fstab by executing the nano editor:

nano /etc/fstab

Inscribe the following:

/dev/sdb /home3 ext4 defaults,_netdev,usrquota,grpquota,user_xattr,acl 0 2

Now, you need to run this script so as home3 can be added to the IPBRICK web interface.

/opt/system/scripts/system_add_new_workareas.php 1

You will get the following notification:

Work Area 3 was successfully inserted!
Don't forget to Apply Configurations to commit the changes.

== Firewall ==

Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:

Advanced Configurations -> Network -> Firewall

Click on Insert and create a rule of this type:

Type of configuration to insert: General Settings
Rule: INPUT
Interface: ETHx (The NIC used in the iSCSI connection)
Protocol ALL
Origin IP: [Storage IPs]
Policy: ACCEPT

Click on the Insert button to create the rule

== Manage iSCSI ==

Some useful commands to manage iSCSI on IPBrick:

Restart the openiscsi: /etc/init.d/open-iscsi restart
Check the session status: /etc/init.d/open-iscsi status
Use the dmesg command to find the disc's device;

How to rewrite an OpenVPN file

2016-01-26T13:47:04Z

Amachado:

Once you have the zip file, decompress it.

ZIP file: user.zip - http://downloads3.ipbrick.com/wiki/user.zip

Inside you'll find four files:
* ca-server-ipbrick.crt
md5sum: ca8153af46bf8cddab95a064e54c1474 ca-server-ipbrick.crt
* user.crt
md5sum: c7a060b8e842415586c25319188eac8b user.crt
* user.key
md5sum: c0898f304cef0dd56e38243937226883 user.key
* user.ovpn
md5sum: f03249bce06c8107c4d109faa34a75c8 user.ovpn

'''Then, open your .ovpn file. It will look like the one below.'''
<source lang="bash">
# Generated by IPbrick - iPortalMais in 2014-Jan-10 19:01
client
dev tun0
#dev-node MyTap
proto tcp
remote vpn.osvaldomatos.pt 1194
#remote-random
resolv-retry infinite
nobind
user nobody
group nogroup
persist-key
persist-tun
#http-proxy-retry
#http-proxy [proxy server] [proxy port]
#mute-replay-warnings
ca ca-server-mail.crt
cert ipbricksupport.crt
key ipbricksupport.key
ns-cert-type server
#tls-auth ta.key 1
#cipher x
comp-lzo
verb 2
#mute 20
#daemon
</source>

[[File:Userovpn1.png]]

'''To rewrite it, add the following elements (as highlighted in red, in the picture below):'''
*''';'''
* '''<ca> </ca>'''
* '''<cert> </cert>'''
* '''<key> </key>'''
* '''The content of each file.'''

[[File:Userovpn2.png]]

'''Note: Use a text editor to open the files and copy its content.'''

'''Your .ovpn file is now ready, it will look like the next one.'''

[[File:Userovpn3.png]]

ISCSI

2015-12-18T18:50:08Z

Amachado: /* Discover and Map */

== Introduction ==

iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.

iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.

It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

== Requirements ==

IPBrick v6.0

Connection to the Internet

== Installation ==

The installation process is done via sources list update.

Access the console:

NOTE: This procedure is done directly at the server's console as a root user.

ipbrick:~# vi /etc/apt/sources.list

#deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60
deb http://ftp.pt.debian.org/debian wheezy main contrib non-free
deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Still at the console, run these commands:

ipbrick:~# apt-get update
...

ipbrick:~# apt-get install open-iscsi

== Configuration ==

In order to configure an iSCSI interface please follow these steps:

NOTE: The service configuration is done directly at the server's console as a root user.

The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.

Usually its name is composed by these elements:

iqn + . + year-month + . + server_name + : + custom_string

E.g:
cat /etc/iscsi/initiatorname.iscsi

GenerateName=no
InitiatorName=iqn.2015-12.com.domain.ipbrick:fileserver

The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:

...
node.startup = automatic
...

And also the authentication parameters:

- '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:

...
#node.session.auth *
#discovery.sendtargets.auth *
...

- '''WITH AUTHENTICATION - CHAP''':

...
node.session.auth.authmethod = CHAP
...
node.session.auth.username = username
node.session.auth.password = password
...
discovery.sendtargets.auth.authmethod = CHAP
...
discovery.sendtargets.auth.username = username
discovery.sendtargets.auth.password = password
...

NOTE: Please replace username and password by the username and password of your iSCSI Target.

Proceed by stopping and then restarting the iSCSI service - execute:

/etc/init.d/open-iscsi stop
/etc/init.d/open-iscsi start

==Discover and Map==

Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15

Example:

ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78

Map the Target

ipbrick:~# iscsiadm -m node -l -T "iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78"
Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78,
portal: 192.168.69.15,3260]
Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful

With a dmesg command it's now possible to see the new disc as a device sdb:

Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
scsi1 : iSCSI Initiator over TCP/IP
scsi2 : iSCSI Initiator over TCP/IP
scsi3 : iSCSI Initiator over TCP/IP
scsi4 : iSCSI Initiator over TCP/IP
scsi5 : iSCSI Initiator over TCP/IP
scsi6 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access QNAP
iSCSI Storage 3.1 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:
(53.6 GB/50.0 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 5:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk

If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:

mkfs.ext4 /dev/sdb

fstab mapping is done by device and it can be captured via /dev/sdb

It will be necessary to inscribe it at /etc/fstab

Assuming that this new volume will be used as home3, create its mount point:

mkdir /home3

Map /etc/fstab by executing the nano editor:

nano /etc/fstab

Inscribe the following:

/dev/sdb /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2

Now, you need to run this script so as home3 can be added to the IPBRICK web interface.

/opt/system/scripts/system_add_new_workareas.php 1

You will get the following notification:

Work Area 3 was successfully inserted!
Don't forget to Apply Configurations to commit the changes.

== Firewall ==

Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:

Advanced Configurations -> Network -> Firewall

Click on Insert and create a rule of this type:

Type of configuration to insert: General Settings
Rule: INPUT
Interface: ETHx (The NIC used in the iSCSI connection)
Protocol ALL
Origin IP: [Storage IPs]
Policy: ACCEPT

Click on the Insert button to create the rule

== Manage iSCSI ==

Some useful commands to manage iSCSI on IPBrick:

Restart the openiscsi: /etc/init.d/open-iscsi restart
Check the session status: /etc/init.d/open-iscsi status
Use the dmesg command to find the disc's device;

ISCSI

2015-12-18T18:49:51Z

Amachado: /* Configuration */

== Introduction ==

iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.

iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.

It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

== Requirements ==

IPBrick v6.0

Connection to the Internet

== Installation ==

The installation process is done via sources list update.

Access the console:

NOTE: This procedure is done directly at the server's console as a root user.

ipbrick:~# vi /etc/apt/sources.list

#deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60
deb http://ftp.pt.debian.org/debian wheezy main contrib non-free
deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Still at the console, run these commands:

ipbrick:~# apt-get update
...

ipbrick:~# apt-get install open-iscsi

== Configuration ==

In order to configure an iSCSI interface please follow these steps:

NOTE: The service configuration is done directly at the server's console as a root user.

The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.

Usually its name is composed by these elements:

iqn + . + year-month + . + server_name + : + custom_string

E.g:
cat /etc/iscsi/initiatorname.iscsi

GenerateName=no
InitiatorName=iqn.2015-12.com.domain.ipbrick:fileserver

The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:

...
node.startup = automatic
...

And also the authentication parameters:

- '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:

...
#node.session.auth *
#discovery.sendtargets.auth *
...

- '''WITH AUTHENTICATION - CHAP''':

...
node.session.auth.authmethod = CHAP
...
node.session.auth.username = username
node.session.auth.password = password
...
discovery.sendtargets.auth.authmethod = CHAP
...
discovery.sendtargets.auth.username = username
discovery.sendtargets.auth.password = password
...

NOTE: Please replace username and password by the username and password of your iSCSI Target.

Proceed by stopping and then restarting the iSCSI service - execute:

/etc/init.d/open-iscsi stop
/etc/init.d/open-iscsi start

==Discover and Map==

Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15

Example:

ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78

Map the Target

ipbrick:~# iscsiadm -m node -l -T "iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78"
Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78,
portal: 192.168.69.15,3260]
Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful

With a dmesg command it's now possible to see the new disc as a device sdb:

Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
scsi1 : iSCSI Initiator over TCP/IP
scsi2 : iSCSI Initiator over TCP/IP
scsi3 : iSCSI Initiator over TCP/IP
scsi4 : iSCSI Initiator over TCP/IP
scsi5 : iSCSI Initiator over TCP/IP
scsi6 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access QNAP
iSCSI Storage 3.1 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:
(53.6 GB/50.0 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 5:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk

If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:

mkfs.ext4 /dev/sdb

fstab mapping is done by device and it can be captured via /dev/sdb

It will be necessary to inscribe it at /etc/fstab

Assuming that this new volume will be used as home3, create its mount point:

mkdir /home3

Map /etc/fstab by executing the nano editor:

nano /etc/fstab

Inscribe the following:

/dev/sdb /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2

Now, you need to run this script so as home3 can be added to the IPBRICK web interface.

/opt/system/scripts/system_add_new_workareas.php 1

You will get the following notification:

Work Area 3 was successfully inserted!
Don't forget to Apply Configurations to commit the changes.

== Firewall ==

Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:

Advanced Configurations -> Network -> Firewall

Click on Insert and create a rule of this type:

Type of configuration to insert: General Settings
Rule: INPUT
Interface: ETHx (The NIC used in the iSCSI connection)
Protocol ALL
Origin IP: [Storage IPs]
Policy: ACCEPT

Click on the Insert button to create the rule

== Manage iSCSI ==

Some useful commands to manage iSCSI on IPBrick:

Restart the openiscsi: /etc/init.d/open-iscsi restart
Check the session status: /etc/init.d/open-iscsi status
Use the dmesg command to find the disc's device;

ISCSI

2015-12-18T18:43:10Z

Amachado: /* Configuration */

== Introduction ==

iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.

iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.

It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

== Requirements ==

IPBrick v6.0

Connection to the Internet

== Installation ==

The installation process is done via sources list update.

Access the console:

NOTE: This procedure is done directly at the server's console as a root user.

ipbrick:~# vi /etc/apt/sources.list

#deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60
deb http://ftp.pt.debian.org/debian wheezy main contrib non-free
deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Still at the console, run these commands:

ipbrick:~# apt-get update
...

ipbrick:~# apt-get install open-iscsi

== Configuration ==

In order to configure an iSCSI interface please follow these steps:

NOTE: The service configuration is done directly at the server's console as a root user.

The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.

Usually its name is composed by these elements:

iqn + . + year-month + . + server_name + : + custom_string

E.g:
cat /etc/iscsi/initiatorname.iscsi

GenerateName=no
InitiatorName=iqn.2015-12.com.domain.ipbrick:fileserver

The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:

...
node.startup = automatic
...

And also the authentication parameters:

- '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:

...
#node.session.auth *
#discovery.sendtargets.auth *
...

- '''WITH AUTHENTICATION - CHAP''':

...
node.session.auth.authmethod = CHAP
...
node.session.auth.username = username
node.session.auth.password = password
...
discovery.sendtargets.auth.authmethod = CHAP
...
discovery.sendtargets.auth.username = username
discovery.sendtargets.auth.password = password
...

NOTE: Please replace username and password by the username and password of your iSCSI Target.

Proceed by stopping and then restarting the iSCSI service - execute:

/etc/init.d/open-iscsi stop
/etc/init.d/open-iscsi start

Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15

Example:

ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78

Map the Target

ipbrick:~# iscsiadm -m node -l -T "iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78"
Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78,
portal: 192.168.69.15,3260]
Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful

With a dmesg command it's now possible to see the new disc as a device sdb:

Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
scsi1 : iSCSI Initiator over TCP/IP
scsi2 : iSCSI Initiator over TCP/IP
scsi3 : iSCSI Initiator over TCP/IP
scsi4 : iSCSI Initiator over TCP/IP
scsi5 : iSCSI Initiator over TCP/IP
scsi6 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access QNAP
iSCSI Storage 3.1 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:
(53.6 GB/50.0 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 5:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk

If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:

mkfs.ext4 /dev/sdb

fstab mapping is done by device and it can be captured via /dev/sdb

It will be necessary to inscribe it at /etc/fstab

Assuming that this new volume will be used as home3, create its mount point:

mkdir /home3

Map /etc/fstab by executing the nano editor:

nano /etc/fstab

Inscribe the following:

/dev/sdb /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2

Now, you need to run this script so as home3 can be added to the IPBRICK web interface.

/opt/system/scripts/system_add_new_workareas.php 1

You will get the following notification:

Work Area 3 was successfully inserted!
Don't forget to Apply Configurations to commit the changes.

== Firewall ==

Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:

Advanced Configurations -> Network -> Firewall

Click on Insert and create a rule of this type:

Type of configuration to insert: General Settings
Rule: INPUT
Interface: ETHx (The NIC used in the iSCSI connection)
Protocol ALL
Origin IP: [Storage IPs]
Policy: ACCEPT

Click on the Insert button to create the rule

== Manage iSCSI ==

Some useful commands to manage iSCSI on IPBrick:

Restart the openiscsi: /etc/init.d/open-iscsi restart
Check the session status: /etc/init.d/open-iscsi status
Use the dmesg command to find the disc's device;

ISCSI

2015-12-18T18:41:06Z

Amachado: /* Installation */

== Introduction ==

iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.

iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.

It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

== Requirements ==

IPBrick v6.0

Connection to the Internet

== Installation ==

The installation process is done via sources list update.

Access the console:

NOTE: This procedure is done directly at the server's console as a root user.

ipbrick:~# vi /etc/apt/sources.list

#deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60
deb http://ftp.pt.debian.org/debian wheezy main contrib non-free
deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Still at the console, run these commands:

ipbrick:~# apt-get update
...

ipbrick:~# apt-get install open-iscsi

== Configuration ==

In order to configure an iSCSI interface please follow these steps:

NOTE: The service configuration is done directly at the server's console as a root user.

The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.

Usually its name is composed by these elements:

iqn + . + year-month + . + server_name + : + custom_string

E.g:

iqn.2012-08.com.domain.ipbrick:fileserver

The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:

...
node.startup = automatic
...

And also the authentication parameters:

- '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:

...
#node.session.auth *
#discovery.sendtargets.auth *
...

- '''WITH AUTHENTICATION - CHAP''':

...
node.session.auth.authmethod = CHAP
...
node.session.auth.username = username
node.session.auth.password = password
...
discovery.sendtargets.auth.authmethod = CHAP
...
discovery.sendtargets.auth.username = username
discovery.sendtargets.auth.password = password
...

NOTE: Please replace username and password by the username and password of your iSCSI Target.

Proceed by stopping and then restarting the iSCSI service - execute:

/etc/init.d/open-iscsi stop
/etc/init.d/open-iscsi start

Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15

Example:

ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78
192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78

Map the Target

ipbrick:~# iscsiadm -m node -l -T "iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78"
Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78,
portal: 192.168.69.15,3260]
Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:
iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful

With a dmesg command it's now possible to see the new disc as a device sdb:

Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)
scsi1 : iSCSI Initiator over TCP/IP
scsi2 : iSCSI Initiator over TCP/IP
scsi3 : iSCSI Initiator over TCP/IP
scsi4 : iSCSI Initiator over TCP/IP
scsi5 : iSCSI Initiator over TCP/IP
scsi6 : iSCSI Initiator over TCP/IP
scsi 5:0:0:0: Direct-Access QNAP
iSCSI Storage 3.1 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:
(53.6 GB/50.0 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 5:0:0:0: [sdb] Write cache:
disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk

If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:

mkfs.ext4 /dev/sdb

fstab mapping is done by device and it can be captured via /dev/sdb

It will be necessary to inscribe it at /etc/fstab

Assuming that this new volume will be used as home3, create its mount point:

mkdir /home3

Map /etc/fstab by executing the nano editor:

nano /etc/fstab

Inscribe the following:

/dev/sdb /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2

Now, you need to run this script so as home3 can be added to the IPBRICK web interface.

/opt/system/scripts/system_add_new_workareas.php 1

You will get the following notification:

Work Area 3 was successfully inserted!
Don't forget to Apply Configurations to commit the changes.

== Firewall ==

Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:

Advanced Configurations -> Network -> Firewall

Click on Insert and create a rule of this type:

Type of configuration to insert: General Settings
Rule: INPUT
Interface: ETHx (The NIC used in the iSCSI connection)
Protocol ALL
Origin IP: [Storage IPs]
Policy: ACCEPT

Click on the Insert button to create the rule

== Manage iSCSI ==

Some useful commands to manage iSCSI on IPBrick:

Restart the openiscsi: /etc/init.d/open-iscsi restart
Check the session status: /etc/init.d/open-iscsi status
Use the dmesg command to find the disc's device;

IPBrick Groupware - iOS

2015-10-25T10:38:24Z

Amachado: Created page with "'''* * * * Página em construção - disponível brevemente * * * *'''"

'''* * * * Página em construção - disponível brevemente * * * *'''

IPBrick Groupware - Android

2015-10-25T10:38:21Z

Amachado: Created page with "'''* * * * Página em construção - disponível brevemente * * * *'''"

'''* * * * Página em construção - disponível brevemente * * * *'''

IPBrick Groupware - Microsoft Outlook

2015-10-25T10:38:17Z

Amachado: Created page with "'''* * * * Página em construção - disponível brevemente * * * *'''"

'''* * * * Página em construção - disponível brevemente * * * *'''

IPBrick Groupware - Mozilla Thunderbird

2015-10-25T10:38:05Z

Amachado: Created page with "'''* * * * Página em construção - disponível brevemente * * * *'''"

'''* * * * Página em construção - disponível brevemente * * * *'''