vxdump: source and dest filesystem sizes

[HPUX SysAdm]

I am using vxdump to copy data b/w filesystems that are on different servers.

Searching these forums gave me all the answers I needed to setup vxdump to copy the data but what I can't figure out is why does the size of the destination filesystem always tends to be somewhat smaller than the source filesystem?

Is this data copy method going to work after I startup the processes or not?

[VK2COT · Accepted solution]

Hello,

vxdump(1M) is quite safe. As long as it does
not report any open-file or similar issues.

It is not unusual to see some difference
in file sizes when the data is copied
from one location to another.

Some things to consider:

a) What is the extent size on source
and destination logical volume?

b) Are the blocks of data in source file
systems contiguous or scattered all over
the file system?

c) Are the files that are copied sparse?

d) Are the files that are copied
large?

e) What is the alignment restriction on allocations in source and destination
logical volume (see the mkfs_vxfs(1M) manual
page)?

and so on.

In other words, if return code of
vxdump(1M) is 0 and does not report
any errors, you are OK.

Cheers,

VK2COT

[HPUX SysAdm]

Thanks VK2COT

[HPUX SysAdm]

.