Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
In RC1 the procedure was to add enough disks to exceed the limit of a 32bit aggregate. I haven't read the release notes for RC2 to check if it is possible to convert without adding disks.
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 21:51 heeft Fletcher Cocquyt het volgende geschreven:
Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Qsm, won't convert, but you can copy from 32 to 64 On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" fcocquyt@stanford.edu wrote:
Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" fcocquyt@stanford.edu wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" fcocquyt@stanford.edu wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Hi Folks,
I recall looking at the DOT 8.1 release notes and man pages.
Check out the man page for the "aggr" command.
In particular "aggr add" has a new flag that causes conversion from 32 bit to 64 bit. I think that you must add at least one disk to the aggr, but not necessarily enough disks to exceed the 32 bit size limit.
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" fcocquyt@stanford.edu wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
Much to my dismay I did find that I had to add enough disks to exceed the 16TB limit for 32 bit aggregates. I don't have enough disk space on my test arrays to try this process out so I'll ultimately have to do it on a live system. I submitted an enhancement request to be able to convert without having the added disk space. I was told it was not in the current plan. I'm hoping it will show up in a later release.
Jeff
On Mon, Nov 28, 2011 at 3:07 PM, Steve Losen scl@virginia.edu wrote:
Hi Folks,
I recall looking at the DOT 8.1 release notes and man pages.
Check out the man page for the "aggr" command.
In particular "aggr add" has a new flag that causes conversion from 32 bit to 64 bit. I think that you must add at least one disk to the aggr, but not necessarily enough disks to exceed the 32 bit size limit.
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" fcocquyt@stanford.edu wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
1. I do not think Data Motion for vFilers between 32 and 64 bits is supported although I cannot find reference right now. 2. VSM from 32 bit aggregate to 8.1 64 bit aggregate does create 32-on-64 bit volume for the duration of VSM relationship. Destination volume will be converted to 64 bit after snapmirror break. 3. You can update HA pair non disruptively from 7.3 to 8.1, there is no need to evacuate vFilers for it.
________________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Tuesday, November 29, 2011 01:41 To: Vervloesem Wouter Cc: toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.bemailto:wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" <fcocquyt@stanford.edumailto:fcocquyt@stanford.edu> wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Andrey is right...here is the reference in the 8.1 docs. 32-bit and 64-bit can mirror only to the same type on the target with Data Motion per the docs.
------ Online migration supports replication of similar volumes by using SnapMirror as the underlying technology. vFiler units can have combination of 32-bit and 64-bit volumes. The source and destination vFiler units must have similar volume types for online migration. For example, if the source vFiler unit has two 32-bit volumes and one 64-bit volume, then the destination vFiler unit must have two 32-bit volumes and one 64-bit volume for online migration.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrey Sent: Monday, November 28, 2011 7:32 PM To: Fletcher Cocquyt; Vervloesem Wouter Cc: toasters@teaparty.net Subject: RE: 8.1 32->64bit volume convert
1. I do not think Data Motion for vFilers between 32 and 64 bits is supported although I cannot find reference right now. 2. VSM from 32 bit aggregate to 8.1 64 bit aggregate does create 32-on-64 bit volume for the duration of VSM relationship. Destination volume will be converted to 64 bit after snapmirror break. 3. You can update HA pair non disruptively from 7.3 to 8.1, there is no need to evacuate vFilers for it.
________________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Tuesday, November 29, 2011 01:41 To: Vervloesem Wouter Cc: toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.bemailto:wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" <fcocquyt@stanford.edumailto:fcocquyt@stanford.edu> wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Our New Corporate Headquarters has Moved! Our NEW Address is: 611 Anton Blvd. Suite 700 Costa Mesa, CA 92626 714-939-2300 All Phone Numbers Will Remain the Same
We want to evacuate the cluster to do a major tray upgrade (removing 5 old EOL trays + adding 5 new DS4243's and a 24 x 2 Tb Sata tray) Just a few minutes ago my Netapp SE sent me an email stating data motion between major revs is not supported. - "The reason: Sync SnapMirror is not supported between major releases of Data ONTAP." Ironic/frustrating since we all along were waiting for 8.1 specifically for data motion support!!
I suppose we could stay on 7.3.5.1 and use data motion to accomplish the tray upgrades, then upgrade to 8.x later without disruption Except we'll be over the size limits on the aggrs with the new trays…ugh.
Since we are in test mode, I'm going to push Netapp for the test point to disable the version check that is blocking the 7.3.5.1 -> 8.1 migration There is "not supported" and there is "may work, but we have not tested it enough"
thanks, Fletcher.
On Nov 28, 2011, at 7:32 PM, Borzenkov, Andrey wrote:
- I do not think Data Motion for vFilers between 32 and 64 bits is supported although I cannot find reference right now.
- VSM from 32 bit aggregate to 8.1 64 bit aggregate does create 32-on-64 bit volume for the duration of VSM relationship. Destination volume will be converted to 64 bit after snapmirror break.
- You can update HA pair non disruptively from 7.3 to 8.1, there is no need to evacuate vFilers for it.
From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Tuesday, November 29, 2011 01:41 To: Vervloesem Wouter Cc: toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.bemailto:wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" <fcocquyt@stanford.edumailto:fcocquyt@stanford.edu> wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
It would be interesting to know the result. I appreciate if you post it whatever outcome is.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] Sent: Tuesday, November 29, 2011 8:01 AM To: Borzenkov, Andrey Cc: Vervloesem Wouter; toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
We want to evacuate the cluster to do a major tray upgrade (removing 5 old EOL trays + adding 5 new DS4243's and a 24 x 2 Tb Sata tray) Just a few minutes ago my Netapp SE sent me an email stating data motion between major revs is not supported. - "The reason: Sync SnapMirror is not supported between major releases of Data ONTAP." Ironic/frustrating since we all along were waiting for 8.1 specifically for data motion support!!
I suppose we could stay on 7.3.5.1 and use data motion to accomplish the tray upgrades, then upgrade to 8.x later without disruption Except we'll be over the size limits on the aggrs with the new trays…ugh.
Since we are in test mode, I'm going to push Netapp for the test point to disable the version check that is blocking the 7.3.5.1 -> 8.1 migration There is "not supported" and there is "may work, but we have not tested it enough"
thanks, Fletcher.
On Nov 28, 2011, at 7:32 PM, Borzenkov, Andrey wrote:
- I do not think Data Motion for vFilers between 32 and 64 bits is supported although I cannot find reference right now.
- VSM from 32 bit aggregate to 8.1 64 bit aggregate does create 32-on-64 bit volume for the duration of VSM relationship. Destination volume will be converted to 64 bit after snapmirror break.
- You can update HA pair non disruptively from 7.3 to 8.1, there is no need to evacuate vFilers for it.
From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Tuesday, November 29, 2011 01:41 To: Vervloesem Wouter Cc: toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.bemailto:wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" <fcocquyt@stanford.edumailto:fcocquyt@stanford.edu> wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Sync Snapmirror requires a lot of common points so I can easily see that failing between major revs. However, a normal Snapmirror should work when going from one rev to a higher rev (but not necessarily in reverse).
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit). The result is that you can't use SM to transfer data from a 32-bit aggregate to/from a 64-bit aggregate. AFAIK, the only way to do that is with QSM, Snapvault, or NDMP.
Personally, I dislike QSM because of the overhead. But since it works at the logical level, it almost always works.
Some basic info here: http://media.netapp.com/documents/tr-3786.pdf
On 11/28/11 8:01 PM, "Fletcher Cocquyt" fcocquyt@stanford.edu wrote:
We want to evacuate the cluster to do a major tray upgrade (removing 5 old EOL trays + adding 5 new DS4243's and a 24 x 2 Tb Sata tray) Just a few minutes ago my Netapp SE sent me an email stating data motion between major revs is not supported. - "The reason: Sync SnapMirror is not supported between major releases of Data ONTAP." Ironic/frustrating since we all along were waiting for 8.1 specifically for data motion support!!
I suppose we could stay on 7.3.5.1 and use data motion to accomplish the tray upgrades, then upgrade to 8.x later without disruption Except we'll be over the size limits on the aggrs with the new traysŠugh.
Since we are in test mode, I'm going to push Netapp for the test point to disable the version check that is blocking the 7.3.5.1 -> 8.1 migration There is "not supported" and there is "may work, but we have not tested it enough"
thanks, Fletcher.
On Nov 28, 2011, at 7:32 PM, Borzenkov, Andrey wrote:
- I do not think Data Motion for vFilers between 32 and 64 bits is
supported although I cannot find reference right now. 2. VSM from 32 bit aggregate to 8.1 64 bit aggregate does create 32-on-64 bit volume for the duration of VSM relationship. Destination volume will be converted to 64 bit after snapmirror break. 3. You can update HA pair non disruptively from 7.3 to 8.1, there is no need to evacuate vFilers for it.
From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt [fcocquyt@stanford.edu] Sent: Tuesday, November 29, 2011 01:41 To: Vervloesem Wouter Cc: toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
The 8.1 system already has 64 bit aggregates. The issue I am seeing is 1 - create 64 bit volume to receive snap mirror from 7.3.5.1 system 2 - issue vfiler dr configure srcvFiler@sourceFiler to initiate the snap mirror 3 - at some point the 8.1 volume 'flips' back to 32 bit.
We are eventually planning to use data motion to non-disruptively migrate the vFilers from the 7.3.5.1 cluster to the 8.1 cluster, then upgrade the 7.3.5.1 system to 8.1
Its not clear how to end up with 64 bit volumes - I heard 8.1 was supposed to have in place 32->64 bit migration?
thanks Fletcher.
On Nov 28, 2011, at 1:35 PM, Vervloesem Wouter wrote:
I thought Fletcher was asking about the conversion of an aggregate (and the volumes within). If you want to migrate your volumes from a 32 to 64 bit aggregate you can use VSM (Volume SnapMirror) starting from ontap 8.1...
Mvg, Wouter Vervloesem
Neoria - Uptime Group Business Park King Square Veldkant 35D B-2550 Kontich
Tel: +32 (0)3 451 23 82 Mailto: wouter.vervloesem@neoria.bemailto:wouter.vervloesem@neoria.be Web: http://www.uptimegroup.be
Op 28-nov.-2011, om 22:21 heeft Chaim Rieger het volgende geschreven:
Qsm, won't convert, but you can copy from 32 to 64
On Nov 28, 2011 12:56 PM, "Fletcher Cocquyt" <fcocquyt@stanford.edumailto:fcocquyt@stanford.edu> wrote: Hi, We're testing out Ontap 8.1RC2 Can someone point out/describe the procedure for converting volumes from 32bit to 64bit?
thanks Fletcher
Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Andrey, George - thanks for the feedback
Anyone have a list of the test points? This one disables model checks -
testpoint -m Dfmutil -n disable-model-checks -e 1 -r 1 –q
Is there one for ontap version checks? Again - I am in pure test mode and have heard many conflicting stories - just want to see what's possible - we certainly were made to hold out for 8.1 for datamotion support for our upgrade plans.
Andrey - can you elaborate on your 8.1 statement ? Cite any TR's ?
thanks
On Nov 29, 2011, at 9:01 PM, Borzenkov, Andrey wrote:
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit).
It's no more so for 8.1 which OP has.
It’s right there in 8.1 release notes:
Starting with Data ONTAP 8.1, you can replicate volumes by using SnapMirror between 32-bit and 64-bit volumes. For both synchronous and asynchronous volume replication, the SnapMirror source and destination volumes can be either 32-bit or 64-bit.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] Sent: Wednesday, November 30, 2011 9:14 AM To: Borzenkov, Andrey Cc: George T Chen; toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
Andrey, George - thanks for the feedback
Anyone have a list of the test points? This one disables model checks -
testpoint -m Dfmutil -n disable-model-checks -e 1 -r 1 –q
Is there one for ontap version checks? Again - I am in pure test mode and have heard many conflicting stories - just want to see what's possible - we certainly were made to hold out for 8.1 for datamotion support for our upgrade plans.
Andrey - can you elaborate on your 8.1 statement ? Cite any TR's ?
thanks
On Nov 29, 2011, at 9:01 PM, Borzenkov, Andrey wrote:
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit).
It's no more so for 8.1 which OP has.
Andrey - does this mean datamotion (vFiler migration) should be possible between 7.3.5.1 and 8.1? (currently we get the error "Minimum ONTAP version required for Automated Online Migration is 7.3.3") We are using the latest OnCommand 5 and NMC 3.1 Last time Netapp support supplied a testpoint workaround to bypass this check - it seems bogus - both source and dest are > 7.3.3
thanks
On Nov 29, 2011, at 9:17 PM, Borzenkov, Andrey wrote:
It’s right there in 8.1 release notes:
Starting with Data ONTAP 8.1, you can replicate volumes by using SnapMirror between 32-bit and 64-bit volumes. For both synchronous and asynchronous volume replication, the SnapMirror source and destination volumes can be either 32-bit or 64-bit.
With best regards
Andrey Borzenkov Senior system engineer Service operations
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] Sent: Wednesday, November 30, 2011 9:14 AM To: Borzenkov, Andrey Cc: George T Chen; toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
Andrey, George - thanks for the feedback
Anyone have a list of the test points? This one disables model checks -
testpoint -m Dfmutil -n disable-model-checks -e 1 -r 1 –q
Is there one for ontap version checks? Again - I am in pure test mode and have heard many conflicting stories - just want to see what's possible - we certainly were made to hold out for 8.1 for datamotion support for our upgrade plans.
Andrey - can you elaborate on your 8.1 statement ? Cite any TR's ?
thanks
On Nov 29, 2011, at 9:01 PM, Borzenkov, Andrey wrote:
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit).
It's no more so for 8.1 which OP has.
Data Motion for vFilers is using synchronous SM for final cutover and SM/sync requires identical major versions on source and destination. Again, this is unrelated to 32 vs. 64 bit. I do not know whether this is just the case of extra QA or there are real technical issues. But keep in mind that SM/sync is using NVRAM forwarding and NVRAM layout can change between major versions …
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] Sent: Wednesday, November 30, 2011 9:34 AM To: Borzenkov, Andrey Cc: George T Chen; toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
Andrey - does this mean datamotion (vFiler migration) should be possible between 7.3.5.1 and 8.1? (currently we get the error "Minimum ONTAP version required for Automated Online Migration is 7.3.3") We are using the latest OnCommand 5 and NMC 3.1 Last time Netapp support supplied a testpoint workaround to bypass this check - it seems bogus - both source and dest are > 7.3.3
thanks
[cid:image001.png@01CCAF44.FFC8AC00]
On Nov 29, 2011, at 9:17 PM, Borzenkov, Andrey wrote:
It’s right there in 8.1 release notes:
Starting with Data ONTAP 8.1, you can replicate volumes by using SnapMirror between 32-bit and 64-bit volumes. For both synchronous and asynchronous volume replication, the SnapMirror source and destination volumes can be either 32-bit or 64-bit.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] Sent: Wednesday, November 30, 2011 9:14 AM To: Borzenkov, Andrey Cc: George T Chen; toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
Andrey, George - thanks for the feedback
Anyone have a list of the test points? This one disables model checks -
testpoint -m Dfmutil -n disable-model-checks -e 1 -r 1 –q
Is there one for ontap version checks? Again - I am in pure test mode and have heard many conflicting stories - just want to see what's possible - we certainly were made to hold out for 8.1 for datamotion support for our upgrade plans.
Andrey - can you elaborate on your 8.1 statement ? Cite any TR's ?
thanks
On Nov 29, 2011, at 9:01 PM, Borzenkov, Andrey wrote:
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit).
It's no more so for 8.1 which OP has.
Hmm, does that mean 8.1 can snapmirror between a trad vol and a flex vol? As soon as I get some free time, I see an experiment coming up :-)
On 11/29/11 9:01 PM, "Borzenkov, Andrey" andrey.borzenkov@ts.fujitsu.com wrote:
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit).
It's no more so for 8.1 which OP has.
No (not for VSM). But it is not related to 32 vs. 64 bit :)
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
-----Original Message----- From: George T Chen [mailto:gtchen@yahoo-inc.com] Sent: Wednesday, November 30, 2011 9:19 AM To: Borzenkov, Andrey; Fletcher Cocquyt Cc: toasters@teaparty.net Subject: Re: 8.1 32->64bit volume convert
Hmm, does that mean 8.1 can snapmirror between a trad vol and a flex vol? As soon as I get some free time, I see an experiment coming up :-)
On 11/29/11 9:01 PM, "Borzenkov, Andrey" andrey.borzenkov@ts.fujitsu.com wrote:
On the other hand, Sync Snapmirror and regular Async Snapmirror are block based and do require that source and destination be the same type (either 32-bit or 64-bit).
It's no more so for 8.1 which OP has.
may have hit a bug, but support dosen't show anything yet...
The time is off on an HA pair 3270's running DOT 8.0.2p3 7-mode. I have other filers that have the same NTP settings and are in synch. I had to manually set the time on these 3270's before I exceeded 5 minutes for my CIFS clients.
Has anyone else noticed or dose anyone have any suggestions?
Thanks
NTP on 8.x seems to much more fragile than it was under 7.x. It will often show as enabled, but not really be running, especially after network glitches.
From a unix box, run `ntpq -p FILER` and see if NTP is running. If it isn't, do options timed.enable off, and then on again.
See https://kb.netapp.com/support/index?page=content&id=1012660 for more details.
John
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of steve klise Sent: Tuesday, November 29, 2011 4:31 PM To: toasters@teaparty.net Subject: 8.0.2p3 NTP issue?
may have hit a bug, but support dosen't show anything yet...
The time is off on an HA pair 3270's running DOT 8.0.2p3 7-mode. I have other filers that have the same NTP settings and are in synch. I had to manually set the time on these 3270's before I exceeded 5 minutes for my CIFS clients.
Has anyone else noticed or dose anyone have any suggestions?
Thanks
I will try that from a nix system.
I already tried to turn it off/on again. Same thing, but thanks, I will try that tomorrow.
Regards
Steve Klise
Storage Engineer, NCDA
__________________________
PALO ALTO MEDICAL FOUNDATION
SUTTER HEALTH INFORMATION SERVICES
PENINSULA COASTAL REGION
Office: 408-523-3163 · Fax: 408-328-1406
e-mail: klises@sutterhealth.orgmailto:abouelj@sutterhealth.org
WARNING: "All e-mail sent to or from this address will be received or otherwise recorded by the Palo Alto Medical Foundation e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient."
________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Clear, John [John.Clear@amd.com] Sent: Tuesday, November 29, 2011 7:06 PM To: steve klise; toasters@teaparty.net Subject: RE: 8.0.2p3 NTP issue?
NTP on 8.x seems to much more fragile than it was under 7.x. It will often show as enabled, but not really be running, especially after network glitches.
From a unix box, run `ntpq -p FILER` and see if NTP is running. If it isn’t, do options timed.enable off, and then on again.
See https://kb.netapp.com/support/index?page=content&id=1012660 for more details.
John
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of steve klise Sent: Tuesday, November 29, 2011 4:31 PM To: toasters@teaparty.net Subject: 8.0.2p3 NTP issue?
may have hit a bug, but support dosen't show anything yet...
The time is off on an HA pair 3270's running DOT 8.0.2p3 7-mode. I have other filers that have the same NTP settings and are in synch. I had to manually set the time on these 3270's before I exceeded 5 minutes for my CIFS clients.
Has anyone else noticed or dose anyone have any suggestions?
Thanks
Steve,
Supposedly it has been fixed in your release, but you might look at burt 459942. I ran across this on my 8.0.1 filers. They mostly seemed to be keeping time once running, but I found they always ran fast after a reboot. Usually about 3 minutes per reboot. The OS upgrades that are supposed to have it fixed still had the problem, but they managed to get in sync within ~5 minutes. It also mentions KB 1010058.
You'll find that most of the timed options don't have any effect in 8.x anymore.
Jeff
On Tue, Nov 29, 2011 at 8:38 PM, Klise, Steve klises@sutterhealth.org wrote:
I will try that from a nix system.
I already tried to turn it off/on again. Same thing, but thanks, I will try that tomorrow.
Regards
Steve Klise
Storage Engineer, NCDA
PALO ALTO MEDICAL FOUNDATION
SUTTER HEALTH INFORMATION SERVICES
PENINSULA COASTAL REGION
Office: 408-523-3163 · Fax: 408-328-1406
e-mail: klises@sutterhealth.orgmailto:abouelj@sutterhealth.org
WARNING: "All e-mail sent to or from this address will be received or otherwise recorded by the Palo Alto Medical Foundation e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient."
From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Clear, John [John.Clear@amd.com] Sent: Tuesday, November 29, 2011 7:06 PM To: steve klise; toasters@teaparty.net Subject: RE: 8.0.2p3 NTP issue?
NTP on 8.x seems to much more fragile than it was under 7.x. It will often show as enabled, but not really be running, especially after network glitches.
From a unix box, run `ntpq -p FILER` and see if NTP is running. If it isn’t, do options timed.enable off, and then on again.
See https://kb.netapp.com/support/index?page=content&id=1012660 for more details.
John
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of steve klise Sent: Tuesday, November 29, 2011 4:31 PM To: toasters@teaparty.net Subject: 8.0.2p3 NTP issue?
may have hit a bug, but support dosen't show anything yet...
The time is off on an HA pair 3270's running DOT 8.0.2p3 7-mode. I have other filers that have the same NTP settings and are in synch. I had to manually set the time on these 3270's before I exceeded 5 minutes for my CIFS clients.
Has anyone else noticed or dose anyone have any suggestions?
Thanks
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Thanks everyone for your responses.
Date: Wed, 30 Nov 2011 01:07:07 -0700 Subject: Re: 8.0.2p3 NTP issue? From: jeff.cleverley@avagotech.com To: klises@sutterhealth.org CC: John.Clear@amd.com; sklise@hotmail.com; toasters@teaparty.net
Steve,
Supposedly it has been fixed in your release, but you might look at burt 459942. I ran across this on my 8.0.1 filers. They mostly seemed to be keeping time once running, but I found they always ran fast after a reboot. Usually about 3 minutes per reboot. The OS upgrades that are supposed to have it fixed still had the problem, but they managed to get in sync within ~5 minutes. It also mentions KB 1010058.
You'll find that most of the timed options don't have any effect in 8.x anymore.
Jeff
On Tue, Nov 29, 2011 at 8:38 PM, Klise, Steve klises@sutterhealth.org wrote:
I will try that from a nix system.
I already tried to turn it off/on again. Same thing, but thanks, I will try that tomorrow.
Regards
Steve Klise
Storage Engineer, NCDA
PALO ALTO MEDICAL FOUNDATION
SUTTER HEALTH INFORMATION SERVICES
PENINSULA COASTAL REGION
Office: 408-523-3163 · Fax: 408-328-1406
e-mail: klises@sutterhealth.orgmailto:abouelj@sutterhealth.org
WARNING: "All e-mail sent to or from this address will be received or otherwise recorded by the Palo Alto Medical Foundation e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient."
From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Clear, John [John.Clear@amd.com] Sent: Tuesday, November 29, 2011 7:06 PM To: steve klise; toasters@teaparty.net Subject: RE: 8.0.2p3 NTP issue?
NTP on 8.x seems to much more fragile than it was under 7.x. It will often show as enabled, but not really be running, especially after network glitches.
From a unix box, run `ntpq -p FILER` and see if NTP is running. If it isn’t, do options timed.enable off, and then on again.
See https://kb.netapp.com/support/index?page=content&id=1012660 for more details.
John
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of steve klise Sent: Tuesday, November 29, 2011 4:31 PM To: toasters@teaparty.net Subject: 8.0.2p3 NTP issue?
may have hit a bug, but support dosen't show anything yet...
The time is off on an HA pair 3270's running DOT 8.0.2p3 7-mode. I have other filers that have the same NTP settings and are in synch. I had to manually set the time on these 3270's before I exceeded 5 minutes for my CIFS clients.
Has anyone else noticed or dose anyone have any suggestions?
Thanks
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611