1. Table of Contents

1. Service Direction / Introduction / Scope
2. Service Transparency
3. Definitions
4. Description of Content
5. Common Mistakes
6. Responsibility Breakdown
7. Limitations
8. Support Information
9. FAQ
10. Summary
11. Use Case

2. Service Direction / Introduction / Scope

iCoreHosting provides RAID configuration options to help increase data redundancy and reduce downtime caused by individual disk failures. RAID is designed to allow a server to continue running when certain disks fail, depending on the RAID level used.

Despite its benefits, RAID is not an absolute protection mechanism. It is important for all clients to understand that RAID does not prevent data loss, does not guarantee server stability, and does not replace a proper backup strategy. This document outlines the scope, limitations, and responsibilities associated with RAID usage to ensure clarity and prevent misunderstandings.

3. Service Transparency

RAID helps reduce impact from physical disk failure but cannot protect against numerous other causes of data loss. Clients must not treat RAID as a guarantee or rely on it as the sole protection method. RAID configurations are provided as a best-effort redundancy feature, not as a data protection service.

RAID also does not guarantee:

• Data accuracy or data integrity
• Protection from file system corruption
• Protection from malware or ransomware
• Protection when multiple disks fail simultaneously
• Successful rebuild after disk replacement
• Application-level or OS-level failures

RAID simply increases tolerance against single-disk failures but carries its own risks, including rebuild errors and performance slowdown during rebuild.

4. Definitions

• RAID: A disk array method designed to provide redundancy or improved performance.
• Redundancy: The ability for a system to continue functioning despite a disk failure.
• Rebuild: The process of restoring RAID integrity after replacing a failed disk, which may take hours or days.
• Degraded Mode: A condition where the RAID is still running but in a vulnerable state.
• Disk Failure: When a physical drive is no longer able to operate normally, causing RAID degradation.

5. Description of Content

When RAID is configured on a dedicated server, the following operational behaviors should be expected:

1. Disk Failure Handling

   RAID may allow the server to remain online when a disk fails. However, the performance may degrade significantly, and the risk of total failure increases until the disk is replaced and the RAID has fully rebuilt.

2. Rebuild Process

   • Rebuild time depends on the RAID level, number of disks, disk size, and server load.
   • Rebuild time may take from several hours to more than 48 hours.
   • High server load may cause rebuild to slow down or fail.
   • Rebuild failure may cause complete data loss.

3. Disk Replacement Workflow

   • iCoreHosting replaces failed disks based on service plan and hardware availability.
   • Rebuild begins only after replacement and requires adequate free system resources.

4. Client Monitoring Requirements

   Clients are responsible for monitoring RAID warnings, system notifications, and SMART errors. Ignoring early warnings significantly increases the risk of permanent data loss.

11. Common Mistakes

• Believing RAID eliminates the need for external backups
• Assuming RAID guarantees 100% uptime
• Delaying disk replacement after receiving alerts
• Running the server under high load during RAID rebuild
• Ignoring degraded mode warnings
• Using RAID for mission-critical systems without proper backup planning

14. Responsibility Breakdown

iCoreHosting Responsibilities

• Perform initial RAID setup during server deployment
• Enable RAID health monitoring tools and alert configuration
• Replace failed physical disks based on service coverage
• Ensure hardware components operate within normal thresholds

Client Responsibilities

• Maintain up-to-date email addresses to receive RAID alerts
• Monitor all RAID health warnings and disk failure notifications
• Respond promptly to RAID DEGRADED alerts
• Immediately report RAID DEGRADED status or disk failure to iCoreHosting
• Maintain external backups at all times
• Understand that RAID is not a guarantee and does not prevent data loss
• Acknowledge that failure to monitor or report RAID issues may result in data loss, which is not the responsibility of iCoreHosting

16. Limitations

The following are important limitations of RAID which all clients must acknowledge:

• RAID does not guarantee data integrity or accuracy
• RAID cannot prevent data loss caused by OS-level corruption or software bugs
• RAID cannot guarantee successful rebuild after disk replacement
• Multiple disk failures can occur at any time and cause total data loss
• Rebuild may stress remaining disks and cause additional failures
• No RAID configuration replaces a proper backup system
• iCoreHosting is not liable for RAID-related data loss, corruption, or downtime

17. Support Information

Disk replacement and RAID status checks are provided based on your service plan. RAID rebuild, data recovery, or file system repair are not included under standard support scopes.

Clients requiring advanced data recovery services should engage a professional data recovery provider.

18. FAQ

Q1: Does RAID guarantee my data is safe?
A: No. RAID only reduces risk from physical disk failure. It does not prevent corruption, rebuild failure, accidental deletion, or malware.

Q2: If RAID rebuild fails, who is responsible?
A: The client is responsible for data protection and backups. iCoreHosting is not liable for rebuild failure or data loss.

Q3: Can RAID continue running if two disks fail?
A: No RAID type can guarantee operation if multiple disks fail unexpectedly.

Q4: Will iCoreHosting recover my data if RAID crashes?
A: No. Data recovery is not included and must be handled by a third-party recovery specialist.

Q5: Does RAID slow down during rebuild?
A: Yes. Rebuild can significantly impact performance and stability.

Q6: Can I run my server normally during a rebuild?
A: Although possible, it increases the risk of rebuild failure. Clients should reduce server load during rebuild.

19. Summary

RAID provides additional redundancy but is not a guaranteed protection method. iCoreHosting is responsible for hardware replacement, but clients remain fully responsible for their data, backups, and operational stability. RAID failures, degraded mode, rebuild failures, and related data loss fall entirely under the client’s responsibility.

20. Use Case

• General-purpose servers requiring basic redundancy
• Web hosting environments with moderate read/write loads
• Applications with proper external backup and versioning systems
• Environments where uptime is important but data protection is handled separately