Hello,
I have the entire Cacti setup on AWS: EC2 Ubuntu 22.04, including SQL. This setup includes all created graphs, data sources, and scripts according to which data in logs on the servers (which are in devices) are monitored. I want to create a backup, or rather a 1:1 copy. How should I proceed? When I migrated from a traditional server to AWS, I had to manually create all the graphs and data sources.
migration Cacti on AWS to other EC2
Moderators: Developers, Moderators
- TheWitness
- Developer
- Posts: 17047
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: migration Cacti on AWS to other EC2
First deploy an empty instance in the new location using the same paths to make it easy and the same cacti version if possible.
Second dump your database in your current production into an SQL file and then import it into the new cacti first dropping the existing cacti database and then importing the dump.
Third start the poler on the new system and let it create the rrd files that already exist in your current production system.
Fourth once you have no more errors in your cacti log on the new system do a final rsync of the rrdfiles from the old production to the new production.
There are other things you'll have to verify in that are that include things like access to email and ensuring that you have SNMP or firewall access to the existing systems from the new location.
If you're using multiple cacti pollers then this situation becomes a little more complicated but not that it cannot be overcome. I just want document it here.
Second dump your database in your current production into an SQL file and then import it into the new cacti first dropping the existing cacti database and then importing the dump.
Third start the poler on the new system and let it create the rrd files that already exist in your current production system.
Fourth once you have no more errors in your cacti log on the new system do a final rsync of the rrdfiles from the old production to the new production.
There are other things you'll have to verify in that are that include things like access to email and ensuring that you have SNMP or firewall access to the existing systems from the new location.
If you're using multiple cacti pollers then this situation becomes a little more complicated but not that it cannot be overcome. I just want document it here.
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Who is online
Users browsing this forum: No registered users and 4 guests