I was looking at my WD folders today and noticed that for the months of August, Sept, Oct, Nov, and Dec I had backups created on the first of the month. This appears to be no longer happening. I never set anything up to do this so how can I get it to do the monthly backups again?
Setup - Control Panel - Databackup (3rd line down)
Make sure the switch is on (Green)
Set hour of backup. Mine is at 1 which does a daily backup zip at 1:55AM.
A databackup52004.zip is overwritten daily until the next month where
databackup62004 is created and overwritten daily.
These are located in the “databackup” folder.
Herb
I don’t know if it’s still the case with current versions, but a few users (me for one) have had crashing problems triggered by the backup functionality.
yes I just tried the databackup function for the first time using ver 10.10o and although it created backup files ok when doing it manually, when I set it as a test to do it automatically (at 7:55am in this case) WD crashed after it had been running OK for 10 days - ho hum
ooh gosh that crash screwed up a few settings on my WD as well - like the wind plot direction being generally east when it has been west for the last few days (although since I have restarted WD it is plotting correctly now). And month to date gif having rainfall scale in hundreds of millimetres. And gosh the wind run totals for today, the month and year to date are corrupt.
I did try the convert log files to graphs for May but the crash seems to have altered a few things which I seem to have sorted out - will monitor for a few days.
But have turned off the databackup function again!
I am not complaining though - still a great program 
bristolwx:
any errors under view , program error log, when wd starts?
When I select backup now it’s duplicating some of the files 2 or 3 times. Why? Do I have something set wrong?
Here is a list of the files being backed up:
wdisplay/databackup/wdisplayftp.reg
wdisplay/databackup/wdisplayftp.reg
winnt/wdisplay.ini
wdisplay/databackup/wdisplayftp.reg
winnt/wdisplay.ini
wdisplay/logfiles/52004lg.txt
wdisplay/databackup/wdisplayftp.reg
winnt/wdisplay.ini
wdisplay/logfiles/52004lg.txt
wdisplay/datafiles/latest.inf
wdisplay/databackup/wdisplayftp.reg
winnt/wdisplay.ini
wdisplay/logfiles/52004lg.txt
wdisplay/datafiles/latest.inf
wdisplay/datafiles/month52004.inf
bristolwx: any errors under view , program error log, when wd starts?
Hi Brian,
I have not cleared the error log and the only errors I currently have are
ERROR: Access violation at address 004032AC in module ‘WeatherD.exe’. Read of address 5753571C at time/date 08:32:07 06/05/2004
ERROR: Access violation at address 004032AC in module ‘WeatherD.exe’. Read of address FFFFFFFC at time/date 08:46:45 06/05/2004
which I know were generated when I viewed the metar image to reset the background image on it.
I guess maybe the May datafile got duff data in it somehow when the program crashed - todays windrun value is 484.5 miles for example - would need to be a hurricane going on for that
I guess I could set the month and year to date wind totals to zero again?!
those errors at start up will cause problems
there is not alot of clues there though as to what is causing them
it might be the weather voice or it might be the web cam??
The errors do not show on startup - only if I do view > metar image (which I rarely do) and click on the OK button which does not close the window and generates the error in the log - and does not cause any other problems.
Webcam I don’t use any more and weather talk seems ok.
I have now reset various values that got corrupted back to what they were apart from month/year to date windrun (cos I haven’t really monitored those values so don’t know what they should be - but they are close enough!). I am not too worried about this glitch. Just will remember not to use the databackup function.
Graph wind direction plotting seems to be sorting itself out again after the corruption (it must be in the datafiles (the logfiles seem ok) and over time will get absorbed and forgotten. I won’t want to start afresh.
It is just one of those things.
Keep up the good work Brian
ah
if you have metar logging on, then it might be that the metar log has grown to big
try deleting that file
thanks for the info Brian - will bear it in mind - the crash and corruption was definitely from the databackup function though - so am just keeping an eye on the graph data in the meantime.
I will let you deal with grhughes databackup question above.
well, when i open up my databackup52004.zip, i dont see any duplicates