<?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: SAS DATA Migration In General in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478961#M286445</link>
    <description>&lt;P&gt;Now to the real answer: you will have to do a proc cport/proc cimport because of the different processor architecture.&lt;/P&gt;
&lt;P&gt;The main bottleneck IMO will be the physical transfer of the cport files from one server to the other. Unless you can do that via some kind of shared storage volume, this will go over the network and be limited by your ethernet bandwidth.&lt;/P&gt;
&lt;P&gt;Make sure that you have several file copies running in parallel; I've found that single sftp transfers do not saturate the available bandwidth, but multiple copies can.&lt;/P&gt;
&lt;P&gt;Ideally, you set up a process where you have sufficent file transfers running all the time, and start cimporting in the target as soon as you have a first package available. Have a string of cports running permanently on the source server, as long as you have space available.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jul 2018 08:57:41 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2018-07-18T08:57:41Z</dc:date>
    <item>
      <title>SAS DATA Migration In General</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478950#M286442</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are working on a plan to migrate SAS Applications from Unix (AIX 7.1 and SAS 9.4) &amp;nbsp;to Linux (RedHat RHEL 7.4 and SAS 9.4). As part of this, the data is also to be migrated. &amp;nbsp;There are many ways to migrate SAS data. We have around 40 TB data to be migrated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any idea how long would it take , as a sample , to migrate 5GB of data. &amp;nbsp;I vividly remember that it has taken me around 8 hours for &amp;nbsp;2GB data from Mainframes to Linux using PROC CPORT &amp;nbsp;and PROC CIMPORT. This I have done 2 years ago.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions &amp;nbsp;regarding the data migration would really be helpful. How can the data of this volume can be migrated the best possible way. &amp;nbsp; This data has &amp;nbsp;normal sas datasets , spd datasets , catalogs and program files. &amp;nbsp; &amp;nbsp;Program files should not take much time as they are just like ordinary files, which do not require &amp;nbsp;any additional work with SAS Procedures.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 08:06:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478950#M286442</guid>
      <dc:creator>vijayanand</dc:creator>
      <dc:date>2018-07-18T08:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DATA Migration In General [how to improve your question]</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478958#M286443</link>
      <description>&lt;P&gt;Hello &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/51337"&gt;@vijayanand&lt;/a&gt;,&lt;/P&gt;&lt;BR /&gt; &lt;P&gt;Your question requires more details before experts can help.&amp;nbsp;Can you revise your question to include more information?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Review this checklist:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Specify a meaningful subject line for your topic.&amp;nbsp; Avoid generic subjects like "need help," "SAS query," or "urgent."&lt;/LI&gt;
&lt;LI&gt;When appropriate, provide sample data in text or DATA step format.&amp;nbsp; See &lt;A href="https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712" target="_blank"&gt;this article for one method&lt;/A&gt;&amp;nbsp;you can use.&lt;/LI&gt;
&lt;LI&gt;If you're encountering an error in SAS, include the SAS log or a screenshot of the error condition.&amp;nbsp;Use the&amp;nbsp;&lt;STRONG&gt;Photos&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;button to include the image in your message.&lt;BR /&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" style="width: 279px;"&gt;&lt;IMG src="https://kntur85557.i.lithium.com/t5/image/serverpage/image-id/16608i91A52F817EAC9A69/image-dimensions/279x150?v=1.0" width="279" height="150" alt="use_buttons.png" title="use_buttons.png" /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;It also helps to include an example (table or picture) of the result that you're trying to achieve.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;To edit your original message, select the "blue gear" icon at the top of the message and select&amp;nbsp;&lt;STRONG&gt;Edit Message&lt;/STRONG&gt;.&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;From there you can adjust the title and add more details to the body of the message.&amp;nbsp; Or, simply reply to this message with any additional information you can supply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" style="width: 229px;"&gt;&lt;IMG src="https://kntur85557.i.lithium.com/t5/image/serverpage/image-id/16605iAC020BC79315B045/image-size/large?v=1.0&amp;amp;px=600" alt="edit_post.png" title="edit_post.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;SAS experts are eager to help -- help&amp;nbsp;&lt;EM&gt;them&lt;/EM&gt; by providing as much detail as you can.&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-style:italic;font-size:smaller;"&gt;This prewritten response was triggered for you by fellow SAS Support Communities member &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/11562"&gt;@Kurt_Bremser&lt;/a&gt;&lt;/SPAN&gt;&lt;/P&gt;.</description>
      <pubDate>Wed, 18 Jul 2018 08:49:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478958#M286443</guid>
      <dc:creator>Community_Guide</dc:creator>
      <dc:date>2018-07-18T08:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DATA Migration In General</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478959#M286444</link>
      <description>&lt;P&gt;Forget the previous message, I must somehow have clicked onto the wrong space while the page was loading.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 08:50:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478959#M286444</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-07-18T08:50:48Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DATA Migration In General</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478961#M286445</link>
      <description>&lt;P&gt;Now to the real answer: you will have to do a proc cport/proc cimport because of the different processor architecture.&lt;/P&gt;
&lt;P&gt;The main bottleneck IMO will be the physical transfer of the cport files from one server to the other. Unless you can do that via some kind of shared storage volume, this will go over the network and be limited by your ethernet bandwidth.&lt;/P&gt;
&lt;P&gt;Make sure that you have several file copies running in parallel; I've found that single sftp transfers do not saturate the available bandwidth, but multiple copies can.&lt;/P&gt;
&lt;P&gt;Ideally, you set up a process where you have sufficent file transfers running all the time, and start cimporting in the target as soon as you have a first package available. Have a string of cports running permanently on the source server, as long as you have space available.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2018 08:57:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-DATA-Migration-In-General/m-p/478961#M286445</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-07-18T08:57:41Z</dc:date>
    </item>
  </channel>
</rss>

