Nils Haustein did such a migration from v7000 Unified to ESS last year. Used SOBAR to avoid recalls from HSM. I believe he wrote a whitepaper on the process.. <br><br><br> -jf<br><div class="gmail_quote"><div dir="ltr">tir. 18. jul. 2017 kl. 21.21 skrev Simon Thompson (IT Research Support) <<a href="mailto:S.J.Thompson@bham.ac.uk">S.J.Thompson@bham.ac.uk</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>So just following up on my questions from January.</div>
<div><br>
</div>
<div>We tried to do 2. I.e. Restore to a new file-system with different block sizes. It got part way through creating the file-sets on the new SOBAR file-system and then GPFS asserts and crashes... We weren't actually intentionally trying to move block sizes,
but because we were restoring from a traditional SAN based system to a shiny new GNR based system, we'd manually done the FS create steps.</div>
<div><br>
</div>
<div>I have a PMR open now. I don't know if someone internally in IBM actually tried this after my emails, as apparently there is a similar internal defect which is ~6 months old...</div>
<div><br>
</div>
<div>Simon</div>
<div><br>
</div>
<span id="m_-4271706148215571441OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"></div></span></div><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><span id="m_-4271706148215571441OLK_SRC_BODY_SECTION"><div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:gpfsug-discuss-bounces@spectrumscale.org" target="_blank">gpfsug-discuss-bounces@spectrumscale.org</a>> on behalf of Marc A Kaplan <<a href="mailto:makaplan@us.ibm.com" target="_blank">makaplan@us.ibm.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>" <<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>><br>
</div></span></div><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><span id="m_-4271706148215571441OLK_SRC_BODY_SECTION"><div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"><span style="font-weight:bold">Date: </span>Friday, 20 January 2017 at 17:57</div></span></div><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><span id="m_-4271706148215571441OLK_SRC_BODY_SECTION"><div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"><br>
<span style="font-weight:bold">To: </span>"<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>" <<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [gpfsug-discuss] SOBAR questions<br>
</div></span></div><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><span id="m_-4271706148215571441OLK_SRC_BODY_SECTION">
<div><br>
</div>
<div>
<div><font size="2" face="sans-serif">I worked on some aspects of SOBAR, but without studying and testing the commands - I'm not in a position right now to give simple definitive answers -
</font><br>
<font size="2" face="sans-serif">having said that....</font><br>
<br>
<font size="2" face="sans-serif">Generally your questions are reasonable and the answer is: "Yes it should be possible to do that, but you might be going a bit beyond the design point..,</font><br>
<font size="2" face="sans-serif">so you'll need to try it out on a (smaller) test system with some smaller tedst files.</font><br>
<br>
<font size="2" face="sans-serif">Point by point.</font><br>
<br>
<font size="2" face="sans-serif">1. If SOBAR is unable to restore a particular file, perhaps because the premigration did not complete -- you should only lose that particular file,</font><br>
<font size="2" face="sans-serif">and otherwise "keep going". </font><br>
<br>
<font size="2" face="sans-serif">2. I think SOBAR helps you build a similar file system to the original, including block sizes. So you'd have to go in and tweak the file system creation step(s).</font><br>
<font size="2" face="sans-serif">I think this is reasonable... If you hit a problem... IMO that would be a fair APAR.</font><br>
<br>
<font size="2" face="sans-serif">3. Similar to 2.<br>
</font><br>
<br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">"Simon Thompson (Research Computing - IT Services)" <<a href="mailto:S.J.Thompson@bham.ac.uk" target="_blank">S.J.Thompson@bham.ac.uk</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">"<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>" <<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">01/20/2017 10:44 AM</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[gpfsug-discuss] SOBAR questions</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Sent by: </font><font size="1" face="sans-serif"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org" target="_blank">gpfsug-discuss-bounces@spectrumscale.org</a></font><br>
<hr noshade>
<br>
<br>
<br>
<tt><font size="2">We've recently been looking at deploying SOBAR to support DR of some of<br>
our file-systems, I have some questions (as ever!) that I can't see are<br>
clearly documented, so was wondering if anyone has any insight on this.<br>
<br>
1. If we elect not to premigrate certain files, are we still able to use<br>
SOBAR? We are happy to take a hit that those files will never be available<br>
again, but some are multi TB files which change daily and we can't stream<br>
to tape effectively.<br>
<br>
2. When doing a restore, does the block size of the new SOBAR'd to<br>
file-system have to match? For example the old FS was 1MB blocks, the new<br>
FS we create with 2MB blocks. Will this work (this strikes me as one way<br>
we might be able to migrate an FS to a new block size?)?<br>
<br>
3. If the file-system was originally created with an older GPFS code but<br>
has since been upgraded, does restore work, and does it matter what client<br>
code? E.g. We have a file-system that was originally 3.5.x, its been<br>
upgraded over time to 4.2.2.0. Will this work if the client code was say<br>
4.2.2.5 (with an appropriate FS version). E.g. Mmlsfs lists, "13.01<br>
(3.5.0.0) Original file system version" and "16.00 (4.2.2.0) Current file<br>
system version". Say there was 4.2.2.5 which created version 16.01<br>
file-system as the new FS, what would happen?<br>
<br>
This sort of detail is missing from:<br>
</font></tt><a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.2/com.ibm.spectrum.s" target="_blank"><tt><font size="2">https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.2/com.ibm.spectrum.s</font></tt></a><tt><font size="2"><br>
cale.v4r22.doc/bl1adv_sobarrestore.htm<br>
<br>
But is probably quite important for us to know!<br>
<br>
Thanks<br>
<br>
Simon<br>
<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" target="_blank">spectrumscale.org</a><br>
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank"><tt><font size="2">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size="2"><br>
<br>
</font></tt><br>
<br>
</div>
</div>
</span></div>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>
</blockquote></div>