Thanks for the suggestion, Wirt, but I don't think in this case it would
work.
Recall we're doing an "online" backup.
Performing 20 of these at different times would result in 20 different sync
points and a resulting "total fileset" that is inconsistent in terms of
representing a single point in time.
Unless otherwise convinced, I think I want a solution that produces a tape
that is restoreable in a single pass, and without comprimizing the online
backup process.
-----------------------------------------------------------------------
-
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651 Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000 Fax: 905.889.3001
email: [log in to unmask] web: http://www.gsainc.com
-----------------------------------------------------------------------
-
---------- Original Message -----------
From: [log in to unmask]
To: [log in to unmask], [log in to unmask]
Sent: Thu, 6 Oct 2005 15:21:53 EDT
Subject: Re: [HP3000-L] copying STD file to tape for subsequent restore
> Gilles asks:
>
> > Customer wants to:
> >
> > 1. perform online store-to-disk of @[log in to unmask]@
> > 2. ftp resulting store files to disaster-recovery spare HP3000 in
remote
> > location
> >
> > At this point, subseqent restoration of files onto existing disks
directly
> > from disk files would require approximately twice to amount of disk
space
> > necessary - ignoring compression on disk (comprising the @[log in to unmask]@ fileset
> plus
> > the space occupied by the store-to-disk files).
> >
> > Is there a way to copy the disk store-to-disk files onto dds in such a
way
> > that it would be possible to perform the restore operation directly
from
> > tape, rather than disk - and thus reduce the highwater mark of total
disk
> > space required.
>
> I don't know the answer to your question, but if there proves to be
> no way to do what you want to do, you could still reduce the amount
> of disc space required on the remote machine to 1/10th to 1/20th
> that currently being required by simply breaking the process into 10
> or 20 transfers of approximately equal length.
>
> Instead of an @[log in to unmask]@ store, store-to-disc only about 1/20th of the
> disc space of the primary system and then FTP that STD file to the
> backup machine, and then restore that fileset on the backup machine.
> Repeat the process as required until all of the files have been moved.
>
> It's more tedious initially than a one-fell-swoop solution, but once
> the controlling job is written, it wouldn't be any worse to execute.
>
> Wirt Atmar
------- End of Original Message -------
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|