Restore emails

Hello,

First of all the version you are using is quite old. You should look to upgrade it to latest version 7.1.SP2 (you will have to first upgrade to 6.8.* versions because direct upgrade is not available). You should also check your SQL version because latest versions do not support SQL 2005. More details can be found in the release notes and compatibility guides.

If users want those old emails they can use older version of FireFox or Chrome.

SourceOne do not maintain folder structure of emails archives since every user can have email at different location also copies could have been archived from journal mailbox itself.

Users can do their own OWNER search and restore back to their mailbox whichever folder they like. Just watch for any defects that would have been fixed between the version you have and latest. There has been more than 12 releases since then.

Thanks,

Rajan

I just responded to Pradeep. We are in the process of building a new server so the latest version can be installed. We are working with a EMC partner to figure out how to move all archives over to the new system. We are also implementing new exchange 2013. I was just hoping for a way to automate a restore of emails to all users for a 3 day period without having to do each one one at a time. End users do not have the ability to install software so we would have to install older Firefox for each person which would take longer than just restoring each person. Do we have any options? Would it be easier to wait until after everything gets migrated? With building a new system, can we migrate all email archives over to the new system? I am ok waiting as long as I can tell people that they will have them. These emails are in sourceone but do not show as shortcuts in exchange since they were delivered to the now broken exchange server and it was not in sync with its DAG member.

Sent from my magic phone

Hi,

EMC SourceOne configuration is scalable in nature. You can bring in and take out machines with a little planning once you know what you are doing. An example is when customers want their archive servers or workers to be on Windows 2008 or Windows 2012 servers because soon 2k3 is coming to end of its support life. In such cases you can bring new machines once you have upgrade and with planning retire old machines. Since you are working with a EMC partner, that is a good step for peace of mind.

Unfortunately for restoration you do not have much option when all users are impacted. One option could be just to have SourceOne upgraded to latest version and ask users to run date based search. Out of that date based search they can restore to their mailbox whatever they need.

The only other thing with current version of ES1 I could think of is virtualised IE. I remember we had an IE executable that was virtualised/ThinApp using VmWare when corporate was on nerwer version of IE but there was one application for which we needed older version of IE. For that we didn’t have to install it just run the executable.

Something like this http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026674

My .02 cents in case it helps.

Thanks,

Rajan

So let me see if I understand this because the partner we are working with is talking about restoring emails during the migration process. So we bring a new SourceOne on line and it, for lack of better term, syncs with the current SourceOne. They do a restore of shortcut emails since the old server will not be there the shortcuts wouldn't work. Once the emails that are shortcutted in users mailbox are restored, they are then journaled into the newe system? This process would maintain all emails that are currently on the production system and they would be then on the new system regardless of whether they are still showing in the users mailbox? If that is the case and end users would be able to restore their own emails after the upgrade, I am good with that. I just need to make sure that if I tell everyone that they will be able to restore their own here in about a week, that they can because again, these emails do not show in their mailbox as a shortcut but they are in SourceOne.

Thanks

Joe Matthews

What you need to do is an in-place upgrade of the existing system to the current version which will support your user's current browser version.

Because of the version you are on this will be double upgrade, first to an intermediate version and then to the final version.

There will also need to be sql version upgrade/move since the supported versions changed along the way.

Rajan,

Can two SourceOne servers of different versions scale together? The problem we have is that we need to get everything from that server to a new server (new OS, newest version of SourceOne, new SQL) without losing anything but we don't want to spend too much time on that server if we don't need to. So if we bring a new one online and scale with the existing, does the data replicate or migrate over? do you have any docs on how to migrate an existing SourceOne to new hardware and version?

Thanks

Joe

Hi Joe,

I do not have visibility to all the facts at your site but for majority of the sites who want to go from any version of SourceOne 6.6 to latest version 7.1.SP2, following is how I personally would have done:

===I assume that you would take backup of all file systems used by SourceOne and SQL databases before you start and refer to product documentation especially release notes ====

1. As Gary mentioned upgrade SourceOne to an intermediate version that supports upgrading from 6.6 version and also supports the SQL server version in use because 7.* versions does not support SQL 2005. For this I would start with downloading release notes of 6.8 (any SP) versions and 7.1.SP2.

2. Go through docs to understand the upgrade path then then upgrade to intermediate version.

3. Once first upgrade is finished, then I would look to first move SQL database to another version e.g. SQL 2008 version. Later on these databases could be moved to another SQL version that is supported e.g. SQL 2012. How to move SQL databases from one server to another are explained with steps in SourceOne documentation.

4. Now upgrade from 6.8.* to 7.1.SP2 version.

5. After upgrade make sure everything is working first.

6. Now if we need retire old Master server, worker servers and Native archive servers, we will have new servers ready. Install SourceOne 7.1.Sp2 software components as per the needs.

7. Make sure new servers have taken the roles and working as expected.

8. Remove roles from old servers and bring their services down.

9. Perform all testing to make sure nothing is missed while allocating roles to servers.

10. Preserve old servers for some time before we decommission them all together.

Others may approach differently but that is what I personally could come up with. You may want to discuss with partner that is helping you in detail because they may have access to some info at your site that we do.

Best regards,

Rajan

Something that you shouldn't forget:

Make sure your UNCpaths are correct and available when moving to a new server environment. If you have your indexes available on local disks and you're about to decommission your 'old' servers, you might lose data (Archive, Index, MCL)

Something I find very useful when it comes to doing upgrades and moves.

Use aliases for all shared data locations when you install SourceOne.

Archive, Indexes, Job Logs, SQL, etc.

This way when it time to move to a new server and/or sql it's just a matter of updating DNS with the new location and the alias address doesn't change.

This is also extremely helpful when it comes time for DR.