The latest TR version is 2.2 dated August 2012 and has this changelog entry: Section 6.15 updated for Data ONTAP 8.1.1 Could you be more specific in which changes are required? As far as I can tell, version 8.1.1 falls under “7.3.5 or later (excluding 8.0)”.
... View more
SnapDrive requires HTTP(S) or RPC connectivity (depending on your setup) to filer to manage LUNs. This can use any interface on filer which has connectivity to server and is enabled for respective protocol.
... View more
The first obvious answer - share ACL change does not affect existing sessions. So users who were connected before remain connected until something forces them to reconnect. Share ACLs are much less granular and flexible than file ACLs, and Microsoft actually recommends exactly opposite - leave share open and control permissions on filesystem level.
... View more
If created from NetApp side, snapshot will not be application consistent. To get application consistent snapshot, it must be coordinated with host. You will need to put applications in consistent state on host and then create snapshot. If you are using VMware, one possibility is to use Snap Manager for Virtual Infrastructure (I believe, today it is part of VSC). It can create consistent snapshot and initiate SnapMirror update.
... View more
Controller is hot pluggable. Wait after “Waiting for giveback” after “cf takeover”, then break with ^C and halt. Now you can pull out controller.
... View more
Just remember that "reboot" is required after setting 'vol options <volname> root'. Doing a failover won't suffice. It will. cf takeover/cf giveback is enough. It provides for moving root volume almost non-disruptively (almost because existing NFS mounts will still become stale and need remount)
... View more
Yes, you need to set option cifs.guest_account and ensure that this Unix user maps to some Windows user which should be considered guest. simsim> options cifs.guest_account nobody simsim> cifs sessions Server Registers as 'SIMSIM' in workgroup 'WORKGROUP' Root volume language is not set. Use vol lang. Using Local Users authentication ==================================================== PC IP(PC Name) (user) #shares #files 192.168.233.1() (DOMAIN\user - nobody[guest]) 1 0
... View more
It does not matter how much physical space is available. You still need logical free space the filesystem (datastore). You can create new datastore in the free physical space and move VM into it.
... View more
Customer has primary site with mix of 32 and 64 bit volumes and DR site. There is drill down procedure which involves breaking snapmirror, testing application on DR site and resuming (resync) snapmirror. Currently DR site undergoes hardware refresh (head swap, decommissioning of ESH2 shelves). It appears that the only space to relocate data from decommissioned shelves is on 64 bit aggregate. So I am looking for the least intrusive way to perform hardware refresh while minimizing changes to existing DR operational procedures. Thank you for taking care of it!
... View more
Yes, I did review this TR and I do not see this scenario described there. I'll try to clarify 1. I have 32 bit source s32 on 32 bit aggregate and destination d64 on 64 bit aggregate 2. snapmirror initialize -S s32 d64. This results in 32 bit volume d64 created 3. snapmirror break d64. This results in d64 converted to 64 bit 4. Now I want to be able to perform "snapmirror resync -S s32 d64" to continue relationship and avoid full reinit As mentioned, I tested this (also via cascading) in 8.1.1 sim and it works (d64 reverts to 32 bit volume after resync), but I would love to have confirmation that it works as intended and is supported.
... View more
After snapmirror break destination is converted to 64 bit. No the question is - is it supported to resync back from 32 bit source and continue 32 bit snapmirror? I tested it on simulator and it seems to work just fine. Which makes sense as it basically reverts destination to pre-64 bit state. But just to be sure - is it really supported? I am currently facing situation when I need either incur serious downtime to convert source to 64 bit, or simply let it continue with 32 bit source. Of course I'd rather avoid downtime if at all possible.
... View more
large raid group size [...] will definately suffer performance Why? Could you explain in more details the reasons? it only needs to pass through 16 disks, as opposed to a raid group size of 24 Could you explain what do you mean under "needs to pass through 16 disks"? Under which conditions does it happen? What operation triggers "pass through 16 disks"?
... View more
These snapshots are also created by schedule. See “snap sched -A”. They can be used to recover data that has been deleted (like destroyed flexible volume), although that probably requires NetApp support. You can disable schedule if you think you won’t need them.
... View more
Could you explain what do you mean under “autodelete snapshot gets created”? What is the difference between “autodelete snapshot” and normal snapshot?
... View more
If aggregate snapshots are enabled, it may be possible to recover data from them. Do not forget that aggregate snapshots are autodeleted when space is low, so if possible stop any activity on this filer to avoid it.
... View more
Well, that’s the worst case. There is no documented procedure to directly head swap from FAS3050 to FAS62xx. And I was told that simply booting 8.0 with root volume from 7.3 was known to cause issues. One possibility is to carve out several unused disks (take spare), install clean 8.x using FAS62xx and then reassign the remaining disks. Then it may be possible to mark old root volume as root and reboot ☺
... View more