>> by mistake MERGEFILESPACES=YES was not specified during
>> export/import of archive data;
>> as a result without giving any warnings or errors archive data was
>> imported to separate set of file spaces slightly changed in comparison with
>> backup file spaces (for example, for backup data /home/abcd - for archive
>> data /home/abc1);
>> fortunately, it is possible to restore data from archives, but I
>> have some questions:
>>Is it correct behavior of TSM Server or TSM Server should inform me about
>>mistake?
If you do not specify MERGEFILESPACES=YES, that is the defined/correct
behavior.
>>Will new archives come to correct file system (I couldn't see any other
>>possibilities, but any way) ?
Yes.
>>May it create any other problems for me in the future?
I suggest you archive a single file, then start the client and see what you
have to do for a successful retrieve.
It will not cause a "problem", except that you will have to remember in the
future that an archived file could be in either the old or new filespace and
remember to look in both.
If you do not often need to retrieve, or are unlikely to need the data, you may
just choose to leave things as they are.
Or, if you still have your V5 server, run the export/import again with
mergefilespaces=yes, then delete the .....abc1 filespaces.
Or, if you no longer have you V5 server, you can still correct it although it
requires some effort:
When there is no archiving activity on the client machine, on the TSM server do:
rename the ...abcd filespaces to ...abcnew
rename the ...abc1 filespaces back to ....abcd (what they should have been
called originally)
export the ....abcd filespaces to tape
rename the ...abcnew filespaces back to abcd
You now have some data in the filespaces on the TSM server by the correct
filespace names.
You also have some data exported to tape with the correct filespace names.
import the data from tape, this time specify MERGEFILESPACES=YES
That should get everything back to where you expect it to be.
W
|
