Having server problems on one computer, so I decided I'd migrate to a
new one. Decided that setting up anew was best, and to restore the
database from backups, so I can learn how it works and be sure it is
all good. Now, where do the backups end up? Copied every three hours
from the server which runs a backup job. Hmm, the remote ones seem to
be wrong - they are from last December... Check server, nope, last
December is what it has too! Long story short, I had a bug in my backup
timing that I'd fixed, but not deployed. Now sorted, but I'm rather
glad I had the opportunity to grab these rather critical databases...

--

Matthew Jones

Matthew


OK what had you done - set it up to run once a year or something - enquiring minds (and the terminally nosey) have to know.

Roy Lambert

Roy Lambert wrote:

> OK what had you done - set it up to run once a year or something -
> enquiring minds (and the terminally nosey) have to know.

The code for the timing was all mine, and I'd made a mistake at some
point. This caused it to fail, but not report it in any way. Most of
the change code was to show the last backup.

The daft thing was me fixing it for one installation, and not then
applying it to the other.

I may yet add an email send if it fails again...

--

Matthew Jones

Matthew


That's not daft.

Daft is deciding to delete a few lines of commented code because it had been commented out for a year or so after making a simple code change which was tested but the deletion of the commented code wasn't.

Unfortunately the code had been commented with {} and I didn't notice that there was live code at the end of the last commented line. This was in my email app, removal of this little bit of code (c 24 characters) caused the saving of the decoded email to table to fail. Like a good boy the app logged this - about 6 million times. If it hadn't run out of disk space (if a decode fails I want the entire email in the error log so I can try manually) it would probably still be going and I'd be wondering why no one was talking to me.


Roy Lambert

Roy Lambert wrote:

> had been commented with {} and I didn't notice that there was live
> code at the end of the last commented line.

Ouch! I shan't document my worst bug here... 8-)

--

Matthew Jones

Matthew


The one thing I will say is reviewing the timestamps of my log file I was impressed by the speed with which ElevateDB filled the available space


Roy Lambert