James_Lane
Level 3
Joined 17 years ago
User Profile
User Widgets
Contributions
Tape pops out - no job running!
Hi, Recently a new "bug" has appeared in my backup routines. Every time Iput in a tape, either Full or Incremental it wirls around for far longer than usual and then pops out. If Iput it back in straight away, it wirls for a little longer and then all is well. The backup jobs run fine. Why is it spitting out the tape? There are no error messages and the tape is set to be overwritten/append. Thanks in advance. Running 9.1 Rev 4691227Views0likes3CommentsThe process cannot access the file because it is being used by another process.
Hi. I'm using BE 9.1 4691 together with a NAS - Buffalo LinkStation. I run two backups per night. First to the NAS and then a Duplicate job that takes this backup and shoves it to tape. The above error is becoming more common so hence this question. This error occurs on the startup of the Duplicate job and I can only conclude it is referring to the backup file recently created. What can possibly be using the first backup file on the NAS other than BE itself? Can I add a delay factor between the two jobs? It looks like the first job does not release its hold before the Duplicate starts up. I also happen to know that using Windows logons to the NAS (linux OS, I think) causes all sorts of problems if you log on twice from the same machine. Pointers most welcome. Thanks in advance.110Views0likes0CommentsThe process cannot access the file because it is being used by another process.
Hi. I'm using BE 9.1 4691 together with a NAS - Buffalo LinkStation. I run two backups per night. First to the NAS and then a Duplicate job that takes this backup and shoves it to tape. The above error is becoming more common so hence this question: What can possibly be using the first backup file on the NAS other than BE itself? Can I add a delay factor between the two jobs? It looks like the first job does not release its hold before the Duplicate starts up. I also happen to know that using Windows logons to the NAS (linux OS, I think) causes all sorts of problems if you log on twice from the same machine. Pointers most welcome. Thanks in advance.Solved277Views0likes1CommentRe: Tape not overwritable when loads of space
Ken, I've been away so appologies for late response. You have mentioned that this sequence of backups should be under the same media set before and I must confess I failed to remember that when going off at various tangents. I will now set this up under one set and use an APP OPP frequency as discussed earlier. MANY THANKS FOR ALL YOUR PATIENCE AND DEDICATION.514Views0likes0CommentsRe: Tape not overwritable when loads of space
Thanks Ken - sorry for the late reply. Maybe the next comment should be a new thread but it does continue on what has gone before: I have continued with this week's setup of one tape for INCR - though I see your point re two INCR tapes. However I am now presented with the error message that must surely drive us all mad. Basically - can't backup to tape as it is Overwrite protected. This is when the Allocated Date is 9/4 even when it came from Scratch Media at the beginning of the INCR jobs namely Tue 15/4. With OPP at 6 and APP at 5 days. If OPP runs from the Allocated Date this is Overwrite protected on the 15th, BUT the job is Append then Overwrite and there is 19Gb available capacity. Why does it not append please? Why is it trying to Overwrite. Even running the job again today (17th) it still fails with same error. P.S. When does a tape "close"? Is it at the end of each backup regardless of the type of backup?514Views0likes0CommentsRe: Tape not overwritable when loads of space
Thank you, this is great. I use the Duplicate method. I understand what you suggest: both Full and Incr on each tape - I had never thought of that style of approach before. However I do remove the FULL tape to offsite the next day to cover risk of fire, flood etc. Leaving the FULL in the machine for the week would expose me to this risk again. Can I still have two tapes for FULL, one for INCR all in the same media set? I would then only rotate the FULL tapes. What would I need to set APP and OPP to? Sorry for being dense but I have not grasped the logic of this yet! I'm off to read the manual again... thanks for your patience. Also I note that you make the OPP just (number of tapes * days in week - 6). This is great news as I always have an issue with the OPP/APP if a job overruns or needs running again for some reason. I just took off one day from the total days, but if it is safe to take off 6, then all events should be covered.514Views0likes0CommentsRe: Tape not overwritable when loads of space
Ah! The Full goes to a Media Set that is a NAS folder, and so does the Incremental. But these are different media sets as they are in different folders on the NAS. This seems to work fine. The tape media sets are also different because I needed to distinguish between the cycles of OPP and APP. So 4 media sets in all with 3 tapes. Looking at this now, if in the 2nd week I had a restore to do on an Incremental and the NAS had blown a fuse - I would blow a fuse too! As it would have been overridden. Basically I am storing about 2 months of backups on NAS with weekly FULL and 4 Incrementals and then this is also sent to tape using the Duplicate job. The tapes though only would take me back 2 weeks as I have just 2 Full tapes I interchange. The incremental will only take me back 1 week. So if I have to have the tape media on one set for both Full and Incremental how do I set this up so as to keep the status quo or should I have a different routine completely?! Maybe: 4 tapes (2 Full and 2 Incr) OPP is 13/14 days (I tend to take one day off in case I have an o'night error and have to run the job again the next day - as this can really mess things up) and the APP is Infinate. Would that work? Oh, my head hurts...!514Views0likes0CommentsRe: Tape not overwritable when loads of space
Thanks for the pointer - however I have the OPP at 4 days as the 5th is the full backup and the APP is Infinite! So what now? I am even more baffled! I don't think I need to worry about overwrites of this tape as the Full Backup resets the starting point each week. I also have all backups going to NAS first. So this Incremental tape only has a life of a week and will only be used if my NAS blows... Is this ok or have I missed a trick or scenario? Thanks for your input.514Views0likes0CommentsTape not overwritable when loads of space
This is probably a basic issue but I am having trouble running a system of backups to tape. I use 9.1 rev 4691 on Windows Server 2003 SP2. Each week I run a FULL backup which then duplicates to tape. There is no problem with this as I alternate 2 tapes and have it set to overwrite each time. My problem is with the incremental daily backups. Currently the job (tape reused each week) is set to Append, or Overwrite if no appendable available. First week after making the tape Scratch Media works fine. Now I always get a message the 2nd week saying tape "is overwrite protected". It has used 1.32Gb with 18Gb available. Why does it not APPEND? How can I force it to go to the end of the tape before thinking about overwritting the beginning please?514Views0likes10Comments