Comments
Sort by recent activity
I am having the same issue. Any update on the issue or a resolution? / comments
I am having the same issue. Any update on the issue or a resolution?
Peter,
Yes they do. Will adding the 4 mask to the fileoptions total remove these? / comments
Peter,
Yes they do. Will adding the 4 mask to the fileoptions total remove these?
Peter,
I just changed the FILEOPTIONS to 1 and it worked perfectly. I have 24 hours on local disk and 3 days on SAN storage.
Thank you for your help! / comments
Peter,
I just changed the FILEOPTIONS to 1 and it worked perfectly. I have 24 hours on local disk and 3 days on SAN storage.
Thank you for your help!
That is exactly what I want...but it isn't working. I want the files in the COPYTO folder to get deleted automatically, but they aren't.
As stated in my first post, the files are backing up to a SAN backended drive, not to tape. / comments
That is exactly what I want...but it isn't working. I want the files in the COPYTO folder to get deleted automatically, but they aren't.
As stated in my first post, the files are backing up to a S...
I have now deleted the job and created a new one with a new schedule that mimics the old job. The same issue is still happening with the backups on this server.
The files seems to be just a few seconds off from each other (when they work) and exactly the same when the backup fails. The funny thing is that this is only happening with one of the databases of the two that are in Full recovery mode. / comments
I have now deleted the job and created a new one with a new schedule that mimics the old job. The same issue is still happening with the backups on this server.
The files seems to be just a few se...
Just in case this happens to anyone else, the issue has been resolved. The server in question was a clustered server, and after the cluster was rolled, the issue disappeared.
I believe there was a sort of 'ghost' job running that could not be seen in MSDB or the agent and was causing the issue. / comments
Just in case this happens to anyone else, the issue has been resolved. The server in question was a clustered server, and after the cluster was rolled, the issue disappeared.
I believe there was a...
I upgraded the components from 4.5 to 4.6 in hopes that this would fix the problem, but it did not. The job works fine when I manually run it or if I run the T SQL from the step of the job in a query window.
This only happens when the agent runs the job. I am out of ideas. / comments
I upgraded the components from 4.5 to 4.6 in hopes that this would fix the problem, but it did not. The job works fine when I manually run it or if I run the T SQL from the step of the job in a qu...
My only problem with that is, the only version of the GUI I had to install was 5.0, but i was not going to upgrade production machines with the new software before doing extensive testing.
I did find the previous version in the public FTP from Red Gate though, so the issue is kind of moot at this point. / comments
My only problem with that is, the only version of the GUI I had to install was 5.0, but i was not going to upgrade production machines with the new software before doing extensive testing.
I did fi...