Article ID: 117633, created on Oct 1, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo


The purpose of this video is to give you an overview of converting your regular storage into a redundant and highly available cloud with the help of Parallels Cloud Storage.

This video is the part of Parallels Cloud Storage course:



Cluster Configuration


Minimal configuration for functional testing only:

  • 1 chunk server
  • 1 metadata server
  • 1 client


  • 5+ chunk servers
  • 3+ metadata servers
  • 1+ client

Your text to link here... Your text to link here...

Amount of physical servers and roles distributions affect cluster performance and redundancy:

  • More chunk servers (CS) (9 is optimal):
    • higher redundancy
    • faster recovery
    • better read and write operations performance
    • higher capacity

-More metadata servers (MDS) (3 or 5 is optimal): - better availability - higher fault tolerance

-More client machines (Parallels Cloud Server hosts): - more virtual environments to run

Hardware Configuration

Metadata Server

Metadata server is RAM-intensive

Chunk Server

Chunk server is HDD-intensive


Client machines are CPU and RAM-intensive

  • Consider resource distribution while combining several roles on one machine
  • Consider using SSD drives for:
    • Write journaling on Chunk Servers
    • Data caching on client machines
  • Use SSD drives with enhanced power-loss data protection
  • Verify hardware prior going to production
  • Consider general requirements for Parallels Cloud Server
  • Use separate physical network for storage traffic
    • Security purposes: storage traffic is not encrypted
    • Performance purposes: internet bandwidth should not be affected by heavy storage traffic
  • Consider amount of physical disks to choose the speed of Ethernet network:
    • 1 Gbps Ethernet for up to 2 HDDs per node
    • 10 Gbps Ethernet for 2 and more HDDs per node

Cluster Discovery

DNS service - recommended

  • Secure
  • Centralized
  • Automated

Zeroconf - not recommended

  • Insecure


  • Can be used for quick tests and troubleshooting

Install Parallels Cloud Storage Services

Install MDS Role

Setting Up the First Metadata Server

  1. Install RPM package:

    ~# yum install pstorage-metadata-server
  2. Enable MDS service: On first server in cluster:

    ~# pstorage -c clustername1 make-mds -I -a -r /pstorage/clustername1-mds -p

    On next servers:

    ~# pstorage -c clustername1 make-mds -a -r /pstorage/clustername1-mds -p
    ~# pstorage -c clustername1 make-mds -a -r /pstorage/clustername1-mds -p
  3. Configure MDS service automatic startup:

    ~# service pstorage-mdsd start
    ~# chkconfig pstorage-mdsd on

Install CS Role

Setting Up Chunk Servers

  1. Install RPM package:

    ~# yum install pstorage-chunk-server
  2. Authenticate to cluster:

    ~# pstorage -c clustername1 auth-node
  3. Enable CS service:

    ~# pstorage -c clustername1 make-cs -r /pstorage/clustername1-cs -t 1
  4. Configure CS service automatic startup:

    ~# service pstorage-csd start
    ~# chkconfig pstorage-csd on

Install Client Role

Setting Up Clients

  1. Install RPM package:

    ~# yum install pstorage-client
  2. Create storage mount point:

    ~# mkdir -p /pstorage/clustername1
  3. Authenticate to cluster:

    ~# pstorage -c clustername1 auth-node
  4. Mount storage:

    ~# pstorage-mount -c clustername1 /pstorage/clustername1
  5. Add storage to /etc/fstab:

    pstorage://clustername1 /pstorage/clustername1 fuse.pstorage rw,nosuid,nodev 0 0

Configure Virtualization Services

  1. Check default virtual environments path:

    • Containers:

      ~# grep VE_PRIVATE /etc/vz/vz.conf
    • Virtual machines:

      ~# prlsrvctl info | grep “VM home”
  2. Copy existing environments to Cloud Storage:

    • Containers (must be in ploop format):

      ~# cp -pr /vz/private/ /pstorage/clustername1/private
    • Virtual machines:

      ~# cp -pr /var/parallels /pstorage/clustername1/vmprivate
  3. Create symbolic links to Cloud Storage

Additional Information

pstorage-hwflush-check manual

Documentation Portal

Official product page

Search Words

add hwnode to cluster


0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF