Comments on: 4 Steps to Developing a Solid Backup Strategy for Exchange http://www.gfi.com/blog/4-steps-to-developing-a-solid-backup-strategy-for-exchange/?utm_source=rss&utm_medium=rss&utm_campaign=4-steps-to-developing-a-solid-backup-strategy-for-exchange Brought to you by GFI Software Fri, 09 Aug 2013 12:13:46 +0000 hourly 1 By: Paul Mah http://www.gfi.com/blog/4-steps-to-developing-a-solid-backup-strategy-for-exchange/comment-page-1/#comment-31885 Paul Mah Fri, 16 Mar 2012 03:41:47 +0000 http://www.gfi.com/blog/?p=3613#comment-31885 @wayne I completely agree. I’ve joined smaller businesses in the past where there was no paper documentation. As systems started breaking down left and right almost immediately was by ‘interviewing’ non-IT staffers who would recall what the previous administrator did to get a clue

]]> By: Nick Dansby http://www.gfi.com/blog/4-steps-to-developing-a-solid-backup-strategy-for-exchange/comment-page-1/#comment-30714 Nick Dansby Tue, 20 Dec 2011 00:30:37 +0000 http://www.gfi.com/blog/?p=3613#comment-30714 The big trade-off being that the more you backup, the longer and more complicated validation becomes, and having a corrupt backup is worse than having no backup at all, for the lost time and resources as well as the false sense of security. When deciding on a backup strategy, one not only has to consider these four factors, but how changing one affects the others.

]]> By: wayne b. http://www.gfi.com/blog/4-steps-to-developing-a-solid-backup-strategy-for-exchange/comment-page-1/#comment-30671 wayne b. Sat, 17 Dec 2011 21:55:45 +0000 http://www.gfi.com/blog/?p=3613#comment-30671 Proper documentation does NOT only correctly set and define the roles of individuals involved in the backup and restoration process, it can also be used as a basis for not making the same mistakes TWICE. This is really important especially if you’re in charge of a large Exchange data – such as the ones maintained in corporations and big organizations.

If your email admin or IT manager decides to leave or resign from your company, and / or you have new employees working on your email, proper documentation can really up the ante.

]]>