Hopefully someone here can help with some tips.
Have an older version of TSM Server (5.4.03) running on an AIX box, and a Solaris 10 TSM client that is using HSM to manage a vxfs volume called /hsm. (Veritas v4.1)
The /hsm volume is a SAN LUN on an older IBM array. Am now looking to migrate my storage to a new EMC SAN, and have a LUN available on the Solaris server from the EMC SAN of the same (similar... just a few bytes larger) size.
I was hoping that if I shut down all TSM processes and used a vxdump / vxrestore of the filesystem then remounted the new LUN as /hsm it would work.... it did not. The copy vxdump/vxrestore took over 12 hours (+4million files) and HSM simply didn't like the new volume.
I do not want to migrate to another mount point, as the usage of this HSM is via an NFS share... I would like to keep the same name.
What options do I have to get the new LUN in place of the old one so I can decommission the old array??
I am an old-time UNIX guy, but for HSM, consider me a newbie!
Cheers!
Have an older version of TSM Server (5.4.03) running on an AIX box, and a Solaris 10 TSM client that is using HSM to manage a vxfs volume called /hsm. (Veritas v4.1)
The /hsm volume is a SAN LUN on an older IBM array. Am now looking to migrate my storage to a new EMC SAN, and have a LUN available on the Solaris server from the EMC SAN of the same (similar... just a few bytes larger) size.
I was hoping that if I shut down all TSM processes and used a vxdump / vxrestore of the filesystem then remounted the new LUN as /hsm it would work.... it did not. The copy vxdump/vxrestore took over 12 hours (+4million files) and HSM simply didn't like the new volume.
I do not want to migrate to another mount point, as the usage of this HSM is via an NFS share... I would like to keep the same name.
What options do I have to get the new LUN in place of the old one so I can decommission the old array??
I am an old-time UNIX guy, but for HSM, consider me a newbie!
Cheers!
