Upgrading from 5.3.x to 6.x includes a WAFL upgrade, in which old snapshots needs to be deleted before upgrade is complete. Since this upgrade is working with low-priority threads, the regular user will just have his WAFL upgraded after a few days/weeks, depending on filer's snap sched settings.

Hope it helps, Eyal.

---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Eyal Traitel - Filer Escalation Engineer CNA, MCSE, CSA, NACA

Network Appliance BV Holland Office Center Kruisweg 799b 2132 NG, Hoofddorp The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Email: eyal@netapp.com ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ----------------------------------------------------------------------

-----Original Message----- From: Tuc [mailto:tuc@ttsg.com] Sent: Monday, February 05, 2001 10:01 PM To: Thomas.L.White@chase.com Cc: taob@risc.org; toasters@mathworks.com Subject: Re: SnapMirror 5.3.6R2 -> 6.0.1R1

in the upgrade to 6.0.1R1 it mentions that all snapshots have to be blown away before allowing snapmirror to run again. But this (as far as I know) refers ro upgrade source as well as

destination

Ihave not seen any comments re: Upgrading one side only.

ERRR?? Where did you see this?

We just upgraded 2 5.3.4RWHATEVER to 6.0.1R1 on Feb 1, and we were told that you had to do both in a snapmirror because of the version issues Brian found. We are having alot of problems with the filers and the systems since the upgrade, but are trying to work it out.

No one told us about deleting the previous snapshots....

Thanks, Tuc/TTSG Internet Services, Inc.

tw

Brian Tao taob@risc.org@mathworks.com on 02/05/2001 12:45:37 PM

Sent by: owner-toasters@mathworks.com

To: toasters@mathworks.com cc: Subject: SnapMirror 5.3.6R2 -> 6.0.1R1

Couldn't find any reference to this error message on NOW:

Sun Feb 4 23:47:00 EST [drp-na1: worker_thread:error]: snapmirror: Filesystem version mismatch for destination volume nocna1_vol0, reverting the version and aborting transfer. SnapMirror will retry until this revert is complete.

That appears on a destination F840 running 6.0.1R1.  Volume

/vol/nocna1_vol0 on the F840 is large enough and is marked offline. "snapmirror status" shows:

Source Dest Status 192.168.50.17:vol0 drp-na1:nocna1_vol0 Idle

Filer 192.168.50.17 is an F740 running 5.3.6R2.  It prints this to

syslog:

Sun Feb 4 23:29:18 EST [worker_thread]: snapmirror: Destination drp-na1 could not accept a complete transfer Sun Feb 4 23:49:18 EST last message repeated 20 times

What is this about filesystem versions?  Is the F840 doing

something about it on /vol/nocna1_vol0? How can I check on the progress of this revert operation?

I guess I should be asking:  are 5.3.x and 6.0.x snapmirrors

compatible? The 6.0 Data Protection Guide doesn't mention caveats or incompatibilities. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't"