Cloudron Forum

@fbartels said in Backups and users: Cloudron treats user names as unique Yes, we used to uuid and then went and changed all the apps to use username so that migration from one Cloudron to another (or anywhere else) is easier. As long as the username exists on the other cloudron, user should be able to login.

@plains-digital yes, you can also restore app by app. https://docs.cloudron.io/backups/#import-app-backup . But obviously, restoring entire server via backup is far simpler.

I have not used VMWare tools extensively, but I think you can do the below Take a full Cloudron backups before you do anything. I think the best approach is to simply use VMware snapshots. Snapshot the VM. Move/copy the snapshot to the end destination and create a new VM again from snapshot. Depending on your setup, maybe the move/copy is redundant. As I said, I don't really know much about the VMware tools. Change the IP address of the dashboard my.cloudron.example to the new IP manually. i.e via your DNS provider. Start the the new VM. You should be able to visit my.cloudron.example already and login Once you visit, go to Domains -> Sync DNS. This will resync all the DNS entries with the new IP automatically. That should be it, I guess. If something goes bad, please let us know here and you can always start up the old instance immediately and continue.

@luckow thanks for your input @luckow said in Merging mulitple Cloudrons in to one big new one?: why? In part just so everything in one place and so I just have to manage, maintain, update etc one server instead of several servers. But also because e.g. I've got an instance of PeerTube on one of the smaller VPSs (it's bridport.tv so makes sense to have it on my.bridport.coop where I've got all the Bridport stuff), but I've realised that it really needs a lot more power than that server has. I'd also like to give access to some of the apps of got on my.uniteddiversity.coop to all the people on my.bridport.coop - at present this would mean them creating another account and then not having the same credentials for both (although to be fair most of the apps currently on my.bridport.coop aren't LDAP enabled anyway, either because they don't have it - like Discourse - or because it doesn't really suit the use case - public instances of PeerTube, Mastodon, Pixelfed). I think quite a few of the apps would likely benefit for the increased power the dedicated server would have. The issues you've highlighted wouldn't be that big an issue for me because I think I'm currently the only person/ name who is on all of them so there aren't two Jane Does (but there would be if I started saying "sign-up over on my.uniteddiversity.coop so I can give you access to our shared x too". The biggest issue would be getting the handful of people actively using some of the other Cloudrons over onto the One Big Cloudron, but currently the numbers of people I'm talking about would be manageable (but this gets harder as more people start joining the other secondary Cloudrons).

@jdaviescoates said in Server migration tips? Need same ubuntu version? Possible to do without downtime?: I guess I could try: add the ip of my old server to my /etc/hosts file on my laptop so I can access it again post DNS changes boot up my old server and run a backup Then try the restore email thing linked above by copying the relevant files from one server to the other (not sure how exactly I'd do that, I guess maybe with scp or something) But I wonder if another option would be to add the ip of my old server to my /etc/hosts file on my laptop so I can access it again post DNS changes boot up my old server and run a backup restore this new backup of the old server into the new server (although I guess this could now get messy - what would happen with emails that have since arrived on the new server). I'd recommend the first option there to avoid overriding any emails on the new server which aren't on the old server. The first steps would be good because then you'd get a backup again you can follow the steps from the docs at that point to restore emails, essentially merging with the new server afterwards. Definitely will be interested if @staff has any other recommendations though, will be good to know for future.

@eddowding said in Updating Cloudron to a stable version: I was migrating servers when I noticed that I'm on 7.2.5, but the latest is 7.3.2. When moving to the new server, you can install it as ./cloudron-setup --version 7.2.5 . 7.3 was out last week, just ironing out some regressions. We expect to start rolling it out next week.

@humptydumpty Thank you, that has actually worked!

@samaneha Which app do you want to migrate? The backups have the database dump and the data files. What else do you need to migrate?

Backup/Restore process is actually better than a disk clone as it allows for one to remove the older cruft, upgrade the OS, switch hardware, etc.. yet all the Apps and Cloudron instance settings work as originally backed up. Very handy and a seriously difficult thing to do, hence the many disk imaging and other schemes to try and replicate a nicely configured system, which quickly become out of date, being so static. Cloudron FTW!

@girish I think it was ultimately a disk space issue - I restarted unbound and that seemed to do the trick. I have to move servers again because of a Vultr restriction (block storage not in the zone I had the VM in) that's unrelated to Cloudron so I'll see what happens. Thanks guys!

@LeeW Thanks for trying it and letting us know!

thanks for proving my point that one cannot have a discussion with you

@timconsidine said in Moving Cloudron to new server : stop apps?: that I didn't set the PTR record in the new VPS provider until I started the migration I ran into exactly this problem the last time as well

@atridad yeah, I just bumped the internal default for data directory migration to be 1GB . I tested with ~500GB now and it's all good.

@girish Thanks for the info and all the work (support) you have done for me Girish

@shai you have to build a custom app, please see this guide https://docs.cloudron.io/guides/multiple-databases-lamp/

@brutalbirdie Thank you, I'll give that a shot!

Thanks guys! Yeah it's a weird issue for sure and likely very rare, so it's probably not a big deal. If it helps for reproducing it, here's a few notes: 27 apps installed at the time of backup/restore Backup & Restore used tgz format with OVH Object Storage in BHS region Backup from a LunaNode m.8 model in Toronto region Restored onto OVH b2-7 model (though since upgraded to b2-15) in BHS3 region LunaNode instance (source) was running Ubuntu 18.04 at backup time, and OVH instance (target) was running Ubuntu 20.04 at the time of restore. When I restored, I very nearly ran out of disk space on the included disk, leaving only ~ 1.5 GB of space remaining. When restoring initially, it failed to restore because of the issue I reported earlier, though doubtful this is a root cause. Immediately moved the boxdata to external disk afterwards though, so plenty of space free soon after the restore was done once I moved boxdata off (20 GB in emails alone so it takes up a lot of space). Hopefully those notes above help in some small way. No worries though if you can't reproduce it, I imagine it's a very rare scenario and could have even been completely unique to me somehow. Hopefully others can chime in though if they experienced anything similar where cron wouldn't run at all (whether a restore involved or not, as I'm still not 100% certain it had to do with the restore though I presume it did).

One other note, the .sql file originally failed to upload due to the dump having the following line: Create SCHEMA public; I commented that out and the import ran fine. I'm guessing there is a command to dump the Postgres DB without a create statement but someone smarter than me probably knows it. I haven't used Postgres a day in my life until yesterday so I'm still getting to know it. I have only used MySQL, Maria and MS SQL and all of those have an option to dump without the create statement, but I figured it was just easier to comment that line out of the SQL file instead of looking up the command and doing a new dump.