data migration

[SAM_24]

Hi,

I need to migrate data from old raid based storage array to high end storage array. I am thinking to create new file systems and copy the data using tar command using the syntax below.

cd fromdir ; tar cf - . | ( cd todir ; tar xf - )

Man page says

Because of industry standards and interoperability goals, tar does not
support the archival of files larger than 2GB or files that have

Does this note applies to tar command syntax mentioned above?

What is the best way to do migration? I need to do it in TBs of data.

Thanks.

[Geoff Wild]

Yes....tar is limited to 2GB - GNU tar - 8GB...

I did migration like yours - best thing to use is vxdump:

vxdump -0 -f - -s 1000000 -b 16 /export/data/sap/IPR/ARCHIVE | (cd /zmnt/export/data/sap/IPR/ARCHIVE ;
vxrestore rf -)

The zmnt is the new storage.

Rgds...Geoff

[Mark Grant]

Well, on modern hpux systems the limit is 8GB though on 10.20 it is 2GB.

The only thing you need to watch out for when doing copying of this type is that you make sure you don't miss out th".files". However, your command syntax is correct.

[RAC_1]

Pax, cpio and tar have limitation of 2gb. you can use fbackup in this case.

Gurus here will give exact command line. I have not used fbackp that often. Even a dd will also help and you can bump up bs count to bit high.

Anil

[A. Clay Stephenson]

Yes, it does. Patched versions of tar (or the Gnu version of tar) will handle files of up to 8GB. If this is too small, look into fbackup/frecover pipelines or load up the Trial Version of OmniBack/Data Protector found on the Application CD's.

Another approach would be to add the LUN's / PV's or your new array to your existing volume group using vgextend and then use pvmove to move the data. You then can vgreduce the originals.

The scary part of this to me is that if you are thinking about using tar for this then that implies that tar is your normal backup. So how are you backing your files >2GB now?