Chat now with support
Chat with Support

QoreStor 6.0.0 - User Guide

Introducing the QoreStor documentation Introducing QoreStor Setting up your QoreStor system Configuring QoreStor settings Managing containers Managing storage groups Managing replications Managing Users Managing QoreStor Remotely Monitoring the QoreStor system Support, maintenance, and troubleshooting

Guidelines for configuring additional storage

Refer to the following important notes and guidelines for understanding storage expansion in QoreStor.

  • QoreStor supports a maximum of 5 enclosures (1 internal plus 4 expansion)
  • QoreStor can only add a mounted filesystem path. QoreStor will not create a filesystem if one is not present.
    • The mounted filesystem should be XFS type.
    • Mount path cannot be read-only.
    • The mount path should not be already configured enclosure path.
  • When adding storage, the filesystem service will be restarted.
  • Storage can be added without being licensed, but an appropriately sized license is required to make the storage usable by QoreStor.
    • Licenses can be added in multiples of Terabytes from 1 TB to the maximum capacity for your QoreStor installation mode.

Adding additional storage

Additional storage can be added through the QoreStor UI or via the system --storage command in the QoreStor CLI. Refer to the QoreStor Command Line Reference Guide for more information on the system --storage command.

IMPORTANT: Adding storage requires QoreStor services to be restarted. This will take the QoreStor server offline for several minutes.

To add storage

Before adding storage, ensure that the storage is mounted to the QoreStor server as an XFS filesystem. Refer to Guidelines for configuring additional storage for additional guidelines and requirements.

  1. In the navigation menu, click Local Storage to expand the menu, then click Storage Groups.
  2. Click Add Storage Location.
  3. Enter the mount path for the additional storage. Click Save.
  4. A warning will be displayed notifying you that a service restart may be required. Click Confirm to continue.

Managing replications

In the QoreStor GUI, you can set up and manage data replication operations. Such replication operations include, creating new replication relationships, managing or deleting existing replication relationships, starting and stopping replication, and displaying current replication statistics.

Guidelines and prerequisites for replication

Refer to the following important notes and guidelines for understanding and using replication in QoreStor.

  • TCP Port Configuration—If you plan to perform replication operations across a firewall, the replication service requires that the following fixed TCP ports be configured to support replication operations:
    • port 9904
    • port 9911
    • port 9915
    • port 9916
  • DMAs and Domain Relationships — To allow replication storage information to be viewed by a corresponding data management application (DMA), the target QoreStor system must reside in the same domain as the source QoreStor system in the replication relationship.
  • Replication Limits — Refer to the QoreStor Interoperability Guide for details about the supported system limits for replication. For a definition of connections and streams, see Streams_vs_Connections.
  • Version Checking — The QoreStor software includes version checking that limits replication only between other QoreStor systems that run the same system software version. If versions are incompatible, the administrator will be notified by an event, and replication will not continue.
  • Storage Capacity and Number of Source Systems — Be aware that the storage capacity of the target QoreStor system is directly affected by the number of source systems writing to its containers, and also by the amount being written by each of these source systems.
  • Bandwidth limiting — Refer to the replication command in the QoreStor Command Line Reference Guide for information regarding limiting bandwidth consumption for replication.
  • MTU Setting — Primary and secondary replication targets should have the same network maximum transmission unit (MTU) setting.

Related Documents