Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
I'm finding that my destination volume appears more "FULL" than my source in a XDP relationship.
Source df output...
Filesystem total used avail capacity Mounted on Vserver /vol/Volume_R/ 95TB 93TB 2056GB 98% --- Vserver1 /vol/Volume_R/.snapshot 0B 22TB 0B 0% --- Vserver1 2 entries were displayed.
Destination df output...
Filesystem total used avail capacity Mounted on /vol/Volume_R_dst/ 100TB 99TB 890GB 99% --- /vol/Volume_R_dst/.snapshot 0B 26TB 0B 0% --- 2 entries were displayed.
I've resorted to deleting destination vol snapshots to keep the transfers from running out of space. Aside from not having those snaps on the destination once the transfer completes, am I shorting myself in any other way by this practice? The purpose of this relationship is to snapmirror a 100TB data volume containing multiple LUNs, break the mirror and use host-based copy to migrate from the LUNs at the destination to a NAS share (CIFS) which will be serving the data going forward.
Thanks for not questioning why the F&$% it was configured this way to begin with 😉 This was an inherited config and I'm trying to correct it.