![]() ![]() Not fast, but definitely faster than the time it requires the update process to time out. On my NAS, copying this folder takes about 30 seconds. So I cannot say that the migration went smoothly, and a less knowing user might not be able to overcome the problems the way I did.Īs far as I can tell, the backup phase makes a backup of the current Cloud files. For the other steps of the update hoops I disabled the backup phase in advance and all went well. Again, the process aborted on a time-out while making the backup. ![]() The next step was to update from NC12 to NC13. Now the update process completed as expected and I was finally running nextCloud. Since I had made my own backups already I took a hard measure: I eliminated the backup phase from the updater script. just removed the backup and started all over again. ![]() Moreover, the backup process did continue until it reached the end, but there is no way to resume the update process. Inspecting the backup folder it turned out that the process times out when some 20% of the backup was done. The only option was to hit – with the same result. At first it went smoothly, until it reached “Creating backup” (step 4). I cleaned up the ownCloud install a bit, downloaded the updater/index.php as instructed, opened a browser page and started the process. The server is a Synology NAS (DS418) running ownCloud 10.0.10.įirst I was a bit (and unpleasantly) surprised to find out that migration was to go through several hoops, from OC10 via NC12, NC13, NC14 to NC15. As a long term ownCloud user I decided that it was time to bite the bullet and migrate to nextCloud. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |