[Networker] Why does NetWorker use a read-only drive for writing?
2007-04-10 13:35:03
I have a tape device wherein I set "Read only" to Yes. The device is
Enabled. Why does NetWorker still try to use the device for backups?
I came in this morning, and NetWorker was waiting for a writeable tape
for a given backup pool/group. The tape in question was loaded in this
device, and the tape is still appendable, but it obviously had set the
'Write enabled' attribute for the volume to 'Yes'. That might make sense
given that the device is read only, so I unmounted the tape and
re-mounted it in one of the other drives and then the backups ran to
that tape and completed just fine.
My question is why would NetWorker have ever loaded this volume in a
device that was set to Read only? I thought any such device would only
be used for recovers or maybe cloning when reading from the source
volume. There is no cloning, however, associated with the affected tape
pool/group.
We're running 7.2.2 on a RedHat storage node. Primary server is 7.2.2 on
Solaris. The device is in a library attached to the snode.
George
--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Networker] Why does NetWorker use a read-only drive for writing?,
George Sinclair <=
|
|
|