Jon,
I love living on the cutting edge.
I once coded a routine that referenced itself... explained to my
manager that you'd need to screw up 16 times before the interpreter
(DCL interpreter under v4.x) would reach its limit and that that
would never happen in practice.
He say down at my keyboard
On Fri, Aug 27, 2004 at 10:57:45AM -0400, Brian Cuttler wrote:
>
> I'm not concerned about the /usr14 error, the disk isn't currently
> spinning, however the "fatal buffer mismanagement bug" error is
> interesting, especially since we only have amanda configured to use
> a single tape (the server
I'm not concerned about the /usr14 error, the disk isn't currently
spinning, however the "fatal buffer mismanagement bug" error is
interesting, especially since we only have amanda configured to use
a single tape (the server does not have a jukebox).
Server is Solaris with a DLT
Client is IRIX
A
On Fri, 27 Aug 2004, Jukka Salmi wrote:
> Greg Troxel --> amanda-users (2004-08-27 08:38:13 -0400):
> > rm'ing the holding dir should work fine. run amadmin config find
> > before and after and you'll note that the disks are recorded as being
> > in the holding dir, but not assigned to a tape.
>
>
Hi,
Greg Troxel --> amanda-users (2004-08-27 08:38:13 -0400):
> rm'ing the holding dir should work fine. run amadmin config find
> before and after and you'll note that the disks are recorded as being
> in the holding dir, but not assigned to a tape.
Worked fine, thanks!
> The only issue I can
rm'ing the holding dir should work fine. run amadmin config find
before and after and you'll note that the disks are recorded as being
in the holding dir, but not assigned to a tape.
The only issue I can see is getting amanda's dump levels and
/etc/dumpdates out of sync, but if these are old and
Hi,
On Friday 27 August 2004 13:31, Kaushal Shriyan wrote:
> When i am running the below command i get the below error
>
> [EMAIL PROTECTED] kaushal]# amrecover -s indus.mumbai.redhat.com
> AMRECOVER Version 2.4.4p1. Contacting server on indus.mumbai.redhat.com
...
> Trying disk /home ...
> Trying
Hi,
if for some reason dumps have been left in the holding disk Amanda
recommends to run amflush. That works fine, but sometimes - especially
if those dumps are already very old - I don't want to flush them to
tape, because I don't need them anymore. What should I do in such a
situation? Is it saf
Kaushal Shriyan wrote:
When i am running the below command i get the below error
[EMAIL PROTECTED] kaushal]# amrecover -s indus.mumbai.redhat.com
AMRECOVER Version 2.4.4p1. Contacting server on indus.mumbai.redhat.com
...
220 indus AMANDA index server (2.4.4p1) ready.
200 Access OK
Setting restore
Hi All !
When i am running the below command i get the below error
[EMAIL PROTECTED] kaushal]# amrecover -s indus.mumbai.redhat.com
AMRECOVER Version 2.4.4p1. Contacting server on indus.mumbai.redhat.com
...
220 indus AMANDA index server (2.4.4p1) ready.
200 Access OK
Setting restore date to toda
Kaushal Shriyan wrote:
I wanted to enable gzip compression on my backups since i want to
accomodate lots of data on to a 40GB tape, At present I am using
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
priori
Hi
change to compress line from none to server or client depending on where
you want the compression to actually be done...
or look at a different dumptype that already does this for you...
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
Kaushal Shriyan wrot
Hi
I wanted to enable gzip compression on my backups since i want to
accomodate lots of data on to a 40GB tape, At present I am using
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
priority low
}
So I wou
13 matches
Mail list logo
