[6795] in linux-scsi channel archive
Re: backup/redundancy solutions
daemon@ATHENA.MIT.EDU (Alvin Oga)
Thu Jul 8 17:13:48 1999
From: alvin@planet.fef.com (Alvin Oga)
To: anoah@pfeiffer.edu (m.allan noah)
Date: Thu, 8 Jul 1999 13:20:11 -0700 (PDT)
Cc: linux-raid@vger.rutgers.edu, linux-scsi@vger.rutgers.edu,
alvin@planet.fef.com (Alvin Oga)
In-Reply-To: <19990708182126.30929.qmail@pfeiffer.edu> from "m.allan noah" at Jul 8, 99 06:21:26 pm
hi allan, steve,
using NT to backup linux destroys linux permissions...
using linux to backup NTs destroys NT permissions/uid/gid
- as others have stated earlier
using mirror'ed disks might result in the original disk being bad/corrupted
and the mirror itself to be bad...( you have the time between mirrors
to find any corruption or bad data etc...
- I keep a tar file ( unmirrored ) so that at least one day of backup
file will/should have a last known good file
- problem with 1 huge backup machine is if that one machine dies...
your raid5 backup is dead to ?? ( bad power surge )
- that huge disk/system sits idle 99% of the time ??
- tape backups for offsite archives only... too slow to recover files
- 20Gb ide drive is $300...( fast, cheap, good for online mirror, etc )
- we have 3 - 64Gb hardware raid as /home... ( or equivalant )
and the backups of it spread across 4 the other servers
- I keep a tar file of changes...
- the tar file is used to create the mirror periodically
- hourly backups to keep a copy of hourly changes
- daily backups/mirror to mirror todays work
- the tar file will have the "changes" for however long we keep the data
- if a file changes daily....going back in time, we should
find a uncorrupted file...but...not to to date ?
- backup can also be corrupt or incomplete
- usually NFS problems
- disk 100% full problems
- lack of backup permission to remotely read root protected files
- if the full backup or incremental backup is bad... any subsquent backups are
bad too ...
- my daily incremental backups start for the last full backup
- my weekly backups span 30 days and a full backup
( if this week full backup is bad...30-day incremental can
( rebuild/recover from last weeks full backup
- weekly full backups reside on different disks on 3 different machines
- it auto-rotates to different backup machines...
( backup_1, backup_7, backup_30, backup_wk1, backup_wk2, etc..
- i wrote my own backup script to do backups and "mirror"
- have search capability too
- some people use cdr to back really critical data
have fun
alvin
#
# linux backing up NTs will lose some uid/gid info from the NTs
# - CAUTION...some linux kernels will corrupt the NT time stamps
#
# take the tar file and extract to the mirror disk or leave it alone on the backups
#
# backup of NT or linux... uses this same method
#
#
# change -mtime to change between hourly/daily/weekly incremental backups
# change /Backup to different disks/servers to protect against power surges, disk crashes
#
linux# mount /Backup
linux# smbmount /WinNT/C passwd -c `mount /mnt/WinNT' -U Administrator ( for NTs )
linux# cd /mnt/WinNT ; find . -mtime -1 -type f -print | tar cvf /Backup/today.tar -T -
linux# umount /mnt/WinNT ; umount /Backup
> bad call. i NEVER backup unix via smb. go and restore from that backup and
> look at your unix permissions. unless you tar first, perms are destroyed by
> smb.
>
> i use a backup server running linux. the nt boxes can dump to it using smb,
> the unix boxes use nfs v3, and the backup server takes care of the rest.
>
> this good cause it gives me a running machine, a harddrive backup, and a tape
> backup.... all with the correct full unix perms.
>
> allan
>
> Steve McPherson <SMCPHERSON@sgrlaw.com> said:
>
> > We do the same thing here. Linux is set up to talk to NT through SAMBA.
> The NT server is running the Backup Exec. The Linux server backs up along
> with everything else.
> >
> > >>> Dirk Petry <petry@ifae.es> 07/08/99 10:57AM >>>
> > Dear Tony,
> > our system manager here just dumps all data from a large
> > mixed LAN on a 70 GB DLT using Seagate Backup Exec running
> > on an NT server. It seems to work pretty well. Typical
> > data transfer speed is 3.5 MB/s.
> >
> > Best regards,
> >
> > Dirk
> > --
> > ----------------------------------------------------------
> > Dirk Petry email: petry@ifae.es
> > Institut de Fisica d'Altes Energies (IFAE), Edificio Cn,
> > Universitat Autonoma de Barcelona, 08193 Bellaterra, Spain
> > Fax: +34-93581-1938 Phone: +34-93581-2833
> >
> >
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
