We are experiencing performance issues, specifically lagging, with the Nextcloud dashboard hosted on a single Ubuntu 22.04 virtual machine (VM). I would appreciate your assistance in identifying the cause of this issue and recommending solutions. Below are the hardware and application details for your reference:
Could you please advise on potential causes of the lagging issue and suggest steps to resolve it? If you need further details, such as server logs, configuration files, or additional system metrics, please let me know, and I will provide them promptly.
Thank you for your assistance. I look forward to your response and hope to resolve this issue as soon as possible.
You didn’t specify what you have already done, in the documentation you can find a number of tip&tricks to improve the performance:
When you experience problems, it can be interesting to use top/iotop to see what resource is used to its maximum (cpu, ram, i/o operations) and try to work on that. Sometime it can also help to check if you have specific resource-hungry apps on Nextcloud, perhaps they can be configured better for your use case to use less resources.
But first, go through the list of optimizations and start there.
This version is not supported any more and receives no security patches. Please update.
I have successfully upgraded Nextcloud to the latest stable version, 31.0.5, on a demo environment containing approximately 10 GB of data. The upgrade completed without any issues, and all files remain intact.
I have two questions before proceeding with the production environment upgrade (which holds around 2 TB of data):
Do I need a separate backup?
When upgrading a large production environment, is there any risk of data corruption or
loss? Should I take a separate backup of the data before proceeding?
What does “Delete old files” mean during the upgrade process?
I came across a step labeled “Delete old files” during the upgrade. Could you please explain
what this step does and whether it’s safe to proceed?
Your guidance on these points would be greatly appreciated.
The update itself touches the code and the database (normally not the data, not sure if there are exceptions). But linked to changes, some cleanup procedure, a client sync or … might get something wrong and delete or alter files.
For upgrades (to new version), I prefer to have a full snapshot of the whole system, so I can go back to exactly what is was before. I suppose you have some sort of backup anyway, question is how long does it take to restore something, and worst case how much is lost (changes since last backup).
Similarly, when I tried to update the “Production Environment,” I got this error. Kindly help me to resolve this. But I have not received it like this when I did the same in the testing environment.
With the command line updater you can disable backup. --no-backup
For normal Backup/Restore read Backup and Restore. Test your Backup/Restore on a test system. You don’t just need a backup in an emergency. You need a functioning backup.
