From: "Ed Walsh" <ewalsh@lightning9.net>
To: matt.hemingway@pcnalert.com, linux-admin@vger.kernel.org
Subject: Re: Linux Backups
Date: Tue, 19 Nov 2002 16:09:38 -0500 [thread overview]
Message-ID: <005a01c29010$062b6960$e1110a0a@ewalsh01> (raw)
In-Reply-To: 3DD9414B0000536D@vader.se.ilan.cogent.net
using Samba 2.0.10 no NFS I should've compiled that in with the build.
----- Original Message -----
From: "Matt Hemingway" <matt@supplyedge.com>
To: "Ed Walsh" <ewalsh@lightning9.net>; <linux-admin@vger.kernel.org>
Sent: Tuesday, November 19, 2002 3:57 PM
Subject: Re: Linux Backups
> How are you transfering the data to the other machine?
>
> If it's NFS, than you need to make sure the server supports NFS version 3
and
> add NFS version 3 support to the client.
>
> I had this same problem with a Linux client we we're backing up to a
Solaris
> NFS server. Re-compiling the kernel with NFS version 3 client support
fixed
> the problem.
>
> -Matt
>
> On Tuesday 19 November 2002 12:34 pm, Ed Walsh wrote:
> > Hi All,
> >
> > I'm getting a little fustrated with linux backup. I have about 30GB of
data
> > residing on RedHat linux 7.1 that needs to be backed up. I've done
backup
> > with GNU tar with compression but it only backs up 2GB worth of data
onto
> > another machine. However, if I have 7GB of free space on the same
machine,
> > tar will go over the 2GB limit. So that part confuses me.
> >
> > I'm kinda hoping that someone knows a better way of backing up large
data.
> > I've somewhat been reading Amanda but I'm not sure if that's the way to
go.
> > I may be wrong since I'm new to linux backups.
> >
> > Any suggestions/recommendations or pointers to go to websites to
research
> > on would be greatly appreciated. Not having much luck on my own.
> >
> > Thanks,
> > Ed
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> ----------
> Matt Hemingway
> matt.hemingway@pcnalert.com
> http://www.pcnalert.com
> 626-585-2788 x136
> ----------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-11-19 21:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 8:01 difference btw CGI and HTML scripts simon Shaw
2002-11-18 16:42 ` Tyler
2002-11-19 17:09 ` Geoff Torres
2002-11-19 20:34 ` Linux Backups Ed Walsh
2002-11-19 20:46 ` Marshall Lake
2002-11-19 20:51 ` terry white
[not found] ` <3DD9414B0000536D@vader.se.ilan.cogent.net>
2002-11-19 21:09 ` Ed Walsh [this message]
2002-11-19 21:55 ` Milan P. Stanic
2002-11-20 9:06 ` Agus Budy Wuysang
2002-11-20 14:20 ` Storage systems Miguel González Castaños
2002-12-10 16:19 ` terminal problems with escape characters Miguel González Castaños
2002-12-11 1:04 ` dashielljt
2002-12-11 8:54 ` Miguel González Castaños
2002-12-12 1:11 ` dashielljt
2002-11-20 13:36 ` Linux Backups djh
2002-11-20 2:43 ` difference btw CGI and HTML scripts Michael Luevane
2002-11-18 18:18 ` - Luis -
2002-11-19 20:43 ` terry white
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005a01c29010$062b6960$e1110a0a@ewalsh01' \
--to=ewalsh@lightning9.net \
--cc=linux-admin@vger.kernel.org \
--cc=matt.hemingway@pcnalert.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.