<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Moving a shelf, with disks, aggr and data from 2020 to 2040 in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37588#M3471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes that volume would also be forced to move with disks.For saving associated volumes, we need to have a copy of associated volume within the filler, to avoid such forceful physical migration situations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Jan 2012 14:58:43 GMT</pubDate>
    <dc:creator>sharmadevender</dc:creator>
    <dc:date>2012-01-10T14:58:43Z</dc:date>
    <item>
      <title>Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37563#M3459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a DS14mk2AT with 1TB SATA drives attached as aggr1 to a single controller FAS2020.&amp;nbsp; I want to move to that shelf, all of the disks the aggr and the data to a dual controller FAS2040.&amp;nbsp; Is there a procedure to do this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:38:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37563#M3459</guid>
      <dc:creator>brettsnow</dc:creator>
      <dc:date>2025-06-05T06:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37568#M3461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;May be this will help you...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H2 class="bl"&gt;&lt;A name="1205815" target="_blank"&gt;&lt;/A&gt;Physically Moving a volume&lt;SPAN class="nodecor"&gt; &lt;/SPAN&gt;&lt;/H2&gt;&lt;P&gt;&lt;A name="1205816" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;To physically move a volume, complete the following steps.&lt;/P&gt;&lt;P&gt;&lt;A name="1205856" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;/P&gt;&lt;TABLE border="1" cellpadding="5" cellspacing="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH align="left" valign="bottom"&gt;&lt;P&gt;&lt;A name="1315030" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;Step&lt;/STRONG&gt;&lt;/P&gt;&lt;/TH&gt;&lt;TH align="left" colspan="2" valign="bottom"&gt;&lt;P&gt;&lt;A name="1315032" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;&lt;/P&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315036" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;1&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;P&gt;&lt;A name="1315038" target="_blank"&gt;&lt;/A&gt;Enter the following command at the source filer to locate the disks that contain the volume:&lt;/P&gt;&lt;A name="1315039" target="_blank"&gt;&lt;/A&gt;&lt;PRE class="jive-pre"&gt;&lt;STRONG&gt;vol status &lt;EM&gt;vol_name&lt;/EM&gt; -r&amp;nbsp; &lt;/STRONG&gt;&lt;/PRE&gt;&lt;H3 class="bsl"&gt;&lt;A name="1315040" target="_blank"&gt;&lt;/A&gt;Result&lt;/H3&gt;&lt;P&gt;&lt;A name="1315041" target="_blank"&gt;&lt;/A&gt;The locations of the data and parity disks in the volume appear under the volume name on the same line as the labels Data and Parity.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315045" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;P&gt;&lt;A name="1315047" target="_blank"&gt;&lt;/A&gt;Place the volume offline and follow the instructions in the disk shelf hardware guide to remove the disks from the source filer.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315051" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;3&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;A name="1315053" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;Halt and turn off the destination filer. &lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315057" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;4&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;A name="1315059" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;Install the disks in a disk shelf connected to the destination filer. &lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315063" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;5&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;A name="1315065" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;Turn on and boot the destination filer. &lt;/P&gt;&lt;H3 class="bsl"&gt;&lt;A name="1315066" target="_blank"&gt;&lt;/A&gt;Result&lt;/H3&gt;&lt;A name="1315067" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;When the destination filer boots, it places the foreign volume offline. If the foreign volume has the same name as an existing volume on the filer, the filer renames it &lt;EM&gt;volume_name(1)&lt;/EM&gt;, where &lt;EM&gt;volume_name&lt;/EM&gt; is the original name of the volume.&lt;/P&gt;&lt;A name="1315068" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P class="caution"&gt;&lt;STRONG&gt;Caution&lt;/STRONG&gt;&lt;BR /&gt;If the foreign volume is incomplete, repeat Steps 1 and 2 to add the missing disks. Do not try to add missing disks while online--doing so causes them to become hot spare disks.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315073" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;6&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;A name="1315075" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;If the filer renamed the foreign volume because of a name conflict, enter the following command to rename the volume:&lt;/P&gt;&lt;A name="1315076" target="_blank"&gt;&lt;/A&gt;&lt;PRE class="jive-pre"&gt;&lt;STRONG&gt;vol rename &lt;EM&gt;vol-name&lt;/EM&gt; &lt;EM&gt;new-name&amp;nbsp; &lt;/EM&gt;&lt;/STRONG&gt;&lt;/PRE&gt;&lt;A name="1315077" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;&lt;EM&gt;vol-name&lt;/EM&gt; is the name of the volume you want to rename.&lt;/P&gt;&lt;A name="1315078" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;&lt;EM&gt;new-name&lt;/EM&gt; is the new name of the volume.&lt;/P&gt;&lt;H3 class="bsl"&gt;&lt;A name="1315079" target="_blank"&gt;&lt;/A&gt;Example&lt;/H3&gt;&lt;A name="1315080" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;The following command renames the users(1) volume as newusers:&lt;/P&gt;&lt;A name="1315081" target="_blank"&gt;&lt;/A&gt;&lt;PRE class="jive-pre"&gt;vol rename users(1) newusers&amp;nbsp; &lt;/PRE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315085" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;7&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;A name="1315087" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;Enter the following command to bring the volume online in the new filer:&lt;/P&gt;&lt;A name="1315088" target="_blank"&gt;&lt;/A&gt;&lt;PRE class="jive-pre"&gt;&lt;STRONG&gt;vol online &lt;EM&gt;vol-name&lt;/EM&gt;&lt;KBD&gt;&lt;STRONG&gt;&amp;nbsp; &lt;/STRONG&gt;&lt;/KBD&gt;&lt;/STRONG&gt;&lt;/PRE&gt;&lt;A name="1315089" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;&lt;EM&gt;vol-name&lt;/EM&gt; is the name of the volume.&lt;/P&gt;&lt;H3 class="bsl"&gt;&lt;A name="1315090" target="_blank"&gt;&lt;/A&gt;Result:&lt;/H3&gt;&lt;A name="1315091" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;The following events occur:&lt;/P&gt;&lt;UL&gt;&lt;A name="1315092" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;LI&gt;The volume is online in its new location. &lt;A name="1315093" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;/LI&gt;&lt;LI&gt;Entries in the /etc/exports file and shares that refer to the volume become incorrect. &lt;A name="1315094" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;/LI&gt;&lt;LI&gt;The in-memory information about active exports gets updated automatically, and clients continue to access the exports without problems. &lt;/LI&gt;&lt;/UL&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315098" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;8&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;A name="1315100" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;Enter the following command to confirm that the added volume came online:&lt;/P&gt;&lt;A name="1315101" target="_blank"&gt;&lt;/A&gt;&lt;PRE class="jive-pre"&gt;&lt;STRONG&gt;vol status &lt;EM&gt;vol-name&lt;/EM&gt;&lt;KBD&gt;&lt;STRONG&gt;&amp;nbsp; &lt;/STRONG&gt;&lt;/KBD&gt;&lt;/STRONG&gt;&lt;/PRE&gt;&lt;A name="1315102" target="_blank"&gt;&lt;/A&gt;&amp;nbsp; &lt;P&gt;&lt;EM&gt;vol-name&lt;/EM&gt; is the name of the volume.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD rowspan="3" valign="top"&gt;&lt;A name="1315106" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;9&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315108" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;If you have...&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315110" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;Then...&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315114" target="_blank"&gt;&lt;/A&gt;An NFS-only filer&lt;/P&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315116" target="_blank"&gt;&lt;/A&gt;Go to Step 11.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315120" target="_blank"&gt;&lt;/A&gt;A CIFS-only or multiprotocol filer&lt;/P&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315122" target="_blank"&gt;&lt;/A&gt;Create shares that refer to the new volume to enable clients to access it, then go to Step 10.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD rowspan="3" valign="top"&gt;&lt;A name="1315124" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;10&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315126" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;If you have...&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315128" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;Then...&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315132" target="_blank"&gt;&lt;/A&gt;A CIFS-only filer&lt;/P&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315134" target="_blank"&gt;&lt;/A&gt;You are done.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315138" target="_blank"&gt;&lt;/A&gt;A multiprotocol filer&lt;/P&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;&lt;P&gt;&lt;A name="1315140" target="_blank"&gt;&lt;/A&gt;Go to Step 11.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315142" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;11&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;P&gt;&lt;A name="1315144" target="_blank"&gt;&lt;/A&gt;Update the system /etc/exports file with the new volume.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315148" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;12&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;P&gt;&lt;A name="1315150" target="_blank"&gt;&lt;/A&gt;Run &lt;KBD&gt;exportfs&lt;/KBD&gt;.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;A name="1315154" target="_blank"&gt;&lt;/A&gt;&lt;STRONG&gt;13&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD colspan="2" valign="top"&gt;&lt;P&gt;&lt;A name="1315156" target="_blank"&gt;&lt;/A&gt;Add the appropriate mount point information to the /etc/fstab or /etc/vfstab file on clients that mount volumes from the filer.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-DEV&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 13:24:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37568#M3461</guid>
      <dc:creator>sharmadevender</dc:creator>
      <dc:date>2012-01-10T13:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37573#M3463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;cool!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is it ever possible for the physical disks to be associated with another volume as well? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 14:08:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37573#M3463</guid>
      <dc:creator>CCOLEMAN_</dc:creator>
      <dc:date>2012-01-10T14:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37578#M3465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What kind of association ? Request you to elaborate &lt;SPAN __jive_emoticon_name="confused" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/confused.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 14:44:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37578#M3465</guid>
      <dc:creator>sharmadevender</dc:creator>
      <dc:date>2012-01-10T14:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37583#M3468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm just curious if data from more then 1 volume can exist on a single disk? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and if it can, what happens when&amp;nbsp; you start pulling out the physical disks? Maybe you're forced to move it as well? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 14:50:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37583#M3468</guid>
      <dc:creator>CCOLEMAN_</dc:creator>
      <dc:date>2012-01-10T14:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37588#M3471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes that volume would also be forced to move with disks.For saving associated volumes, we need to have a copy of associated volume within the filler, to avoid such forceful physical migration situations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 14:58:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37588#M3471</guid>
      <dc:creator>sharmadevender</dc:creator>
      <dc:date>2012-01-10T14:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37593#M3474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been asked for more details;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FAS2020 is single controller&lt;/P&gt;&lt;P&gt;Data OnTap 7.2.4L1&lt;/P&gt;&lt;P&gt;12 internal 300GB drives - aggr0 is here&lt;/P&gt;&lt;P&gt;one expansion shelf - DS14mk2AT with 4 1TB drives - aggr1 is here&lt;/P&gt;&lt;P&gt;all data in aggr1 (DS14) is CIFS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FAS2040 dual controller&lt;/P&gt;&lt;P&gt;Data OnTap 7.3.6&lt;/P&gt;&lt;P&gt;12 internal 600GB drives - aggr0 (cn1) and aggr 0 (cn2)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to move the DS14mk2AT with 4 1TB drives with the volumes, aggr1 and all data.&amp;nbsp; This aggr is NOT shared with the other aggr on the FAS2020, so all volumes and data in that aggr are on DS14 and 1TB drives.&amp;nbsp; So I want to move the shelf with the drives, not just the drives themselves.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am hoping it is as easy as offline all volumes in the DS14 aggr.&lt;/P&gt;&lt;P&gt;Off Line aggr on DS14&lt;/P&gt;&lt;P&gt;Halt 2020&lt;/P&gt;&lt;P&gt;Physically move DS14 cables from FAS2020 to FAS2040.&lt;/P&gt;&lt;P&gt;Bring up new DS14 storage on FAS2040&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully all data will be in place and all CIFS ACL info will be consistent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Verify all CIFS data can be seen/shared with all existing hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 2020 and 2040 have a SnapMirror relationship today, and the CIFS data is on the 2040, but on aggr0 on the 600GB drives.&amp;nbsp; It needs to be on the 1TB drives.&amp;nbsp; So hopefully by moving the shelf and the 1TB drives, the data will be intact and moved to the 2040.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this make sense.&amp;nbsp; Does this sound workable and reasonable?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 17:59:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37593#M3474</guid>
      <dc:creator>brettsnow</dc:creator>
      <dc:date>2012-01-10T17:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: Moving a shelf, with disks, aggr and data from 2020 to 2040</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37598#M3477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;2020 : halt&lt;/P&gt;&lt;P&gt;2040 : cf disable then halt both nodes&lt;/P&gt;&lt;P&gt;plug ds14 shelf into 2040&lt;/P&gt;&lt;P&gt;SERIAL or RLM : boot 2040 into maintenance mode (second CTRL-C at boot and choose option 5 ). At question "continue with boot" press Y&lt;/P&gt;&lt;P&gt;At maintenance mode prompt :&lt;/P&gt;&lt;P&gt;"disk show -v" (to check that all 1Tb disks are present)&lt;/P&gt;&lt;P&gt;"disk reassign" to change old disk serial by new one - serial number of your controller is available with "sysconfig -v"&amp;nbsp;&amp;nbsp; Syntax:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;&lt;STRONG&gt;disk&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;&lt;STRONG&gt;reassign&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt; {-o &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;&lt;EM&gt;old_name&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt; | -s &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;&lt;EM&gt;old_sysid&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;} [-n &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;&lt;EM&gt;new_name&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;] [-d &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;&lt;EM&gt;new_sysid&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Times; text-align: -webkit-auto; font-size: medium;"&gt;]&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;halt&lt;/P&gt;&lt;P&gt;at loader prompt : boot_ontap&lt;/P&gt;&lt;P&gt;once booted :&lt;/P&gt;&lt;P&gt;check everything is there "aggr status" "vol status" "sysconfig -r" then re-enable cluster : "cf enable"&lt;/P&gt;&lt;P&gt;done&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2012 21:36:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Moving-a-shelf-with-disks-aggr-and-data-from-2020-to-2040/m-p/37598#M3477</guid>
      <dc:creator>mrousseau</dc:creator>
      <dc:date>2012-01-16T21:36:07Z</dc:date>
    </item>
  </channel>
</rss>

