Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
Networker asking for a specific tape from previous days backup
This has occured a few times now and i am unable to tell why. The logs do not give anything away.
In my scenario we have 2 tapes a day for our FS backups. On several occasions it could get to say Wednesday and the clone would stop and networker would ask for the tape that was written to on Monday. I insert the tape it ask for it reads it for about 5 seconds, ejects it and the clone continues as normal.
This isn't normally a massive issue but on this occasion it is asing for a tape which is no longer on site and i do not reallt want to have to pay for an emergency tape recall. Is there any way i can cancel this request?
Thanks
UPDATE: I managed to cancel the request by restarting the networker services but i would still like to understand why its randomly requesting a specific tape from a previous days clone.
It is guress work, and i know i have not given much information but i dont have any more. This has been happening for some time. Originaly version 8.1.1.2 and also on 8.2.1.
There is no information in the logs as to what its looking for on the tape it requests. It mounts the tape, reads it for a few seconds then ejects it and networker carries on the orignal clone as normal.
Here is my 2 cents worth...
Most likely a corrupted database or so it is going back and searching an old tape.
Did you try running nsrck -L7 to repair the database?
When you restarted Networker it no doubt ran the nsrck command and cleaned up the indexes
It hasn't happened to me but that is probably where I would start
Thats where there is a problem. A tape is mounted and has written its save sets, networker then decided it wants a tape that was written to 3 days ago, i insert this tape, it only reads off it, it does not write to it. And the same with the original tape, nothing further is written to it. Its extremely difficult to pinpoint what its looking for.
What do we talk about at all? - Right now there are too many unknown parameters:
- A NW server with at least 2 tape drives attached. No jukebox - correct?
- Which backup level? - Do you run a full every day?
- Why can you be so precise with your "2 tapes per day" - Are these 2 backup tapes or 1 backup & 1 clone tape per day?
- The process is a clone job. If so, only the media index is involved - the CFI does not matter at all.
- Volume clone or save set clone?
- Automatic or scheduled clone job?
- Scripted cloning?
- The tape NW demands is obviously a source tape - correct?
Why should NW ask for an older tape at all?
- Wrong script command?
- Wrong device configuration (AMM?)
- Wrong driver?
This is all I can suggest right now. First we have to clarify the scenario.
If that's the case then it does sound like it is looking at the index on the tape
It makes sense then that it would have to go back and look at the tape just to see what was already backed up.
I would assume that it is a clone of an incremental and not a full backup
You probably won't have another issue with at particular tape/clone
@Larry
"If it is an incremental backup and the indexes are messed up it would make sense that it would go back and look at the index on the previous backup."
In general you are right - however, this does not apply to cloning. Cloning exclusively relies on media db information.
IMHO it looks to me more as NW would go and verify a volume label (for whatever reason). I just do not understand why it would interrupt/pause an active process.
bingo.1
1 Rookie
•
2430 Posts
1505
0
Posted July 20th, 2016 09:00
Without any further info, this is hard to tell.
NW obviously wants/needs to verify the label but only you can tell.
Next time you clone you should start a manual clone job (from the command line) and use another debug level (for example "-D5") Then you should see more info in the daemon.raw file.