I can't find much documentation or guidelines and am hoping to get some pointers from you guys.
Copy to tape can be really slow when reading from a deduped Windows Server 2012 volume. (set files not to dedup until 2 days old which helps massively)
Job progress reports 99% when the job moves to a second tape (sometimes)
I've had one media set take a tape that had been allocated to a different set and write to it
Jobs failed due to issues accessing the database:
v.Eremin wrote:Probably, GUI glitch or something similar. Does it result in further issues or it’s more about simple inconvenience?
v.Eremin wrote:Might it be that there were no free tapes available at that time and the one that was allocated to different mediaset had already exceeded its retention period?
lordjeffers wrote:As per description, it looks like overloaded SQL issue. So, the question is whether or not there was a high load put on the SQL server at that time and what edition of SQL server is being used (Full, Express)?
Users browsing this forum: cotterj and 3 guests