View source for IPortalDoc use multiple volumes

= 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*