Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+mt\s+status\s+command\s+aborting\s+a\s+running\s+backup\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+mt\s+status\s+command\s+aborting\s+a\s+running\s+backup\s*$/: 2 ]

Total 2 documents matching your query.

1. [Networker] mt status command aborting a running backup (score: 1): Author: Clb <cbrandenstein AT MSA DOT COM>; Date: Thu, 3 Feb 2005 11:56:17 -0500; I have a question for the group. Has anyone ever issued an mt -f device status command while a backup was running? If so, what happened? Here is what happened to us. We have several Tru64 5.1b, dedic; /usr/local/webapp/mharc-adsm.org/html/Networker/2005-02/msg00054.html (11,721 bytes)
2. Re: [Networker] mt status command aborting a running backup (score: 1): Author: Darren Dunham <ddunham AT TAOS DOT COM>; Date: Thu, 3 Feb 2005 09:41:03 -0800; It's been a while since I've done that in a fiber environment, but I seem to recall that if a different node had the drive in use, I'd get "SCSI Reservation" errors, and if the current node was usin; /usr/local/webapp/mharc-adsm.org/html/Networker/2005-02/msg00057.html (12,044 bytes)

Current List: 1 - 2
Page: [1]