pfSense

Not sure it works (pfSense-2.0-BETA4-20101201-1616.iso).
I restored my configuration just before midnight, and the RRD directory looks like this now:

rw-r--r- 1 nobody wheel 47608 Dec 2 01:32 WAN-quality.rrd
rw-r--r- 1 nobody wheel 194776 Dec 2 01:31 ipsec-packets.rrd
rw-r--r- 1 nobody wheel 194776 Dec 2 01:31 ipsec-traffic.rrd
rw-r--r- 1 nobody wheel 194776 Dec 2 01:31 lan-packets.rrd
rw-r--r- 1 nobody wheel 194776 Dec 2 01:31 lan-traffic.rrd
rw-r--r- 1 nobody wheel 727424 Dec 2 01:31 system-memory.rrd
rw-r--r- 1 nobody wheel 243328 Dec 2 01:31 system-processor.rrd
rw-r--r- 1 nobody wheel 243328 Dec 2 01:31 system-states.rrd
rw-r--r- 1 root wheel 3465 Dec 1 23:52 updaterrd.sh
rw-r--r- 1 nobody wheel 194776 Dec 2 01:31 wan-packets.rrd
rw-r--r- 1 nobody wheel 47608 Dec 1 23:50 wan-quality.rrd
rw-r--r- 1 nobody wheel 194776 Dec 2 01:31 wan-traffic.rrd

The config file I restored had both a "WAN-quality.rrd" file (listed as the first one in the config file) and a "wan-quality.rrd" file.
As you can see from the dates, only the uppercase file is being updated with new data.
The only other mention of uppercase WAN in the config file is the "descr" field for the "wan" interface.

Well seems ok now.
Chris why do you think this is not fixed?

The quality RRDs are still using the uppercase interface name, where they previously always used lowercase and still should. Hence WAN-quality and wan-quality above.

That is the gateway quality graph not the interfaces one :)
As far as i can tell the interface graphs all use the not uppercase version.

For me, the quality graph was always the offending one.

Well that has changes since long time now.
It is more than 5-6 months it has changed!

Changed to uppercase you mean?
I guess the question is: Should it also be reverted to lowercase?
(I think it should be lowercase since thats what it's always been, and it matches the other interface files)

Well as it is now it cannot use any lowercase name since it uses the gateway name!
Possibly on 2.x++ this can be fixed by giving a reference to the gateways to use in the name. Mostly this is a limitation to what apinger can pass back as information to match the status.

I guess it should be mentioned in the release notes at some point then, as many people will have the problem.

Or preferably, the upgrade/backup restore procedure should simply rename the old lowercase file to uppercase.

FWIW, I user the merge-rrd python script to merge my 2 files together, and it looks like it worked fine.