Nextcloud for business: plan storage, backups and users
A shared file service works well when storage, access and recovery match daily work. Start with your team's data and workflows. These determine the capacity, user groups and operational requirements you actually need.
Measure your data and allow for growth
Measure current storage use by department and project. Separate active working files from older material that does not need daily synchronisation. Consider both large numbers of small files and large individual files, as they place different demands on synchronisation and processing.
For illustration, 300 GB of initial data growing by an assumed 10 GB per month would reach about 420 GB after a year, before allowing for versions, trash, previews and headroom. Replace these assumptions with your team's figures. A plan sized exactly at that limit would leave little room for growth.
Plan groups before individual shares
For each shared data area, decide who may read, edit and change permissions. Groups organised by responsibility are usually easier to maintain than many individual permissions. Assign owners to project folders so shares remain accountable when staff change.
Agree how to handle external recipients, expiry dates and passwords for shared links. Offboarding includes device connections, existing shares and handing over business files as well as disabling access. Test these rules with an ordinary user account rather than only as an administrator.
Synchronisation and backups serve different purposes
A synchronised device also receives changes and deletions. It is therefore not a reliable substitute for a separate backup. Versions and trash can help with everyday mistakes; restoring the whole installation also requires an appropriate backup process.
Nextcloud identifies the database, configuration, any custom apps and the theme as relevant alongside the files. They need to form a consistent set. NUXOA managed plans include seven daily onsite backups and two weekly offsite backups. Three-copy Ceph replication complements these backups but does not replace copies from different points in time.
Performance depends on usage
When choosing server resources, consider active users and applications as well as total account count. Large uploads, many previews, search and additional apps create their own workloads. Collaborative document editing and video meetings should be considered additional services with their own requirements.
Start with a pilot group from different departments. Test typical files, mobile access, external sharing and recovery of an accidentally deleted file. Record the results and select the plan accordingly. User count alone is not a reliable measure of the CPU or RAM required.
Checklist before migration
- Document data volume and growth; allow headroom for versions and trash.
- Define groups, folder owners and external sharing rules.
- Review extra services such as Office and Talk, and each integration.
- Agree pilot testing, cut-over, backup verification and rollback.