RRD Data Download & Restore



  • Under "Diagnostics: Backup/restore", is there a way to backup/restore ONLY the RRD data?

    The reason is that when I update from 1.2.3 to 2.0, the RRD data seems to get messed up or get lost on some systems.

    I can always easily recreate my configuration from my notes or memory, but trying to recreate the RRD data is next to impossible.

    I just want to have a clean install of 2.0 and then ONLY restore the RRD data.

    thanks..



  • Are you running the embedded version.  If so, then the upgrade doesn't work correctly on some of the RRD data, as it collects more data on 2.0, and so the files need massaging as part of the upgrade.  That part doesn't work correctly on 2.0 upgrades.

    Wait for 2.0.1, which I believe is due soon.  Or at least that's what I was told after I verified that the version fixes this bug.  ;D

    Update
    You could always load the Backup package, which will allow you to back up the RRD data.  However, I don't know if restoring it on a 2.0 system would trigger the upgrade of the data to the new format.

    Maybe someone more knowledgeable can answer that part.

    Cheers.



  • It would be great to have the option of ONLY backing up OR restoring the RRD data without touching or possibly screwing up an otherwise stable setup.

    With such a setup, I can safely swap a nanobsd setup with a full install without having to choose whether to lose the RRD stats or messing the entire configuration as there appears to be some issues when swapping configuration data w/ different pfSense versions and build-types.



  • @EddieA:

    You could always load the Backup package, which will allow you to back up the RRD data.

    And restore.

    Update
    I just notice you also mentioned build types.  You cannot move i386 RRD data to AMD64, and vice-versa.

    And note what I said about the 1.2.3 -> 2.0 needing to massage the data, so moving between releases may not always work either.

    Cheers.



  • @blewis:

    With such a setup, I can safely swap a nanobsd setup with a full install without having to choose whether to lose the RRD stats or messing the entire configuration as there appears to be some issues when swapping configuration data w/ different pfSense versions and build-types.

    There is no difference in the config between versions or build types, with the exception of if you're switching architectures (i386 to amd64 or vice versa) and that's only with RRD data. You can paste in the backed up RRD XML into a different config to restore.



  • @cmb:

    You can paste in the backed up RRD XML into a different config to restore.

    Yeah, I was forgetting that you can export the RRD data, I wouldn't call it a backup, to XML and import that back.  But that would be more work, and it's not how the backup package works.

    I'm guessing you might be able to do that between architectures, but between releases you'd have to know the differences and modify the data.  You'd essentially have to do what the upgrade process does.

    Cheers.



  • @cmb:

    @blewis:

    With such a setup, I can safely swap a nanobsd setup with a full install without having to choose whether to lose the RRD stats or messing the entire configuration as there appears to be some issues when swapping configuration data w/ different pfSense versions and build-types.

    There is no difference in the config between versions or build types, with the exception of if you're switching architectures (i386 to amd64 or vice versa) and that's only with RRD data. You can paste in the backed up RRD XML into a different config to restore.

    Does this mean that let's say I d/l the config (w/ RRD data) from pfSense 1.2.3 and I can simply copy & paste the RRD data using NotePad++ to a newer config from pfSense 2.0. The config XML does not have any internal checksum protection to make sure it's valid?

    Also, can it be the reason why there is not the feature to save only the RRD data is because the i386 RRD data is NOT COMPATIBLE w/ the AMD64 RRD data?  Will you be making or is it even possible to make the two interchangeable?

    Thanks!



  • @blewis:

    Does this mean that let's say I d/l the config (w/ RRD data) from pfSense 1.2.3 and I can simply copy & paste the RRD data using NotePad++ to a newer config from pfSense 2.0. The config XML does not have any internal checksum protection to make sure it's valid?

    That's only possible from the same version. 1.2.3 had no ability to put the RRD data in the config, and its RRD format is different, won't work without going through the upgrade process that happens during the 1.2.3 to 2.0 config upgrade.

    @blewis:

    Also, can it be the reason why there is not the feature to save only the RRD data is because the i386 RRD data is NOT COMPATIBLE w/ the AMD64 RRD data?  Will you be making or is it even possible to make the two interchangeable?

    That's just the way rrdtool works, we don't develop it or maintain it or have any control over it. We've discussed options for automatically converting it, but there is a major catch 22 there that makes it a real nightmare, so we have no plans to accommodate that. It is possible to manually convert, there is info in the mailing list archive on that.



  • Than you for the explanation, cmb!

    I had never expected saving/importing/exporting ONLY the RRD data can be so troublesome…

    The packages that I tested does not have this capability as well.

    A few years ago I wouldn't even care to look at the RRD Traffic graphs as it didn't affected me, I guess time has definitely changed.  But now with monthly CAPS imposed by many-to-most major ISPs around the world, who can afford NOT to ignore how much traffic one uses.  Overages can be quite expensive!


Log in to reply