---
title: "StellarOne 3.3 Upgrade Frequently Asked Questions"
slug: "stellarone-3-3-upgrade-frequently-asked-questions"
description: "EndpointProtection/StellarSeries/ready_to_release/HelpCenter"
updated: 2026-04-22T13:47:52Z
published: 2026-04-22T13:47:52Z
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.txone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# StellarOne 3.3 Upgrade Frequently Asked Questions

### **Summary**

---

This article provides answers to the most frequently asked questions regarding the upgrade process to StellarOne version 3.3, including key requirements, expected changes, and common troubleshooting guidance.

#### **1. What version must my system be on before upgrading to 3.3?**

- Your system must already be running StellarOne 3.2.5. Upgrades from earlier versions are not supported.

#### **2. Why is version 3.2.5 required before upgrading?**

- Version 3.2.5 ensures migration verification, resource validation, and improved upgrade visibility including firmware progress tracking.

#### **3. Do I need to perform a backup before upgrading?**

- Yes. A full backup is required to protect system and database data stored on the second disk.

#### **4. What are the disk space requirements for StellarOne 3.3?**

- OS Disk: 15 GB free space, 35 GB total minimum. System + Database disk requires at least 5 GB free and 30 percent free on the DB partition.

#### **5. What are the memory requirements?**

- Minimum 8 GB for systems with up to 3 years of data retention. Additional memory increases based on retention duration for Agent Events, Server Events, and Audit System Logs.

| Data Retention | Minimum Memory |
| --- | --- |
| ≤ 3 years | 8 GB |
| 4 years | 9 GB |
| 5 years | 10 GB |
| 6 years | 11 GB |
| 7 years | 12 GB |
| 8 years | 13 GB |
| 9 years | 14 GB |
| 10 years | 15 GB |

#### **6. What pre-upgrade steps should I follow?**

- Verify that your system is running version 3.2.5, confirm Agent Event migration, ensure adequate disk and memory resources, and perform a full backup.

#### **7. What if the OS disk does not have enough space?**

- Reboot to clear temporary files. Expand Disk 1 if you need more space.

#### **8. What if the database or system partition is full?**

- Perform manual log purge, delete unused patch files, expand Disk 2, or contact Support if expansion is not possible.

#### **9. What if I receive an “Insufficient Memory” error?**

- Increase memory based on the data retention requirement table.

#### 10. What if Agent Event migration is still in progress?

- Wait for the migration progress bar to finish, then retry the upgrade.

#### 11. What if I see a “Database Table Abnormality” error?

- Contact Support immediately. Do not continue the upgrade.

#### 12. What if the DB upgrade fails during firmware upgrade?

- Contact Support immediately. Do not retry the upgrade.

For support assistance, please contact us at support@txone.com or your Support Provider.