server-on-diet.png

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

After running successfully a medium-to-big cluster, one of your concerns is your database keeps growing. If you do not do anything, sooner than later there won't be a server that can host your FusionPBX database.

The good news about this is that it is very easy to know why the database grows so fast. It is logic, more customers, more calls, therefore, your database detailed record grows faster. In technical words, your v_xml_cdr table grows and grows.

Depending on the kind of customers you are hosting, CDR can be very valuable or depreciable. Depending on the country you are, by law, you may be required to store a CDR record somewhere. Somewhere not in your production database. So, your solution is to archive them. If someone asks for them, you will deal with that later.

Read more: Thrid Part: Keep FusionPBX on Diet

server-on-diet.png

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

When you run a successful PBX with FusionPBX, one of your problems is to keep it on diet. Depending on your server sizing, this issue may come soon or later, but it will arrive. I am talking about disk space.

There are two points to cover:

  1. Database
  2. Recordings

Read more: Keep FusionPBX on Diet

server-on-diet.png

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

In my last article (time ago), I publish a way to keep FusionPBX on a diet (by safely deleting recordings and keeping the database with low disk use). But, what about the voicemails?

I will talk now how to delete safely the old voicemails within your policy.

Read more: Second part: Keep FusionPBX on Diet

Subcategories

About

Read about IT, Migration, Business, Money, Marketing and other subjects.

Some subjects: FusionPBX, FreeSWITCH, Linux, Security, Canada, Cryptocurrency, Trading.