Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Disk partitioning for Red Hat installation

EcoStruxure IT forum

Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure IT
  • EcoStruxure IT forum
  • Disk partitioning for Red Hat installation
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Cory_McDonald
Admiral Cory_McDonald Admiral
124
Jef
Admiral Jef Admiral
108
gsterling
Captain gsterling Captain
71
APC_Steve
Captain APC_Steve Captain
62
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to EcoStruxure IT forum
Solved
DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

0 Likes
5
1011
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

Disk partitioning for Red Hat installation

Hi Team!

I need your advice about disk partitioning when we need to install DCO on Red Hat.

As per manual disk space should be parted like this:

  • /data is used for indexes and ETL configuration. Minimum size 5 GB.
  • /data/backup is used for backups. Minimum size 50 GB. Backups should always be mounted on a remote network share.
  • /opt/jboss-as is used for the application server. Minimum size 10 GB.
  • /var/lib/pgsql is used for the postgres database. Minimum size 30 GB.
  • /var/log is used for log files. Minimum size 5 GB.

Total size is 100 Gb.

How I need to change this disk space in case I have 400 Gb disk?

Should I expand all disks propotionally or I need expand only /var/lib/pgsql for example?

What is the best practice? Please advice.

(CID:144312273)

Labels
  • Labels:
  • Data Center Operation
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

0 Likes
3
1011
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

Hello Valentin.

Did you use logical volume manager when the above partition layout was created? This decision is made when the CentOS or Redhat host is installed.

If yes, then expanding filesystems at a later time is possible. If not, then its less likely you'll be able to expand the filesystems without having to re-install DCO on a server with the modified partition layout.

Regards

Greg Sterling

(CID:144312345)

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Replies 5
DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

0 Likes
3
1012
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

Hello Valentin.

Did you use logical volume manager when the above partition layout was created? This decision is made when the CentOS or Redhat host is installed.

If yes, then expanding filesystems at a later time is possible. If not, then its less likely you'll be able to expand the filesystems without having to re-install DCO on a server with the modified partition layout.

Regards

Greg Sterling

(CID:144312345)

Reply

Link copied. Please paste this link to share this article on your social media post.

DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

In response to DCIM_Support
0 Likes
0
1011
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

Hi Greg!

Thanks for your answer!

My question is about initial DCO installation from scratch.

What I should say to customer's Linux administrator about disk size?

I'm worry about useful resource usage and afraid situations when we have too much space for ETL and not enough space for DB, for example.

Playing with filesystem on production server is not best option I guess. As well as re-install because of initial mistake.

 

(CID:144312416)

Reply

Link copied. Please paste this link to share this article on your social media post.

DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

In response to DCIM_Support
0 Likes
0
1011
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:43 PM . Last Modified: ‎2024-04-03 02:33 AM

I don't think there is an official "best practice" here as the requirements are sometimes dictated by the customers operating systems policies.

You are correct the user guide makes the following recommendations:

  • /data is used for indexes and ETL configuration. Minimum size 5 GB.
  • /data/backup is used for backups. Minimum size 50 GB. Backups should always be mounted on a remote network share.
  • /opt/jboss-as is used for the application server. Minimum size 10 GB.
  • /var/lib/pgsql is used for the postgres database. Minimum size 30 GB.
  • /var/log is used for log files. Minimum size 5 GB.

That being said, if I run a default installation of DCO on CentOS using our iso you'll end up with something like this:

  • /boot  is 500MB
  • /boot/efi about 200MB
  • swap about 512MB (may change based on the size of the disk)
  • / will own the rest of the disk space

In the above default layout the customer is not defining specific partitions for /opt/jboss-as, and /var/lib/pgsql and so on. In this case if you define a 400GB disk, most of the disk space would remain on the / filesystem and would be available to all of the directories mentioned in the user guide.

There are a couple of reasons to consider defining specific partitions.

  • One would be to protect the app or operating system if a partition becomes full. If the /data partition was full, DCO will have issues but the operating system would continue to run.
  • The other could be performance related if the customer was to choose to separate disk IO's, they could allocate separate disks from an array as the source of the above partitions. So the disk IO's to the /var/lib/pgsql folder would be separated from the disk IO's to the other folders.

If deployed as one disk with the above directories all under the / filesystem, then DCO, Postgres, and the operating system are all sharing/accessing the same disk.

I have worked with customers which require the partitions be split out, others not.

I can tell you the /var/lib/pgsql directory has the postgres database on it so it will grow as your customers configuration grows. /data/backup is the default location for DCO backup files, so if the solution is large this directory could consume a lot of disk space, so make sure if needed you define a cleanup policy in the backups settings in the web client. /var/log contains OS log files and some postgres/dco logs, but most of the dco logs are under /opt/jboss-as

Hope this helps

GregS

(CID:144312427)

Reply

Link copied. Please paste this link to share this article on your social media post.

DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:44 PM . Last Modified: ‎2024-04-03 02:33 AM

In response to DCIM_Support
0 Likes
0
1011
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:44 PM . Last Modified: ‎2024-04-03 02:33 AM

Thank you very much!

 

(CID:144312438)

Reply

Link copied. Please paste this link to share this article on your social media post.

DCIM_Support
Picard DCIM_Support
Picard

Posted: ‎2020-07-05 07:44 PM . Last Modified: ‎2023-10-22 01:54 AM

0 Likes
0
1011
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-07-05 07:44 PM . Last Modified: ‎2023-10-22 01:54 AM

superhero.png

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.

Reply

Link copied. Please paste this link to share this article on your social media post.

To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of