Summary: Need clarification on AdvFS V3 and V4 compatibility

From: Carlos Chua <chuacarlos_at_hotmail.com>
Date: Fri, 15 Dec 2000 13:31:11 +0800

Thanks to the ff for their valuable replies:

John Francini
Steven Hancock
alan_at_nabeth.cxo.dec.com

My original questions are:

1. Whether having both AdvFS V3 and V4 mounted on the same system will have
problems or not.

2. Are there any better approach for migrating large data during a cluster
upgrade.

The answer I got is no, there should not be any problem mounting AdvFS V3
and V4 at the same time on the system. The incompatibility problem comes in
if after you convert to AdvFS V4 on UNIX V5.1 and then later on wants to
move back the volume to UNIX V4.0, which only recognize AdvFS V3.

As for my plan on migrating large amount of data with small downtime window,
I receive positive reply on this so I'm now more confident on moving forward
with my original plan.

Thanks again !

Carlos

Below are extracts of the replies I got:

-------

"You can certainly have AdvFS V3 and V4 volumes mounted on the same
system. They're not compatible in the sense that if you try to use
addvol to add a volume to an AdvFS V3 domain the added volume will
also be Version 3. Only new AdvFS domains created under Tru64 V5.x
will use V4 semantics.

Whether Oracle itself has issues around a mixture of V3 and V4 AdvFS
domains holding a single database is a different question -- can't
answer that one, I'm afraid."

-------

The two on-disk formats are different. Since individual
domains represent different filesets, mixing them isn't
going to be an issue at the file system level (at least
in the single-system case). To take full advantage of
V5 clustering, they may all have to be the new on-disk
format. ASE may have its own restrictions, if you were
using it for failover.

-------

I think your plan makes perfect sense and is exactly the methodolgy
we had in mind for migrating customers with short downtime windows.

You can have both V3 and V4 domains mounted on the same v5.x system
at the same time with no problems. Those V3 domains will simply not
be able to take advantage of some of the new features available in
the V4 format. The V3 domains can migrate back to Tru64 4.x, but not
the V4 domains. So, don't convert until you're sure everything's
working properly.

The only "gotchas" in your plan I can think of are the disk naming
will have to be worked out (eg. rzXX -> dskXX). Once you have that
done, you can easily set up the domain directories in /etc/fdmns with
links pointing to the correct devices. Also, if you're using LSM, this
would make the conversion more complex.





>From: Carlos Chua <chuacarlos_at_hotmail.com>
>To: tru64-unix-managers_at_ornl.gov
>Subject: Need clarification on AdvFS V3 and V4 compatibility
>Date: Wed, 13 Dec 2000 00:05:27 +0800
>
>Hi Systems managers and Gurus,
>
>I'm currently planning to migrate a cluster from V4.0F to V5.1 that has 2TB
>of data spread across 30 domains/mountpoints. I would need some advice on
>whether my plan sounds feasible and at the same time need help to clarify
>on
>how compatible AdvFS V3 and V4 are.
>
>My current environment is Tru64UNIX V4.0F and TruCluster V1.6. Database is
>Oracle and all data reside on around 30 mountpoints (/oradata1,
>/oradat2....) with each having its own AdvFS domain.
>
>My plan for the upgrade is:
>
>1. Set up a new cluster running TruCluster V5.1.
>2. Install application software
>3. Once everything is setup and configured, detach the old storage and hook
>this up to the new cluster. The reason I plan to do this is because we are
>restricted to a max of 6 hrs continuous downtime for the cutover. As I
>don't
>think we'll have sufficient time to backup and restore all the 2TB of data
>in that time frame, I'm planning to physically move the data to the new
>cluster so that at least I can immediately start up the application.
>4. As the data is from the old AdvFS format, I'm planning to do
>backup-recreate domain-restore data gradually thru out a period of time,
>doing probable 10 domains per downtime. Ultimately I would have all the
>data
>residing on the new AdvFS version.
>
>My questions are:
>
>1. Does my last step sense especially for Oracle? My concern is will I run
>into trouble in the middle of the conversion period, when I'll be having
>some Oracle data on AdvFS V4 while some data on AdvFS V3? I've read
>somewhere in the archive that these 2 are not compatible. Does it apply to
>my case? Can I have both AdvFS version mounted on the same OS?
>
>2. Any better work around solution for migrating large data with small
>downtime windows?
>
>Thanks in advance for sharing your experience.
>
>Regards,
>
>Carlos
>chuacarlos_at_hotmail.com
>_____________________________________________________________________________________
>Get more from the Web. FREE MSN Explorer download :
>http://explorer.msn.com
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Received on Fri Dec 15 2000 - 05:33:35 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT