SQB46 fails to move/delete processed log files
ev89pimp
Posts: 10
Hello all,
I'm having an issue with SQB Pro that only manifests itself under periods of heavy load on the target server. Here is a little background information:
We have a primary server and backup server in separate offices that are interconnected via a T1 vpn. We are using SQB Pro in a log shipping scenario and it works fine during the week. We run batch processing each night that results in 3-4GB of transaction logs to be shipped over and processed on the backup server.
On Sunday's, we run database maintenance jobs on the primary server that again generates massive traffic from primary to secondary server. What happens during these maintenance jobs is that the secondary server will process .sqb transaction logs, but fail to move the processed logs from a directory called NOTProcessed to Processed.
When I look at the log files for the SQB application on the backup server, the log will indicate a log file was moved and deleted from the NOTPROCESSED folder, but I verify myself that it actually DID NOT get moved or copied. When this happens repeatedly, SQB will fail to restore since it finds "old" transaction logs in the NOTPROCESSED directory that have LSNs that are too early to apply to the backup db. When this happens, each and every restore will fail until I manually delete these old log files.
Any idea what's going on?
thanks
I'm having an issue with SQB Pro that only manifests itself under periods of heavy load on the target server. Here is a little background information:
We have a primary server and backup server in separate offices that are interconnected via a T1 vpn. We are using SQB Pro in a log shipping scenario and it works fine during the week. We run batch processing each night that results in 3-4GB of transaction logs to be shipped over and processed on the backup server.
On Sunday's, we run database maintenance jobs on the primary server that again generates massive traffic from primary to secondary server. What happens during these maintenance jobs is that the secondary server will process .sqb transaction logs, but fail to move the processed logs from a directory called NOTProcessed to Processed.
When I look at the log files for the SQB application on the backup server, the log will indicate a log file was moved and deleted from the NOTPROCESSED folder, but I verify myself that it actually DID NOT get moved or copied. When this happens repeatedly, SQB will fail to restore since it finds "old" transaction logs in the NOTPROCESSED directory that have LSNs that are too early to apply to the backup db. When this happens, each and every restore will fail until I manually delete these old log files.
Any idea what's going on?
thanks
Comments
The backup server (target) is a clean build of Windows 2003, running SQL 2005, and nothing else! I have dual 2.4ghz xeons and 4GB ram...I can't figure out why SQB would have an issue moving the file and if it did, why it would say it moved it!!
HELP
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
On a side note, I've noticed monster disk queueing happening on the data drive on this database server around the same time the files aren't deleted. Has anyone seen this situation cause Windows NOT to delete a file when asked? Maybe the queue gets so long that the deletion request times out?
thanks,
E