<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://wiki.ipbrick.com/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.ipbrick.com/index.php?action=history&amp;feed=atom&amp;title=IPortalDoc_use_multiple_volumes</id>
		<title>IPortalDoc use multiple volumes - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.ipbrick.com/index.php?action=history&amp;feed=atom&amp;title=IPortalDoc_use_multiple_volumes"/>
		<link rel="alternate" type="text/html" href="https://wiki.ipbrick.com/index.php?title=IPortalDoc_use_multiple_volumes&amp;action=history"/>
		<updated>2026-05-13T13:20:01Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.23.2</generator>

	<entry>
		<id>https://wiki.ipbrick.com/index.php?title=IPortalDoc_use_multiple_volumes&amp;diff=1032&amp;oldid=prev</id>
		<title>Amachado: Created page with &quot;= Motivation = How to rearrange filestorage of an IPBRICK.OS with IPortalDoc.  == Ojectives == * to separate DATA from Operating System (OS) * to allocate filestorage warehous...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.ipbrick.com/index.php?title=IPortalDoc_use_multiple_volumes&amp;diff=1032&amp;oldid=prev"/>
				<updated>2018-04-23T17:59:04Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;= Motivation = How to rearrange filestorage of an IPBRICK.OS with IPortalDoc.  == Ojectives == * to separate DATA from Operating System (OS) * to allocate filestorage warehous...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;= Motivation =&lt;br /&gt;
How to rearrange filestorage of an IPBRICK.OS with IPortalDoc.&lt;br /&gt;
&lt;br /&gt;
== Ojectives ==&lt;br /&gt;
* to separate DATA from Operating System (OS)&lt;br /&gt;
* to allocate filestorage warehouse to a separate volume, a new volume that can grow dynamically&lt;br /&gt;
* to allocate database binaries to a separate volume, a new volume that can grow dynamically, preferencially utilize faster disks&lt;br /&gt;
&lt;br /&gt;
== More Info - LVM ==&lt;br /&gt;
Before proceed we recommed you to read the [[Map new LVM]] section.&lt;br /&gt;
&lt;br /&gt;
= Technical Procedure =&lt;br /&gt;
Overview of the procedure:&lt;br /&gt;
* on-line - without stoping the services&lt;br /&gt;
** to prepare the new volumes (recommendation see [[MAP new LVM]])&lt;br /&gt;
** initial and intermediate synchronizatione the contents from the old to the new volume&lt;br /&gt;
* off-line - stop services and perform the final synchronization &lt;br /&gt;
** stop the services&lt;br /&gt;
** perform final synchronization of contents&lt;br /&gt;
** to replace mount point&lt;br /&gt;
** to restart services&lt;br /&gt;
* validation and final maintenance&lt;br /&gt;
** validate that all services are performing as expected&lt;br /&gt;
** do system maintenance, clean data not used, free old space&lt;br /&gt;
&lt;br /&gt;
== Start Point ==&lt;br /&gt;
For the purpose of this section, we will assume the existence of the following volumes:&lt;br /&gt;
* /dev/sda :: operating system installation&lt;br /&gt;
** Volume Group : /dev/vgsystem1/ :  lvdata1  lvos  lvswap  lvvar&lt;br /&gt;
* /dev/sdb :: disk to be used by database binaries (postgresql)&lt;br /&gt;
** Volume Group : /dev/vgipdocdb/ : lvipdocdb  [ext4]&lt;br /&gt;
* /dev/sdc :: disk to be used by warehouse&lt;br /&gt;
** Volume Group : /dev/vgipdocarm/ : lvipdocarm [ext4]&lt;br /&gt;
&lt;br /&gt;
For more information on the preparation of the new LVM volumes/filesystem please refer to [[MAP new LVM]].&lt;br /&gt;
&lt;br /&gt;
== On-Line ==&lt;br /&gt;
These steps may be executed with the system on-line, in production state.&lt;br /&gt;
&lt;br /&gt;
*TODO*&lt;br /&gt;
&lt;br /&gt;
== Off-Line ==&lt;br /&gt;
These steps imply that service is not available, stop services for final synchronization.&lt;br /&gt;
&lt;br /&gt;
*TODO*&lt;br /&gt;
&lt;br /&gt;
== Final Maintenance ==&lt;br /&gt;
*Todo*&lt;/div&gt;</summary>
		<author><name>Amachado</name></author>	</entry>

	</feed>