A workaround if the GUI reports Verify incorrectly
HJoyce
Posts: 186
The VERIFY keyword is specified, a procedure is run after the backup process to check the backup file is not corrupted and can be read for restoring.
After the backup process has completed on a server an entry is recorded in the backup history.
After the verify process has completed the backup history data is updated to show the outcome of the verify process.
Unfortunately if the SQL Backup user interface is open, there's a chance that it caches the data before the verify process has finished, in which case the VERIFY column reports 'NO'.
In this case you can delete the local data cache located in the folder
C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data. This will cause the user interface to fetch the backup history data in order to create a new local cache which could have a temporary performance impact on the GUI.
This will be addressed in a future release of SQL Backup.
After the backup process has completed on a server an entry is recorded in the backup history.
After the verify process has completed the backup history data is updated to show the outcome of the verify process.
Unfortunately if the SQL Backup user interface is open, there's a chance that it caches the data before the verify process has finished, in which case the VERIFY column reports 'NO'.
In this case you can delete the local data cache located in the folder
C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data. This will cause the user interface to fetch the backup history data in order to create a new local cache which could have a temporary performance impact on the GUI.
This will be addressed in a future release of SQL Backup.
Helen Joyce
SQL Backup Project Manager
Red Gate Software
SQL Backup Project Manager
Red Gate Software
Comments