On Wed, Aug 15, 2007 at 07:57:32PM -0700, fedora wrote:
In normal failure modes, this should be taken care of. Can you give
some detail on the type of failure that's triggering this?
Also, amcleanup should function as a second line of defense for killing
such processes.
Here is the
Hello I'm wondering if self backups are possible with AMANDA?
That is, not having any client machines, but simply installing AMANDA
server on a linux box and using it to backup the machine its on?
If not, would it be possible to setup both client AND server on the same
box and use it in this
Hi all,
I hope you can help! I'm just setting up amanda on a solaris 5.7 server,
and I'm getting this error:
odus 99 /home3/local/etc amcheck normal
Amanda Tape Server Host Check
-
Holding disk /home3/amanda/holding: 7302172 KB disk space available, using
7199772 KB
Debaecke, David M CTR SPAWAR, MILL DET wrote:
Hello I'm wondering if self backups are possible with AMANDA?
That is, not having any client machines, but simply installing AMANDA
server on a linux box and using it to backup the machine its on?
If not, would it be possible to setup both
Debaecke, David M CTR SPAWAR, MILL DET schrieb:
Hello I'm wondering if self backups are possible with AMANDA?
That is, not having any client machines, but simply installing AMANDA
server on a linux box and using it to backup the machine its on?
If not, would it be possible to setup both
What group is your amanda user in ?
Follow the links from the device /dev/rdsk/c0t1d0s5 to the
/devices/... and check the protections on that.
you may want amanda in a different group or something.
On Thu, Aug 16, 2007 at 10:04:42AM -0700, Brian Maxwell wrote:
Hi all,
I hope you can help!
The various dump programs on Solaris need access to the raw device for
the file system. The rundump command is set-uid root so it can make the
backups, but the amcheck portion is not. The solution I found for my
Solaris systems was to change the group membership to the 'amanda'
account to the
Hi all,
I'm sorry to be so bothersome, but I'm having another problem, and after
looking through all of the documentation I could find, I can't solve it.
In my disklist file, I've defined a new client, named lucy. I set up the
amanda client package on lucy according to the directions in the
Thanks all for getting me on the right track. Adding amanda to the sys
group fixed the problem.
Brian Maxwell
Sr. Software Engineer I
SWCM RAM Block 1 2 GMLS and Phalanx/SeaRAM
520.794.9076
520.498.5962 Pager
520.975.4725 Cell
[EMAIL PROTECTED]
image/gifimage/gif
On Wed, Aug 15, 2007 at 07:57:32PM -0700, fedora wrote:
In normal failure modes, this should be taken care of. Can you give
some detail on the type of failure that's triggering this?
Also, amcleanup should function as a second line of defense for killing
such processes.
Here is
On Thu, Aug 16, 2007 at 02:38:03PM -0700, Brian Maxwell enlightened us:
I'm sorry to be so bothersome, but I'm having another problem, and after
looking through all of the documentation I could find, I can't solve it.
In my disklist file, I've defined a new client, named lucy. I set up the
11 matches
Mail list logo