Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
1328 views

Migration Checklist


So here's my checklist. I just thought I would post to make sure I
didn't forget anything.

1. Install Pre-migration server in new tree, as documented in Mig.Wiz.
2. Patch
3. Install license
4. Backup source
5. Migrate Data (watch progress from home)
6. Finish Migration tasks
7. Physical switch.
8. Install additional apps on server (backup, UPS, etc).

I two main questions right now.

Is it OK to license the server before migration? and how long will it
take to migrate about 250 Gig of data over 100Mb/s ethernet from a
compressed volume to an uncompressed one ?

Jim Helfer
WTW Architects
Pittsburgh PA
Labels (2)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

Hey Jim,

Kinda. While on paper it looks good, I am running at about a 50% success level.

If the ONLY thing you are doing is a hardware to new hardware upgrade, Please take a look at Portlock Storage Manager. www.portlock.com. I have only used it in a test environment so far but plan to use it tomorrow in production. So far, what would normally be a 1-3 day server migration turned out to be 11 hours from start to finish. The few hundred dollars it costs is worth it.

Your migration with the Migration Wizard will take many, many days. You really need two things. 1. Uncompress that drive! You are going to want to shoot yourself watching bit by bit go across the screen. 2. Gigabit ethernet! Are you by change on time and material? 🙂

Tom


>>> Jim Helfer<jhelfer@wtwarch.com> 6/21/2006 1:55:36 pm >>>


So here's my checklist. I just thought I would post to make sure I
didn't forget anything.

1. Install Pre-migration server in new tree, as documented in Mig.Wiz.
2. Patch
3. Install license
4. Backup source
5. Migrate Data (watch progress from home)
6. Finish Migration tasks
7. Physical switch.
8. Install additional apps on server (backup, UPS, etc).

I two main questions right now.

Is it OK to license the server before migration? and how long will it
take to migrate about 250 Gig of data over 100Mb/s ethernet from a
compressed volume to an uncompressed one ?

Jim Helfer
WTW Architects
Pittsburgh PA
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

250 gigs will take a long time, but you can always get the pre-mig
server set up, and do the "copy files" portion anytime BEFORE the
actual migration. This is the ideal way to do it. Then when its
actually time to do the upgrade, you can tell it to only copy files
that have changed since the last copy.
--



Jim Helfer wrote:

>
> So here's my checklist. I just thought I would post to make sure I
> didn't forget anything.
>
> 1. Install Pre-migration server in new tree, as documented in Mig.Wiz.
> 2. Patch
> 3. Install license
> 4. Backup source
> 5. Migrate Data (watch progress from home)
> 6. Finish Migration tasks
> 7. Physical switch.
> 8. Install additional apps on server (backup, UPS, etc).
>
> I two main questions right now.
>
> Is it OK to license the server before migration? and how long will it
> take to migrate about 250 Gig of data over 100Mb/s ethernet from a
> compressed volume to an uncompressed one ?
>
> Jim Helfer
> WTW Architects
> Pittsburgh PA

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

Jim Helfer wrote:

>Is it OK to license the server before migration? and how long will it take
>to migrate about 250 Gig of data over 100Mb/s ethernet from a compressed
>volume to an uncompressed one ?


yes, and probably over 24 hours - the last time I migrated a server with
that much data compressed, I think it ran 23 hours or so. Best to start
it on a Friday night 🙂

If possible, put a gigabit NIC in the old server temporarily (and the new
one if it doesn't have one) so you can migrate faster.

--
Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

Joe Brugaletta wrote:
> 250 gigs will take a long time, but you can always get the pre-mig
> server set up, and do the "copy files" portion anytime BEFORE the
> actual migration. This is the ideal way to do it. Then when its
> actually time to do the upgrade, you can tell it to only copy files
> that have changed since the last copy.



Seems to be some variety of opinion. 23 hours, many , or at least
overnight.

What I was planning to was start on Friday night. From your
suggestion, maybe I'll start right now, adn see what happens.

I thought about GB networking hardware, but I don't have all of the
pieces here, it might be too late in the game for that.

Thanks for the advice.

Jim
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

No problem, I've done it this way many times (copying the data before
hand). This process will also backup all the trustees too, that
usually takes a bit of time as well.
--



Jim Helfer wrote:

> Joe Brugaletta wrote:
> > 250 gigs will take a long time, but you can always get the pre-mig
> > server set up, and do the "copy files" portion anytime BEFORE the
> > actual migration. This is the ideal way to do it. Then when its
> > actually time to do the upgrade, you can tell it to only copy files
> > that have changed since the last copy.

>
>
> Seems to be some variety of opinion. 23 hours, many , or at least
> overnight.
>
> What I was planning to was start on Friday night. From your
> suggestion, maybe I'll start right now, adn see what happens.
>
> I thought about GB networking hardware, but I don't have all of the
> pieces here, it might be too late in the game for that.
>
> Thanks for the advice.
>
> Jim

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

Joe Brugaletta wrote:

> No problem, I've done it this way many times (copying the data before
> hand). This process will also backup all the trustees too, that
> usually takes a bit of time as well.


The trasnfer actually took about 12 hours, minus open files and such.
As you said, I'll just copy changed files over the weekend. It's nice
to have that chunk done. Going to make the rest of the weekend that much
simpler.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Migration Checklist

Jim Helfer wrote:

>As you said, I'll just copy changed files over the weekend.


just an FYI - when you run the mig wizard, tell it to only copy newer
files. Then, a few screens later it asks you if you want to copy files by
date - do this, it will make it much faster. Tell it to only copy files
modified after the day before you ran the wizard.

If you only tell it to copy newer files, for some reason it takes as much
time to check if the file is newer as it does to copy small files (found
this out moving user home dirs where they were storing their GW archive
files - 10s of thousands of little tiny files). The final copy was taking
as long as the initial copy.

Stopped the final copy and put in the files modified after date and it
zoomed thru the copy.


--
Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.