Synology Storage Pool & Volume Best Practices
Best Practices for Synology Storage Pool and Volume for Performance and Safety
One of the most important things you can do is plan out your Synology storage pool and volume layout correctly. Once data starts to grow, backups build up, and snapshots get bigger, it becomes hard and dangerous to undo bad planning.
Storage pools decide how many copies of data there are and how disks are set up. Volumes determine how data is organized and shown. Getting these basics right from the start is important for performance, safety, and long-term growth.
This guide gives you useful tips on how to get the best performance while keeping your data safe.
Know the Difference Between a Storage Pool and a Volume
A storage pool is the RAID-based base where disks are kept together and safe. It sets the level of redundancy, fault tolerance, and how physical disks are used.
A volume is where shared folders, iSCSI targets, applications, and files actually live. It sits on top of a storage pool.
The storage pool is like the engine, and the volume is like the layer of storage that you can use.
Pick the Best RAID Strategy
The first and most important choice is how to set up RAID.
SHR, or Synology Hybrid RAID
SHR is perfect for most small and medium-sized spaces. It lets you use disks of different sizes and makes it easier to add more later. In environments with mixed drives, SHR maximizes usable capacity while keeping redundancy.
RAID 1, RAID 5, RAID 6, and RAID 10
In business settings where predictability and strict performance requirements are important, traditional RAID levels are often preferred.
- RAID 5 protects against drive failures and makes better use of space. RAID 6 adds protection for two drives and is best for larger disk arrays where it takes longer to rebuild. RAID 10 gives you better performance, but it takes away usable space.
- RAID 6 or SHR-2 is often safer for disks that are 10TB or bigger because it takes longer to rebuild them.
- RAID 0 should never be used for production data.
Don’t put different performance levels in the same pool
If you want to use SSDs and HDDs together in the same storage pool, you need to set them up specifically for caching. When you mix drives with different speeds and performance profiles, you get bottlenecks.
If you need SSD caching, set it up on purpose instead of mixing different types of drives in the pool.
Consistency makes things easier to predict and more reliable to rebuild.
Plan the volumes for separating workloads
You can make one big volume, but splitting volumes by workload often makes management and resilience better.
For instance:
- One volume for folders that everyone can use
- One backup volume
- One volume for iSCSI or virtualization
- One volume for storing surveillance data
This method lets you change snapshot schedules, retention policies, and performance monitoring for each workload.
It also lowers the chance of resource contention.
Use Btrfs to protect your data
Choose Btrfs as the file system for volumes when you can.
Btrfs makes it possible to:
- Copying snapshots
- Checksums for data integrity
- The ability to heal itself
- Options for granular restore
These features make it much harder for silent corruption and ransomware to happen.
Btrfs is highly recommended for environments that put safety and recovery flexibility first.
Don’t let storage usage go over 80%
When volumes get close to full capacity, performance drops and snapshots don’t work as well.
Snapshots need space to keep track of metadata and versions. When storage is more than 80% full, the risk goes up and the ability to recover goes down. Before reaching critical levels, expand or archive proactively.
Allow Regular Scrubbing
Data scrubbing checks the consistency of RAID and finds hidden disk errors.
For systems with high availability, schedule scrubbing once a month. For smaller systems, do it once every three months.
Scrubbing makes sure that rebuilding is reliable and finds disks that are about to fail before they do.
Care more about your snapshot strategy
Taking pictures often protects against ransomware and accidental deletion.
Best practice:
- Five-minute snapshots of important documents
- Hourly pictures of shared data
- Daily snapshots for long-term storage
- Replication offsite for disaster recovery
You should never use snapshots instead of backups, but they do let you roll back right away.
Check the health of your drive and the resources on your system
Use DSM’s Resource Monitor and Storage Manager on a regular basis.
Look out for:
- Warnings from SMART
- Sectors that have been moved
- Latency on the disk is high.
- CPU saturation while indexing or virtualizing
RAID design is only one part of storage performance. It also has to do with keeping an eye on things ahead of time.
When to Make Separate Pools Instead of Adding to Them
It may seem easier to extend one big pool, but if corruption happens, the blast radius gets bigger.
Making separate storage pools for different departments or functions reduces risk and makes it easier to fix problems.
In bigger places, separate pools also let you replace hardware at different times.
Combine your pool design with your backup plan.
Never depend on RAID alone for safety
RAID keeps your disks from failing. It doesn’t keep you safe from:
- Ransomware and mistakes made by people
- Malicious deletion and natural disasters
Along with your pool strategy, use Hyper Backup, Snapshot Replication, and offsite replication.
Don’t just think about uptime when designing storage architecture; think about recoverability as well.
About Epis Technology
Epis Technology looks at storage pool configurations based on the type of workload, the expected performance, and the rules that must be followed. The team plans how to use RAID in a way that supports business continuity, sets up snapshot schedules, and includes backup and replication frameworks in the planning of storage architecture. By making sure that volume segmentation matches real operational needs, Epis Technology makes sure that systems can grow over time without putting safety at risk.