07-15-2010 04:28 AM
07-15-2010 06:06 AM
07-16-2010 03:34 AM
07-21-2010 01:50 AM
Quick update on this
We seperated this SQL instance from the main backup job and created a new job just for this instance. This worked without any issues we also ran the job at the same time as when it was in the main job (on request of Symantec support) and this ran with no issues, we therefore added the instance back into the main backup job setting it for the original timimg (i.e. back to how it was in the start) and this has run without issue.
When our support company contacted Symantec support about this they were told "Symantic are saying that at the moment there is no reported problem with this in 2010, or we are one of the first. Unfortunately, no hotfix is engineered by symantic if one customer reports a problem. If more and more customers start reporting there is a problem with this then a hotfix will produced to fix this".
So if anyone else has this issue please report it to Symantec support that way we may get this fixed