[Networker] issues with AFTD with USB drive
2011-03-16 13:41:26
I searched the list's archives before posting this.
My management instructed me to use a USB drive in creating a short-term
backup solution in a remote office.
I have known that USB drives can perform well as a desktop harddrive, but
have not seen them in use in production situations. I now know why. :-)
In directing savesets to be stored on the AFTD rd=somehost:Y:\aftd (where
Y:\aftd is a folder on a 2TB USB drive I was given) I *regularly* see
problems like these inside the server's /nsr/logs/daemon.raw file:
38758 03/16/11 07:36:33 2 0 0 1 23684 0 dalsn004 nsrd media emergency:
Cannot write to Y:\aftd\90\50\630a5181-00000006-68808bf2-4d808bf2-219f0014-
4f1d839a - Invalid argument
42506 03/16/11 07:36:34 2 0 0 1 23684 0 dalsn004 nsrd media info: save
set C:\ for client jpnnpd1 was aborted and removed from volume
TokyoData.003
When this symptom arises, the backup aborts and the saveset starts over
from the top. Usually this process repeats until I've exceeded
the "retries" setting in the client resource.
Have others seen this, or are there known workarounds I should have
thought of?
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] issues with AFTD with USB drive,
Ty Young <=
|
|
|