Server Migration Pack P2P

[Robert H. Cywinski]

Can anyone who has used the Server Migration Pack P2P give me some feedback on the success of your migration? Are there any caveats to be aware of? The product description seems a bit too good to be true but if it works as described it will save me tons of time.

[Ken Krubsack]

I've used it for a few migrations and generally have had good success. There are definitely caveats, though.

1. If at all possible, have GB all the way from source to target.
2. On the source, make darn sure you have things like database services stopped. You don't want any open files. I'd probably also recommend stopping the HP agent services - you're going to want to install a newer PSP after the migration. Antivirus should be stopped as well.
3. Speaking of installing a new PSP, I'd copy it to a local drive on the source so it gets migrated and you don't have to worry about network drivers not working on your new server.
4. Firewall-type software running on the server will probably give you fits - especially MS ISA server.
5. Have your drive arrays configured on your new server before you start - it's just easier that way.

[Steven Clementi]

Lastly... and last I heard...

...you can ONLY migrate new current generation servers.

I.E. you can not migrate a BL20p G2 to a BL20p G3 or G4. (or a Dl380 G2 to a 380 G3/G4)


Steven

[Robert H. Cywinski]

The source server is running SQL Server. Does this have to be installed on the target server or does it migrate to the destination?

[Rob Buxton]

The target server should be blank. No OS, SQL or anything else. That's what P2P does, copies the entire source server to the target and then updates it with the required drivers.

I've only used P2V and that works well. The caveats noted above about stopping services etc. is good. The less activity on the source the cleaner the copy.

[Robert H. Cywinski]

One last thing. What about partitions? Is this managed in SMP?