Comments
Sort by recent activity
Script provided fails to backup. In Q-Analyzer It completes quickly with only a display of databases where recovery = full. Is it possible that the first db selected has recovery to simple so it fails there?
Thanks in advance ~Chris / comments
Script provided fails to backup. In Q-Analyzer It completes quickly with only a display of databases where recovery = full. Is it possible that the first db selected has recovery to simple so it f...
I have run some tests and have verified that this appears as a bug in SQLBackup. Erasefiles will not remove files with database names that are longer than 22 charactors. Resolution: export database with long name to database with name less than 22 charactors. Erasefiles will then work as expected. / comments
I have run some tests and have verified that this appears as a bug in SQLBackup. Erasefiles will not remove files with database names that are longer than 22 charactors. Resolution: export databas...
The server has multiple databases, the SP backs up TRN log files every 2 hours and deletes log backup files older than one day on all databases as configured, except for a few. The backup files that are not being deleted go back to the date that the SQLBackup job was created.
Any known issues with long file names? This might be entirely irrelevant but it seems that the backup files that are not being deleted are 20+ char long. Doesn't seem to be a 15+1 char issue as several of the databases are longer that 16 char but less than 20. / comments
The server has multiple databases, the SP backs up TRN log files every 2 hours and deletes log backup files older than one day on all databases as configured, except for a few. The backup files tha...