You were right about the -D option, the xfsrestore works fine now.
As for using the -a, it is not important. I think that DMF must work a bit
differently than HPSS. We actually punch holes in the file after migrating
the data. I guess that DMF does not, which requires use of the -a option
to xfsdump in order to keep the migrated data from being dumped. For us
the data isn't there at all, so xfsdump doesn't have a choice to make.
Thanks for the advice,
-James Goodwin
Software Engineer
IBM Global Services - Federal
jagoodwi@xxxxxxxxxx
Phone: (281) 336 2578
Fax: (281) 335 4231
T/L 260-2578
Dean Roehrich
<roehrich@xxxxxxx To: James A
Goodwin/Houston/IBM@IBMUS
> cc: linux-xfs@xxxxxxxxxxx
Subject: Re: xfsdump/restore
Not Restoring Regions
06/20/2002 10:01
AM
>From: "James A Goodwin" <jagoodwi@xxxxxxxxxx>
>We have been doing some testing with xfsdump/xfsrestore and have noticed
>that DMAPI regions present on files at dump time are not restored.
We support just one region for the file, but I think you want to use the -D
option on xfsrestore.
Now you've reminded me of something else...
You're probably using dm_set_dmattr() to attach HSM-specific info to the
file.
Our DMAPI implementation actually uses extended attributes to store that
info.
Because this is HSM-specific info, only your HSM can decode it. Now look
at
the -a option on xfsdump.
That -a option would be useful to you, I'll bet. To do that, xfsdump knows
how to decode the HSM-specific info that comes from our own HSM, "DMF".
However, It doesn't know how to decode the info from your HSM. It may be
time
for you to submit some code to xfsdump.
In the xfsdump and xfsrestore manpages the -A option is described from a
DMF
perspective, but I don't believe this is DMF-specific.
Dean
|