MailStore Home - Tips and Tricks - Part 4 - Manual repair corrupted MailStoreFileGroup.fdb files and .fdb backup

Problem:

"The problem occurred when moving my back-up to a new location. Somehow the MailStoreFileGroup.fdb file got corrupted. To cut to the chase is there a way to manually repair the file for my latest database back-up is to old for my comfort. I would rather repair the database and have excess to all my archived mails including the including the possibility of it going wrong. Then on forehand back up from an older back-up and missing those essential mails."

Resolution:

Thanks to MailStore Community powered support:

MailStore Home - Tips and Tricks Part 3 … in the Cloud

Problem:

Actually there is no problem just considering the possibility and ways to move/sync my portable MailStore Home folder to the Cloud Drive

Resolution:

MailStore Home - Tips and Tricks Part 2 - Multiple Home users

Problem: 

Аll of my family use email services and mail archiving by MailStore Home. My desire is they to have personal mailstore archive located in their private folders on our home NAS. If you try to install or run portable MailStore Home from network share you will get the error:

Resolution:

MailStore Home - Tips and Tricks Part 1 - Scheduled Tasks

MailStore is awesome mail archiver. The Home edition is free for personal use. It’s a small, portable and easy to use software designed to make backup, restore and email migration. MailStore supports many different types of mailboxes such as Outlook, Outlook Express, Thunderbird, Exchange Server, Office 365, .EML files and more. It also supports a variety of internet based mail services such as Gmail, Hotmail and Yahoo mail.

MailStore is well known and proven software and my goals are not to make advertisements or yet another product review because such materials you can find enough in the Internet. I’ll show you how to make your life easier despite some restrictions and lacks in Home edition.

Problem:

Automated backup feature is missing in Home edition so I wouldn't have to manually run it every day or week. 

Error in the RPC receive loop: RpcIn: Unable to send

Problem:

Error message above is flooded in Event Viewer on a MS Windows VM guest when vmtools upgrade is performed to 5.1 but I encountered the same error recently after fresh installation of VMWare tools on new VM guest.
Error message for Linux guest is the same. According to KB2036350 - this should be fix the problem, however the tools.conf sometimes is not created.

Jumbo frames in virtual FreeNAS 8.3.1 on ESXi 5.X

... and how to setup vmxnet3 vNIC and Jumbo frames

Problem:

When I set jumbo frames (MTU=9000) on em0 vNIC in virtual FreeNAS I can't get frames bigger than 1500 between the peers, even configuring mtu=9000 in all network elements between end points. Do not be fooled if you see this:

[root@freenas] ~# ifconfig em0 mtu 9000
[root@freenas] ~# ifconfig em0 em0: flags=8843 metric 0 mtu 9000 options=9b
ether 00:50:56:87:xx:xx options=9b ether 00:50:56:87:xx:xx
.....

I did some unsuccessful tests with em0 (in my case vnic is recognized as intel 82545EM) and MTU=9K. Eventually I could not get real jumbo frames between FreeNAS and other vm even inside vSphere host. Probably exception is being in the E1000 driver used by FreeNAS virtual machine though this also depends of physical NICs. em(4) supports variations of the hardware - some do jumbo frames, some don't. It could easily get a lot quirks in a VM, depending on how the VM emulates the card and the mode of networking used. This should show which of the Intel cards is being emulated.

# pciconf -lv | grep -A3 em0