Pages

Thursday, 23 August 2018

It’s been a long time to write any new posts for all of you.
Now I am back again with some great knowledgeable posts on Cloud & Other
useful Products.

Today I am going to introduce with one new Product named as “Kernel for Exchange Server”. In every
organization (IT or Non-IT, Big or Small Size Organization), everyone uses
mailbox servers for exchanging mails communication with critical or sensitive
data. Many of the mail communications have confidential attached files as well
which is very critical to get it lost. Some mails may have some kind of
acceptances or agreement between two authorities for any kind of work or
payment process. What if those mails get lost due to complete mailbox
corruption or some of EDB files got corrupt & you are unable to see those
mails or attached file? How will you recover those files? There are some ways
given by Microsoft to check corruption errors & recover files like Backup
but what if backup files too get corrupted? How will you recover your complete
Data with zero loss?

There are many products available in market to use for such
kind of recovery. One of them is “Kernel for Exchange Server” – Very simple,
user-friendly, just in few click jobs & multiple choices of recovery
options available. This product is a complete solution to keep your
Exchange Server up and running in a good state. It allows recovering data from
corrupted EDB files and backup file, and then allows migrating them to live
Exchange Server, Office 365 or to Outlook PST files. It can also export email
files to MSG and EML file formats.

This product is user-friendly that anyone can use it without
any reference guide to recover or protect corrupted files or migrating files
from listed sources to destinations. It’s just a few click jobs & you will
get the complete recovered data in required availability options.

ROOT CAUSES FOR EXCHANGE SERVER
FAILURES?

It can be exchange
database (EDB) corruption or File system level corruption or Application Level
corruption.

Key Root causes for corruptions are:

Physical Corruptions: Commonly known as Hardware Failure which is
very rare & low level corruption. This may occur due to low level resources
availability on the hardware.

Logical Corruptions: It can be database or application level
corruption. Database corruptions may occur due to invalid index entries, cross
object chain linkage because of engine failure in database. Application corruptions
can results corruption in file header, access control levels.

HOW TO AVOID EDB CORRUPTION ISSUES?

There are some ways
to avoid corruptions in EDB like:

Validate
the hardware components: Should be latest updated version.

Validate
the Exchange Server configurations: Refer Microsoft reference guide for best practices/recommendations to configure the server.

Monitor
the Exchange Services & other components for any alerts or failures:
Scheduled maintenance activities for updates or other configuration check-ups
can avoid failures.

Allow
access to required files/folders for Exchange Server in Antivirus Programs –
Make sure all required ports or access is configured in Antivirus program.

If
possible, use backup tools for taking regular backup of Databases – Backup
files should be saved to external storage for avoiding any backup file
corruptions.

Run
Microsoft Exchange Server Best Practices Analyzer for regular testing for any
issues.

Configure
alerts for regular disk space check-up if space is full to increase spaces in
database – Database should at least have 25% buffer disk space available for
EDB. This alert can be configured via Monitoring Tool.

But what if still
EDB files got corrupted? Then best way is to use any third-party product to
recover corrupted EDB files. Kernel for
Exchange Server is one of the best recovery tools for recovering corrupted
files in just few clicks.

CONFIGURATION STEP:

Here you have to
provide Software Activation Details. Once you buy the software, You will get
the Activation Password on Your registered email ID which You have to enter on
below screen:

Once above required
information is added, below is the software console screen:

USE CASE – RECOVER CORRUPTED
OFFLINE EDB FILE

To start with
recovery, Click on Offline EDB under “Recover or Migrate from any of these
sources”:

Click Next:

Choose corrupted
EDB file path & Click Next:

Now there are 2
Scan Modes available:

Standard Scan: This
option performed low level scanning where EDB files are less corrupted. There
is no identity for corruption type but this type of scanning takes less time.
If EDB files are not recovered using this scanning then it will automatically
proceed for deep scanning.

Deep Scan: For large sized
& highly corrupted files, use Deep scanning mode. This will take long time
as compared with Standard Scan but recovered all data from corrupted EDB files.

In some cases, when recovering corrupted EDB files the
“From” field shows blank values so it is advised to select checkbox "Use
message table to get "From" field".

“Use Disk Space” option will let software use the additional
disk space for large size EDB files with multiple mailboxes to avoid any
failures during recovery.

Once selected scan mode, click Next:

After completing
scanning, Click Finish:

Now You can see all
recovered mailboxes in the software screen:

Similarly, you can
select other available sources options to recover data.

RECOVERY AT DESTINATION LOCATION:

I have shown
recovery as PST file. To save data as PST file, Click on PST file under “Save
or Migrate to any of these destinations”: