About aborzenkov

aborzenkov · ‎2012-10-21

Is your copy strictly unidirectional or you copy data in both directions between two locations? Is data on destination available read-write or read-only? How do you solve collisions (when data was changed on both source and destination)?

aborzenkov · ‎2012-10-20

You cannot. The only thing that can be changed is number of cylinders. But cylinder geometry (sectors per track and tracks per cylinder) is fixed when LUN is created.

aborzenkov · ‎2012-10-17

Two controllers in HA pair are mostly independent systems, so you cannot really import anything. Just build it in standard way, enable CF and use HA config checkers to verify configuration.

aborzenkov · ‎2012-10-17

Yes. It is called - surprise - file-read-file ☺

aborzenkov · ‎2012-10-11

Yes, you can go directly from 7.3.x to 8.1 (check release notes and update guide for prerequisites). Do you have any reason to update at all? Any specific functionality that is missing? Have you ever heard “never touch a running system”? ☺ 8.x is more resource demanding, so 7G may be better choice on low end systems unless you need some features missing in 7G.

aborzenkov · ‎2012-10-11

Well … this thread lists half a dozen issues at least and none of them is related to RLW upgrade. So which issue do you have in mind specifically? ☺

aborzenkov · ‎2012-10-11

If system is correctly configured for failover, it can be done as NDU without downtime. CIFS and NDMP sessions will be interrupted though. Why 8.0.1? I would say, either 8.0.3 latest patch or 8.1.1P1. What is the reason to chose this specific version?

aborzenkov · ‎2012-10-10

OK. He said “disk assign shows no unassigned disks”, so they belong to some other filer. They need to be reassign to this controller.

aborzenkov · ‎2012-10-10

So assign unowned disks to other controller.

aborzenkov · ‎2012-10-09

Users are authenticated using SID not name, so as long as users retain SID they will have the same permissions.

aborzenkov · ‎2012-10-09

I guess after domain name change filer won’t be able to authenticate users. Just rerun “cifs setup” after domain name change. This does mean short outage for CIFS services. You may need to adjust your DNS configuration as well.

aborzenkov · ‎2012-10-05

And how does it answer my question?

aborzenkov · ‎2012-10-04

They did not update source yet.

aborzenkov · ‎2012-10-04

The MAC address for the SP module** is not the same as for the interface e0M~~. I was under the impression these were the same interfaces. No, they are not. They are two different interfaces connected to internal switch that is connected to the wrench port. So they need different IP addresses, and you apparently set them to the same address. See diagram in Administration Guide which explains is very well.

aborzenkov · ‎2012-10-04

One of my customer currently doing VSM from 8.0 to 8.1 until source is updated. All mirrors were retained during target update.

aborzenkov · ‎2012-10-04

Lun move will “rename” it but only within the same volume. If you need to move it to different volume you need to copy it using any available method (snapmirror, ndmpcopy, vol copy) and possible use “lun move” on new volume.

aborzenkov · ‎2012-10-03

The only way to resolve this issue is to have identical UID for identical users on both systems. This is how NFS always worked.

aborzenkov · ‎2012-10-02

No, I did not get any reply as can be seen here My post has two question marks, so I presumed it is clear where the questions were ... I did get advice how to force specific aggregate to be disk root for the next boot and used it during head swap. This worked.

aborzenkov · ‎2012-10-02

Support for online changing to software based disk ownership is available starting with 7.3.1 In 7.3 you have to boot in maintenance mode.

aborzenkov · ‎2012-10-02

Please read tr-3483 for a detailed explanation of space management with LUN.

aborzenkov · ‎2012-10-01

You mount volume on host and use any available tools for host operating system to do it. There are plenty, both for Windows and for UNIX.

aborzenkov · ‎2012-10-01

Follow boot device replacement procedure. Omit all steps that refer to restoring any previous data. https://library.netapp.com/ecm/ecm_get_file/ECMM1280342

aborzenkov · ‎2012-10-01

I do not understand your question. As I understood from your first post, controller B booted, but booted old version. Just repeat software update procedure on controller B. I do not recommend downgrade, this is far less trivial than upgrade and should always be done under guidance of NetApp personnel.

aborzenkov · ‎2012-09-28

It’s total per HA pair.

aborzenkov · ‎2012-09-28

Well, if you put more load on your system by running aggregate scrubbing more often, you should expect some impact …

Re: Help one location Filer to other location filer data copying

Re: lun resize

Re: What is the "easy" way to build a second controller in an HA pair by "importing" data from the f...

Re: Is there an API call to essentially rdfile/?

Re: Upgrading ONTAP 7.3.5 to 8.1 Mode

Re: Data Ontap 8.1 upgrade - RLW_Upgrading process in the background BEWARE!!

Re: Upgrading ONTAP 7.3.5 to 8.1 Mode

Re: FAS3240 boot loop (no disk error)

Re: FAS3240 boot loop (no disk error)

Re: How to adjust the Windows domain name change on filers which are using that domain..?

Re: How to adjust the Windows domain name change on filers which are using that domain..?

Re: system health support for FC HBA/shelves/disks?

Re: 64 bit aggr in place upgrade

Re: SP Port Goes Up/Down

Re: 64 bit aggr in place upgrade

Re: LUN RENAME

Re: how to keep the user and group name the same on two diff NFS clients from the same NetApp NFS se...

Re: Rules for diskroot selection if multiple are present?

Re: [7.3] upgrade_ownership not recognized

Re: fractional reserve % and available disk space

Re: Tree listing within a volume

Re: Need Help...Installing Data Ontap

Re: Takeover of the partner node is impossible due to reason waiting for partner to recover

Re: 3240 6U HA

Re: Data Ontap 8.1 upgrade - RLW_Upgrading process in the background BEWARE!!