1509 - Self-hosted storage

This page describes best practices for customers who make use of self-hosted storage. To ensure optimal storage management, we recommend following these guidelines as closely as possible.

If you have any questions for us, please log a support ticket so that a member of our team can advise you.

Page contents

• Security
• OS management
• Networking
• Updates
• Reporting and notifications
• Data sovereignty
• Capacity management
• Legacy clients
• API management

Security

If you want to use signed certificates see Article 1511.

See Article 875 for guidance on how to set the cipher suite on the Storage Platform.

You may also find useful information in Article 1358 - Storage Platform secure ciphers: support for operating systems.

Note: Some self-hosted customers have reported problems with remote tunnel access using ESE v25.4.22. We are currently investigating the problem. In the meantime, we recommend checking that your StorageServer cipher (and possibly protocol) settings are in line with our guidance here.

Console users can still make use of remote access by connecting to the StorageServer through the AccountServer. To do this, enable the field shown in the screenshot below when connecting to your platform. This workaround is unfortunately not possible from the RedApp.

OS management

For security purposes and optimal software performance, it is imperative to stay up to date with operating system updates.

Our System Requirements and Compatibility Matrix contains detailed information about which operating systems and specifications are supported.

Networking

Your inbound connections will need to meet specific requirements. See the Redstor Network Requirements for a list of AccountServer IPs.

Note that incorrectly bound IP addresses can cause connectivity issues to an AccountServer, including if it is an incorrect IPv6 address when trying to use IPv4.

DNS best practices:

• See our DNS best practices for self-hosted StorageServers and MirrorServers on the Redstor Platform in Article 1580.
• See our DNS best practices for self-hosted Storage Platforms in Article 1061.

Updates

Software updates take place according to the Redstor Data Management Platform Maintenance Windows.

If a scheduled update of a StorageServer does not complete successfully, the update can be done manually by following the steps in Article 1515.

Reporting and notifications

For guidance on how to set up reporting and notifications, see Article 107.

Data sovereignty

For some of our services, Redstor processes data regionally to ensure optimal performance and maintain data sovereignty. See Article 1380 for more information.

Capacity management

For best practices regarding storage capacity management, see Article 1510.

Legacy clients

Your data estate may include legacy backup clients. For information on how to approach these, see Article 1548.

API integration

If you are looking to use a REST API in the management of your backups, see

• Article 1549 - How to monitor a StorageServer using an API call
• Article 1193 - How to use the Storage Platform REST API