HP3000-L Archives

January 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Fri, 21 Jan 2000 15:54:09 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
"Jensen, Gary" wrote:
>
> We were wondering if there are any advantages/disadvantages when using HP
> TurboStore with the INTER and COMPRESS options when backing up to tape.

:RESTOREing HFS files from an ;INTER backup has some major problems due to the
scrambled file order that ;INTER produces.

For example, let's say you need to restore a large HFS directory tree that
doesn't already exist on disk.  Let's say the tree looks something like this:

/dir1
/dir1/file1
/dir1/file2
/dir1/dir2
/dir1/dir2/file3

Now let's say that ;INTER has written these to tape in this order (hey, it
could happen):

/dir1/dir2/file3
/dir1/file1
/dir1/dir2
/dir1/file2
/dir1

What happens if you want to :RESTORE /dir1/ (recursively)?  The first file on
the store tape is /dir1/dir2/file3.  Now at this point /dir1 doesn't exist, so
:RESTORE will have to create it for you if you specified ;CREATE.  But you end
up with default POSIX permissions and the owner/group ID of the user doing the
:RESTORE.  This could very well break your applications which depended upon the
original attributes!

I discovered this when I tried using :STORE-to-disk and :RESTORE ACCT= to do
some HFS account cloning/renaming.  The directories were very impressively
screwed up in the new account.  I had to purge the new account and start over
using tar instead of :STORE/:RESTORE.

- Mark B.

ATOM RSS1 RSS2