Physical reallocation does not inflate volume snapshots (which is likely what your support meant). It does inflate aggregate snapshots so you may need to delete them. As for your other question - thin provisioning may be on different levels so no blanket answer is possible, but yes, if you thin provision on volume level it means making volumes thick.
... View more
If you still have common snapshots between source and destination, you can try update or (if it fails) resync which will always work. If all snapshots are aged off, you need to rebaseline.
... View more
Unfortunately, to my best knowledge this is impossible (using officially known tools at least). Parity and dparity disks consume full disk size when allocated initially, so you cannot replace them with smaller disks. They could be some undocumented internal means to do it 🙂
... View more
What is failover policy? Failover group only defines possible candidates; how these candidates are selected is determined by failover policy.
... View more
The 2552 uses Advanced Drive Partioning to create the root aggregates. Can I be confident that the spare drives in shelf 0 will function as spares for the drives in the new shelf? To my best knowledge they won't. You need to add non-partitioned spare.
... View more
SATA disks are supported. I do not think cDOT MC allows non-mirrored storage, you need to plan your disk space accordingly. Logically, SAS optical cables are needed only to connect components across long distance, what follows, if SAS copper length is enough, I do not see why you cannot use them. MetroCluster is simply two single node clusters with relationship setup, so nothing prevents you from doing it in the field. You will need second cluster license though to build second cluster.
... View more
If you break 32 to 64 snapmirror relationship, destination is automatically converted to 64 bit. As far as I know this is the only case when system does it automatically.
... View more
To avoid confusion - you have fabric metrocluster; stretch metrocluster does not use switches. There is no need to disable cf. Just reconnect one link and when verified that new link is OK reconnect second link. This way you won't lose redundancy (cluster can work with just a single link). As usual, it makes sense to do it off peak.
... View more
Yes, as long as snapshot is still available on secondary, just make it accessible (over NFS or CIFS, as appropriate) and simply copy file over.
... View more
No, it is not common, unless there is misunderstanding and you want something else. What is common is to restore volume state to one of snapshots on snapmirror destination, or to restore individual files from it.
... View more
The only way to get snapshot back is to reverse snapmirror direction and completely rewrite source volume. This is rather disruptive procedure.
... View more
In principle, they are just JBODs with SAS expanders. So there are some chances hooking them to SAS HBA works. Of course, you probably lose all nice features like environment monitoring, error recovery etc. People used previous generation FC shelves this way. Not that I suggest or endorse it of course. License question is out of scope here; you need to ask your HBA vendor whether any license is needed.
... View more
It is not clear - do you ask how to restore content of this snapshot (full or partial) or do you want to literally get snapshot back (I.e., "undelete " it)?
... View more
If the question is whether you can use the same volume both as snapmirror and snap vault destination at the same time - no, you can not. You can use different qtrees on the same volume for QSM and SV, but this won't achieve space savings you mean.
... View more
My understanding is that if I do that, then, when I attach the disks to the new filer, they will show up as 'spare'. No; they won't show at all because they belong to different filer. And special boot menu 4 also always creates root aggregate and volume. So you will need to manually assign each disk (because if they are owned you cannot use wildcards here), destroy root aggregate, zero disks belonging to the aggregate. Exactly as if you just connected the same disks without going via special boot menu. So this step won't hurt but it is also absolutely redundant.
... View more
To communicate both partners must know how to talk to each other. Do "other IP" know how to route to your new IPv6 address? Does your gw know how to route between both subnets? Without seeing actual IPv6 configuration and routing table from both sides it is impossible to even start to guess.
... View more
Documentation describes how to convert FAS2240 into shelf while retaining data on internal disks. If you do not need data, you can simply replace controllers with IOM and connect to existing FAS. All further work (reassigning and zero disks) can be done online from this system. Is it not possible to: Boot the 2240 into maintenance mode and zero the disks. No really; disk zero_spares command is not available in maintenance mode (I do not think you can even destroy aggregate in maintenance mode before you can start zeroing disks). What you can do is to reassign ownership to new system en mass which is easier than doing it disk by disk online.
... View more