Under 1000 DBs left.
November 17, 2008
It may have been quiet on here, but I’ve been busy cleaning up our Notes environment.
And we have hit what I feel is a nice milestone we have under 1000 Notes databases left on our productions servers, and that includes the system databases and others that I know we don’t need to worry about migrating.
Another 500 should be gone at the 1st of the year, and I’mn hoping to enter 2009 with only about 250-300 databases to worry about.
(Of course, some of those 250 are very large, complex, apps.)
November 19, 2008 at 12:17 pm
How did you prioritize?
What does the server topology look like now versus what notes is/was?
email me, I’d like to know more. My customers would like to know but many are in co-existence mode…
November 20, 2008 at 7:10 am
@1) I focused first on the old, dead databases that have not been touched in years. There is no technical work with those, just communications, archivals, data storage, and deletion. I then focused on what I call my “roadblocks” — the databases that have become a virtual infrastructure for the Notes environment. For example, databases that hold user or organizational data for multiple other Notes databases. I created mew data sources for these, either in SharePoint or ACtive Directory, then used AJAX calls from my client and web apps to query for the data. Once that dev work was done, I could delete all that “glue” within the Notes environment. I’m now left with a smaller number of databases that are not very interconnected, so I can attack them one at a time. At this point, I’m prioritizing the easy stuff first. Calendar, mailboxes, discussions, etc. I’m leaving the hard stuff for the end of the migration, but trying to refactor and simplify as we do maintenance work, so that when we are ready to tackle the large, complex Notes apps, they should be simpler and easier to manage.
November 20, 2008 at 10:10 am
Just wondering whether you are using any third party tools (like Cashal or Quest) for doing the actual migration.
November 20, 2008 at 12:40 pm
@3) Nope – we considered them, but out budget this year was very limited, so we were told to do what we could without 3rd party tools or contractor support.
I think they would add value to large migrations, though… in particular if they can migrate data for you.