[Tacfire11]

Hello Experts,

Got the system finally running, and the Transporter tool worked , migrating three users successfully. Howerver, I noticed it took about 5 minutes per user. Hmmm, I have over 4,500 Users they want to cut over in one night. Doing the Math, the numbers aren't looking too good :(.

Anyone ever did a large migration with the transporter tool?

What was your maximum throughput you were able to achieve?

Will the Transporter Tool multi-thread?

Can I run multiple transporter tool sessions against the same database reliably?

Thanks everyone .

[icontech]

Bump this up I have the same questions.

[BB1877]

I'm not using BBET for a large number of users, only about 100. It's taking about 12 minutes each, but I am going from a USA server to one in Belgium over a MPLS link. You have to just let it cook...it appears to hang or quit responding, but it actually working. I'm doing it in small batches. Trying to do a large number of users with it would scare me from what I've seen.

I had it completely hang once, but luckily it was between users, so I had a couple users that were moved okay, and the remaining just had to be run again.

I've also run into a bug whereby once the migration is complete, the user's OTA address book sync is broken. (Notes environment...the properties for address book sync which should show the mail server won't even display in the BES interface, it throws an error...I hate the new web interface but that's a different post).

The solution has been to drop the user off the 5.0.1 destination BES, readd them, and EA. If I add a user fresh to the 5.0.1 BES, the address book sync works properly. RIM can't track it down and is likely related to our mixed Notes environment (source BES is 6.5, destination, 8.5).

These multiple steps aren't as clean as I'd like of course, but beats the alternative which would require a handset wipe. At least BBET is getting the user to the new BES.

[icontech]

Originally Posted by BB1877

I'm not using BBET for a large number of users, only about 100. It's taking about 12 minutes each, but I am going from a USA server to one in Belgium over a MPLS link. You have to just let it cook...it appears to hang or quit responding, but it actually working. I'm doing it in small batches. Trying to do a large number of users with it would scare me from what I've seen.

I had it completely hang once, but luckily it was between users, so I had a couple users that were moved okay, and the remaining just had to be run again.

I've also run into a bug whereby once the migration is complete, the user's OTA address book sync is broken. (Notes environment...the properties for address book sync which should show the mail server won't even display in the BES interface, it throws an error...I hate the new web interface but that's a different post).

The solution has been to drop the user off the 5.0.1 destination BES, readd them, and EA. If I add a user fresh to the 5.0.1 BES, the address book sync works properly. RIM can't track it down and is likely related to our mixed Notes environment (source BES is 6.5, destination, 8.5).

These multiple steps aren't as clean as I'd like of course, but beats the alternative which would require a handset wipe. At least BBET is getting the user to the new BES.

Thanks for sharing. I found documentation on Transporter 5.0.2 but can't locate the download. It has a bunch of fixed issues. I have around 600 users that I need to migrate and I'm trying to figure out what kind of downtime I need. From what I've read, if the migration works successfully then users would only have a delay of email during that time only.

[knottyrope]

BES 5 SP 2 has not been released yet.

[JavaJunkee]

Originally Posted by Tacfire11

I have over 4,500 Users they want to cut over in one night.

Wow! I didn't trust the migration tool to migrate my users en masse.

I have around 550 and moved them in small batches of 10 - 20 over the course of several weeks. Call me paranoid, but I wanted to be able to closely monitor all moves, to ensure IT Policy, Service books, etc were set correctly. I had several migrations that did fail, as well as a dozen or so that for what ever reason didn't take the IT Policy. Had to trouble shoot each one.

Good Luck

[icontech]

Originally Posted by knottyrope

BES 5 SP 2 has not been released yet.

Yes its odd that they publish documentation before the software is available for download.

[nike9090]

It maybe technically possible to move all the accounts on the server side, but can the support handle all the calls/issues in the morning ?

RIM and other large companies indicate that 12% of the users will need support during/after migration.

Found that it's best to locate the OLD BES, NEW BES and the Transporter server in the same data center. Regarding speeds, it depends on how quick can the device acknowledge policy changes.

[Flo_ACC]

When i did my migration i did it in 1 morning by waves of 20 users. if i remember it's the max (if my memory is good).

regarding move process it took me less than 10 minutes to move 20 Users, now it depend of your link between servers. if it's local network using Giga bytes it should be faster.

[icontech]

Originally Posted by Flo_ACC

When i did my migration i did it in 1 morning by waves of 20 users. if i remember it's the max (if my memory is good).

regarding move process it took me less than 10 minutes to move 20 Users, now it depend of your link between servers. if it's local network using Giga bytes it should be faster.

How many total users? Any issues? Thanks

[Flo_ACC]

Originally Posted by icontech

How many total users? Any issues? Thanks

it wwas a small amount : 60 users in total by waves of 20 as i said.....

i had few problems but it was because before this migration the old admin did a migration and did it wrong so i had problems with few phones ... but i was a really exotic problem ....

[Tacfire11]

We did a run of 342 Pilots users the other night, and only encountered 9 Users which required after migration support (so all in all about a 2.2% failure rate). Has anyone ever tried to run multiple Transporter tools against the Source and Target Configuration Databases? Did it work. I will be moving 1,125 tomorrow night in Mass. So I will post and let you know you how it goes.

[Tacfire11]

Oh forget to mention, this run took exactly 1:52 mintues to move 342 Users.

[icontech]

Originally Posted by Tacfire11

Oh forget to mention, this run took exactly 1:52 mintues to move 342 Users.

Thanks for the feedback. Only around 2 hours for 342 users isn't bad at all. I have about 545 users to migrate this weekend.

We're you using the 5.0.2 version of Transporter that was released yesterday? I've already updated my BES to SP2 so I'm thinking I should use the new version of Transporter as well.

Below is a known issue listed in the release notes of Transporter SP2. I also think I read somewhere that only one instance of Transporter should be connecting to a source and destination database at the same time.

(DT 666612) If you use the BlackBerry Enterprise Transporter to move more than 300 user accounts from a BlackBerry
Enterprise Server Express instance to a BlackBerry Enterprise Server instance while the source and destination servers are
processing email messages and other tasks, the BlackBerry Enterprise Transporter might not be able to move all of the user
accounts.
Workaround: Move 100 user accounts at a time from the source BlackBerry Enterprise Server Express to the destination
BlackBerry Enterprise Server.

[icontech]

Originally Posted by Tacfire11

We did a run of 342 Pilots users the other night, and only encountered 9 Users which required after migration support (so all in all about a 2.2% failure rate). Has anyone ever tried to run multiple Transporter tools against the Source and Target Configuration Databases? Did it work. I will be moving 1,125 tomorrow night in Mass. So I will post and let you know you how it goes.

Any consistency to the users that required support? Device model, OS, etc? Thanks

[Tacfire11]

Originally Posted by icontech

Any consistency to the users that required support? Device model, OS, etc? Thanks

The one behavior I've noted is that users whose units have not applied the last IT Policy sent, are basically skipped. The only other issue I discovered was Four (4) users required resending the Service Books. That may have been they were out of service area, turned their handhelds off in the middle of the policy being applied.

We are pushing a larger number tonight, so I will let you know. I'm going to try and throw 1,500 users tonight with the tool. My anticpated failure rate is 85, or about 5% based on the last run. I'll update everyone tomorrow, how the migration went, and depending on the outcome, how much of Butt Cheeks are left ;).

[Tacfire11]

OK Guys, drum roll please.... Here's the results from last night. We queued up 1,580 users in a single batch an let her fly. Here's the numbers.

Total Users to Migrate: 1,580
Run Time: 11hrs, 43 Mins
Average Users per hour: 135

Migration completed successfully (1st Pass) - 417
Migratoin Completed, but pending Policy - 1,099
Migration Skipped due to Violation - 64
Projected Failue Rate: 10%
Actual Failure Rate: Less than 5%


Ok, so the real question - Morning after - help desk calls logged: 2