How do I increase disk space on AWS EC2?

[swiftechinc]

I found an article a while back that walked through the steps of increasing disk space for 3CX on Amazon EC2 but at the time I didn't need it. I bookmarked it but I got a bit over-zealous when cleaning up bookmarks a while back and must have deleted it. Now I need to increase the disk space and can't find that article. I've shut it down, increased the storage and fired it back up but it still appears to be limited to the initial size that was installed. If I remember correctly, there was a way to do it without resorting to a backup, destroy, restore process. which makes me nervous. Anyone know how to do this?

 

[Alphabetic]

You would need either linux or windows knowledge on increase partitions. Though, you would be better off with a backup and restore. I posted something ages ago on using GParted to increase the partitions, do a search you may find it.

 

[swiftechinc]

You would need either linux or windows knowledge on increase partitions. Though, you would be better off with a backup and restore. I posted something ages ago on using GParted to increase the partitions, do a search you may find it.

Thanks. I'm a Windows guy that runs Linux systems following directions online more than I should because, well, it's often the better choice.... But I don't do it often enough to feel comfortable in this case. lol

Unless someone else shows up with a magic wand today, I'm just going to run a backup, a couple of them, and make copies in a few different places just in case. Restoring from backups has been a solution of last resort for me, always taking 4x as long as planned, even when I planned 4x longer than I thought. I'm still reeling from an HTPC failure last year where 3TB of movies, music, and photography work were on a drive that was replicating to another drive using MS Sync Toy. The primary drive failed, and the backup began failing as I was copying it all to a new drive three days later. I only recovered about 40% over 6 days before it completely failed.

Maybe there was no clean and easy magical solution. Or perhaps the backup/restore in this case was it... Perhaps I'll be delightfully surprised when it goes well. I guess I'll find out late tonight. If I return here at 4am with incoherent ranting, just ignore me. :-D

 

[Alphabetic]

If you've done a backup then theres no harm in giving this a go. It will be considerable quicker.

https://www.3cx.com/community/threads/increasing-partition-on-virtual-debian-install-guide.81782/

 

[swiftechinc]

If you've done a backup then theres no harm in giving this a go. It will be considerable quicker.

https://www.3cx.com/community/threads/increasing-partition-on-virtual-debian-install-guide.81782/

Well, not if I throw some confusion into it and try to move it over to Lightsail to get more disk space for the dollar and prevent having to do it yet again later. And I'm sure I can find more ways to make it even more complex....OK. I'm not looking to make it difficult. But I think I may see if I can spin up a Lightsail instance and import the system to it before I tear down the other. I figure that if it works, then I don't have to worry about it, and if it doesn't, I can just pretend that I never tried.

 

[Alphabetic]

You could fire up your 2nd instance on Lightsail and set it up as your standby server then failover to it.

 

[swiftechinc]

Yeah. That's what I'm thinking. Working on some billing stuff right now but when I get done I'm gonna hop over and see what all that involves. I've never ran with a failover on 3cx but I may as well learn now. It's gonna require a separate IP and I know the IP for the 3cx subdomain can be set within 3cx. I'm not sure if we're using IP authentication or not at Flowroute so I need to get that information together. And I'm not sure if Flowroute can set a backup path. There's a lot of questions I have about that, whether I can make it an automated redundant failover or if I would need to manually login to make changes if the primary goes down. Sounds like a fun little learning project.

 

[ChrisC_3CX]

Just want to add that there are a few things you should keep in mind:

• When setting up a 3CX Failover configuration we always recommend deploying the passive instance first. This is due to the fact that you have to deploy the machine first before switching over to passive, meaning that if you already have a PBX running, installing the new PBX to have it act as the passive server will update the DNS record automatically to its IP. This provided of course that you're using a 3CX FQDN.

• DNS TTL will also play a role here so bear in mind that for the ENT license DNS TTL is 5 minutes whereas for PRO and STD it is 6 hours. If you manage the network for all 3CX remote sites you might want to consider configuring them to use Google's DNS to speedup DNS global propagation.

• The default template we have for Flowroute sets them up as a Register based SIP Trunk so there's a good chance they do not need your IP to authenticate but contacting them to make sure would be a good idea.

• Regarding how it works, to put it simply the Passive server monitors certain 3CX Services of the primary server and will automatically switch itself to active if one or all of those services stop responding so there's nothing you have to do manually if it was setup properly to begin with such as setting up scheduled backups on the primary and scheduled restore tasks on the passive to keep it up to date in regards to configuration.

You might want to check out the guide here: https://www.3cx.com/docs/failover/

I hope you find this information useful. Do let us know if you need anything else.