Consider the following circumstances when creating nested filesets:
- You cannot access a nested fileset if the metadata server that is hosting
the parent fileset is unavailable. In other words, if the
parent fileset becomes a rogue fileset and is unable to be failed over, then
the nested filesets of that parent fileset would also, effectively, be unavailable.
- A FlashCopy® image
is created at the individual fileset level and does not include any nested
filesets. You cannot make a FlashCopy image of a fileset and any nested filesets
in a single operation. This can be of concern if you are required to have
a consistent image of a fileset and its nested filesets. Making FlashCopy images
in multiple operations could lead to ordering or consistency issues.
- To detach a fileset, you must first detach all of its nested filesets.
- It is not possible to revert to a FlashCopy image when nested filesets
exist within the fileset. You must manually detach the nested filesets before
reverting to the FlashCopy image. You can reattach the nested filesets
after the fileset is reverted.
- When creating nested filesets, attach them only directly to other filesets.
Do not attach filesets to client-created directories because a large-scale
restore is more complex.