Re: full file system cannot achieve make_tape_recovery Frank Slootweg <this@ddress.is.invalid> wrote in message news:<40e666e9$0$1756$abc4f4c3@news.wanadoo.nl>...
> yls177 <yls177@hotmail.com> wrote:
> > can a full file system backup accomplish the same as
> > make_tape_recovery?
> >
> > my understanding is that make_tape_recovery is necessary to restart
> > the system and in the case of a full file system, i dont think that i
> > can do so cos i still need the basic configuration to talk to the
> > device to do the restoration.
> >
> > thanks
>
> In short you need a make_tape_recovery(1M) kind of backup for the case
> where the system does not ('fully') boot for whichever reason. With not
> 'fully', I mean that it does not boot, and can not be made to boot, to a
> phase where the file (backup) restore software is available.
>
> You need (full) file (system) backup (i.e. SAM/fbackup(1M) or (better)
> OmniBack (DataProtector?) et al) for all other cases.
>
> So you need *both* and one is no subsititute for the other.
yeah.. i was using omniback (dataprotector) in the past... but then
now in the new setup in my client place, they are using fbackup. i
think the advantages are as follows with using omniback
1) a centralised backup storage/strategy compared to individual
dds/dlt tapes available to each server.
right? |