Blog

When I'm running MailStore webinars, I'm frequently asked about file groups and how they work. I've written this article to give you a good idea of how you can manage your existing file groups, how they can be moved around and what to do with those containing older email.

So what exactly is a file group?

ms-file-group.jpg

iscsi-icon.jpgHopefully you're already aware that one of the great new features coming in BackupAssist version 6.4 is the native support for iSCSI targets. This feature allows you to run Windows image jobs that fully support incremental updating and history. This is a great feature for disaster recovery backups as it negates the need to have local media (typically USB hard drives) attached to every server or workstation you want protected. I have covered the idea of iSCSI backups in this previous post, but as part of my help with the beta testing of BackupAssist I'm running some real world speed testing on my own Windows 7 box. The aim being to see how long backups will actually take in order to to get an idea of how often they can be run within the day to provide as up to date a backup as possible of the full system drive.

Over the past few years we've used a variety of different virtualisation tools but have historically always stuck to a mixture of either VMWare tools (esxi, Player and Workstation) or Microsoft’s Hyper-V platform. These have worked really well for building larger virtual server platforms but recently I was looking for a quick and easy to configure tool that I could use on my own desktop PC. I was just looking to build some simple test machines for evaluating software in a range of scenarios. After some browsing I came across Oracle VirtualBox and I must say I've been impressed with it so far.

You may have picked up on the grapevine (or the phone when talking to us!), that there's an exciting new version of BackupAssist in the offing. Well, I can confirm the rumours, version 6.4 is due to include both advanced iSCSI support and RecoverAssist, which will make life considerably easier for those of you performing image backups and bare metal restores on 2008/R2/SBS/Hyper-V/Win7/Vista.

mailstore-proxy.png I don't often get asked about the MailStore proxy, as most of our customers tend to use a local email server of some kind such as MDaemon or Microsoft Exchange where it's not needed. Every so often however, I'll be asked about creating a centralised archiving solution for an off-site POP3/ SMTP service which is where it provides a simple but effective solution. Typically customers using these services will have have been using simple, user-based archiving such as the manual creation of local PST files which may or may not be include in a wider backup strategy - by no means an ideal solution.

One of the key benefits of using BackupAssist in a Hyper-V environment is that only one licence is required on the physical host server in order to perform file level backups across all of the guest machines. In this post I’m going to step through a Hyper-V scenario I come across quite frequently, and show you how to configure a single backup job to provide the following:
  1. Bare metal backup
  2. Recovery of a guest machine in its entirety
  3. Recovery of files from a guest
  4. Exchange mailboxes and near-continuous SQL backup
For this scenario the following set of licences must be purchased for one installation of BackupAssist on the Hyper-V host server. 1 x BackupAssist with Upgrade Protection 1 X Hyper-V Granular Restore Console 1 x Exchange Mailbox add-on 1 x SQL add-on

Scenario 1 – Server configuration2008-server.jpg

In this example I’ll be backing up a single 2008 Hyper-V server running two 2008 guests. VM 1 - 2008 SBS including Exchange VM 2 - 2008 Server R2 with SQL

Before I start, I should warn you, this may be a rare issue that only effects a handful of customers - in particular those that use older NAS hardware. However, through diagnosing this issue I've learned much more about how the media usage report works with BackupAssist rsync jobs and thought it would be useful to share my findings.