I am having a problem with a backup file job.
About two weeks ago, we received a notice that a backup job stopped working because the file was too large for the server it was being moved to.
Normally, the file's size would be around 1.8 GB, however, according to our information, the file was ballooning to around the 4 GB mark and higher.
Upon reviewing the contents of the backup file, there was the data along with approxiamtely 60 to 70 transaction logs.
According to the properties of the backup job, the overwrite parameter was set to "append" when it should have been "overwrite", however the parameter would keep going back to "append" after we changed it.
The job was brought back to normal, however there is a concern that this problem will re-occur within the next few weeks.
Could anyone tell me how and why something like this would happen, and how we can prevent it from becoming a major problem?
If you need any further information to come up with an answer, please let me know here.
Thank you.
About two weeks ago, we received a notice that a backup job stopped working because the file was too large for the server it was being moved to.
Normally, the file's size would be around 1.8 GB, however, according to our information, the file was ballooning to around the 4 GB mark and higher.
Upon reviewing the contents of the backup file, there was the data along with approxiamtely 60 to 70 transaction logs.
According to the properties of the backup job, the overwrite parameter was set to "append" when it should have been "overwrite", however the parameter would keep going back to "append" after we changed it.
The job was brought back to normal, however there is a concern that this problem will re-occur within the next few weeks.
Could anyone tell me how and why something like this would happen, and how we can prevent it from becoming a major problem?
If you need any further information to come up with an answer, please let me know here.
Thank you.