What are the challenges you face when working across database platforms? Take the survey

Erasefiles=1 deleting stuff less than 24 hours old?

BruceBBruceB Posts: 14
edited August 12, 2005 7:54AM in SQL Backup Previous Versions
I've just started using the erasefiles extension in my backup script and got a nasty surprise when I looked in the backup directory this evening. I was using the following cmd from a batch file -

"C:\Program Files\Red Gate\SQL Backup\SQLBackupC" -SQL "backup database fred to DISK = '<AUTO>' with ERASEFILES=1,MAILTO_ONERROR='xxx@xxx.co.nz'"

and a similar script to make hourly transaction log backups. (It also has erasefiles=1 - is this strictly necessary? The help doesn't distinguish between log and full backups regarding deletion).

It's 10pm here but I don't have any files prior to 2am this morning. They were there this morning.


  • Options
    This is still weird... I changed to ERASEFILES=2 and now it is deleting stuff 36 hours old rather than 48!

    My timezone is GMT + 12... could this be freaking out the calculation?

  • Options
    peteypetey Posts: 2,358 New member
    That is a confirmed bug. Pls contact support for a patched version.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.