[amukhey]

I just want to validate my theory. If you are migrating a BES Server, where is the PIM Sync for each user is stored--SQL DB (Separate Server--Remote) and will this ensure that it will re-populate once you move servers?

[dev]

The size of a SQL db is roughly 100MB for the initial db + up to ~1MB to 1.5MB per user. Strictly speaking about PIM data, it usually stores PIM data configurations, sync state info, OTA PIM changes...plus others. If you're keeping the SQL db and the other BES-specific data (State db, profiles db), changing servers should not affect PIM data. If you're using a new SQL db, then you'll likely lose all of a users' specific PIM config info. Hmmm...I've never gone inside the SQL db to look for user PIM data before....for other info like server instance name..etc.
Why the brain-teaser?

[amukhey]

Since RIM cant come up with a Fail Over that actually involves no manual intervention (more like a clustered environment like we have for Domino Mail), I am forced to try out options using SQL Replication and 3rd party replication tools (at the bit level and not just replacing files).

I am setting up a test environment, 2 BB servers (4.0 SP5 HF1) 1 SQL Server (ver 2000). I want to shut down my production server, change DNS so the test environment recofgnizes the production as far as DNS and doesnt need me to change anything in Domino...my question comes here: when I bring up the new test remote SQL Server, will it keep the pim sync settings in BB Server Manager for the profiles?

My initial answer is no but then I could be wrong and the only way to find out is to test this theory out.

I am close to completing my tests on this....Il let you all know (and patent it first hopefully if it works).