How can we help you today? How can we help you today?

Backup bug - SQL Backup has detected that more recent backup

Just performed a backup using v6 GUI and v6 server components and came across the following issue.

SQL Backup has detected that a more recent backups have used the same backup file.

I always use the <AUTO> option for the file name so was a bit surprised by this. Had a quick check and cant see how this is the case.

The log doesn't show any problems but the GUI is showing 2 files in the same backup??

Bug1.gif
Bug2.gif
Andrew Hodge
0

Comments

7 comments

  • mattchandler
    Hi Andrew,

    Thanks for raising this. This is an issue that we've seen before. Our UI developer hoped he had fixed it in this release, but obviously its still live.

    A workaround for this problem should be to delete the UI data cache - first you will need to close the GUI, and then delete all the files (should be called 1.dat, 2.dat, etc) in the application data. This will probably be found at:
    "C:\Documents and Settings\[your username here]\Local Settings\Application Data\Red Gate\SQL Backup\Server Data"
    or at: "c:\users\[your username here]\Appdata\Local\Red Gate\SQL Backup\Server Data\", on a Vista machine.

    I'd be grateful if you could let us know the details of when this happened. What OS were you using and which version of SQL Serve?. Were you in the middle of doing anything before this issue manifested itself? Any information would be useful.

    There is a registry key that will enable verbose logging in the UI. If possible it would be great if you could: Set the registry key "HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\Client\Full Logging" to "1" (creating 'client' and 'full logging' if they don't already exist), and then send us the log files if this issue happens again.

    Many Thanks,
    mattchandler
    0
  • mattchandler
    I should mention that you are still able to restore the backup, by selecting the file directly, using the folder browser.
    mattchandler
    0
  • Andrew Hodge
    Thanks Matt,

    I saw that I could restore the backup from file

    I deleted the cache and it resolved the issue

    This happened this morning at 9.05am

    Client
    Windows XP SP3

    Server
    Windows Server 2003 SP2
    SQL Server 2000 SP4

    Nothing particularly obvious happening. When I performed another backup 10 minutes later I didnt have a problem.

    I will turn the logging on to see if I can recreate the issue.

    A
    Andrew Hodge
    0
  • Andrew Hodge
    matt,

    I dont have the key HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\ ?

    I created this as well.

    I set the Full Logging to 1 as a string, Started SQL Backup GUI but cant see any logs being created? Where do the logs get created
    Andrew Hodge
    0
  • mattchandler
    Hi Andrew,

    That ought to work, although I should have mentioned that if you're using an x64 machine, the registry should be at:
    HKEY_LOCAL_MACHINE\Software\Wow6432Node\Red Gate\SQL BackupThe log files should be in:
    "C:\Documents and Settings\[your username here]\Local Settings\Application Data\Red Gate\logs\SQL Backup\"
    It ought to be obvious whether the registry key is effective - the log files will grow significantly larger (without the setting we will log very little).

    I hope that helps, sorry I wasn't clearer the first time. Thanks for all your help.
    mattchandler
    0
  • Andrew Hodge
    Tried adding the key but no luck - no logs being created.

    registry.gif
    Andrew Hodge
    0
  • mattchandler
    FullLogging should be all one word (unlike what I wrote earlier - sorry!)

    Hopefully that really should work now! Thank you for your patience.
    mattchandler
    0

Add comment

Please sign in to leave a comment.