Comments
Sort by recent activity
petey wrote:
Are the old files encrypted? If they are, they need to have been encrypted using the same password as the one you are using for the current backup, before they can be deleted.
Yes, the files are all encrypted, the password hasn't changed. I'm using the same "PASSWORD=" parameter as before the update to v5.1:
PASSWORD = ''<ENCRYPTEDPASSWORD>XXXXXXXXX</ENCRYPTEDPASSWORD>''
It worked like a charm with the old SQL Backup version 4.5. / comments
petey wrote:
Are the old files encrypted? If they are, they need to have been encrypted using the same password as the one you are using for the current backup, before they can be deleted.
Ye...
Same problem here...
Server Components are version 5.1.0.2781, SQL Server has been rebooted after the upgrade, so there shouldn't be anything left in SQL server memory.
Code I'm using: exec master..sqlbackup N'-SQL "BACKUP DATABASE [databasename] TO DISK = ''X:\SQL_DATA_BACKUP\<DATABASE>\<TYPE>\<DATABASE>_<TYPE>_<DATETIME YYYYmmdd_hhnnss>.sqb'' WITH COPYTO=''\\backupserver\SQL_DATA_BACKUP\<SERVER>\<DATABASE>\<TYPE>'',
FILEOPTIONS = 3, PASSWORD = ''XXXXX'', KEYSIZE = 128, ERASEFILES_ATSTART = 2, COMPRESSION = 1, THREADCOUNT = 3, VERIFY"', @exitcode OUTPUT, @sqlerrorcode OUTPUT
Old backup files are NOT deleted, no warnings or errors occur.
Tried without "VERIFY", but no success.
Tried with "ERASEFILES" instead of the "ERASEFILES_ATSTART", no success either.
I still have backup files from over a week ago in both the local backupfolder and the remote backup folder (despite ERASEFILES_ATSTART = 2).
Environment:
Windows Server 2003 Standard SP2
SQL Server Enterprise Edition v8.00.2039 (SP4)
SQL Backup Standard Edition version 5.1.0.2781
SQL Server, SQL Server Agent and SQL Backup services running as user with administrative rights (and as such have full access to both the local and the remote backup folder)
Oliver Drexler / comments
Same problem here...
Server Components are version 5.1.0.2781, SQL Server has been rebooted after the upgrade, so there shouldn't be anything left in SQL server memory.
Code I'm using:exec master.....
Thanks for your reply. I'm glad you could reproduce this on your side [image]
Until there's a fix I'll just edit the script manually and remove the brackets from the function call each time I checkout/update one of those tables (currently we're only using the "hashbytes" function in computed columns, so this is a simple search&replace).
Regards,
Oliver / comments
Thanks for your reply. I'm glad you could reproduce this on your side
Until there's a fix I'll just edit the script manually and remove the brackets from the function call each time I checkout/up...