The benefits of using iSCSI for BackupAssist image backups

I often get asked about the best way to create off-site image backups.

One logical approach is to use a windows network share for the destination, however because the destination is not accessible at the disk sector level, the incremental imaging feature can’t be used. A full image backup must be taken each time the job runs which can take significantly more time as well as requiring a larger amount of storage if you wish to keep multiple images.

For this reason, we often recommend that customers stick to local destinations for image backups with history, and plug in either a local dedicated USB hard drive or a pool of USB drives. This approach works very well and allows for multiple images a day, typically taking less than an hour to run on an average SBS server.

However the disadvantages of relying on local backups are clear in that they’re still susceptible to loss, theft and damage. An often overlooked solution for image backups that combines the best features from both of these methods is iSCSI.

So what is iSCSI?

iSCSI is a network protocol that provides a virtual SCSI interface over IP. Simply put, this allows you to create and share a virtual SCSI device over an IP network to be seen on a remote server, as if it was a local attached drive. In our example we will share a virtual hard drive from an iSCSI server ‘target’.

Why is iSCSI different to a Windows share?

With a windows share you create a standard windows folder on a server and specify share permissions in order for other devices to gain access over the network. This folder can have multiple connections to it and works at the file access level. It is seen by the remote device as a network device not a local one, and within BackupAssist is referred to as its unique UNC Path. There is however, no access to the destination at a disk level (blocks/ sectors) and it’s this access that the Windows Image engine requires to be able to compare existing images and perform incremental backups.

iSCSI on the other hand is a block level device share. A standard virtual hard drive container file ‘VHD’ is created on the iSCSI server (target) and is shared to the iSCSI client (initiator) over the network. This client can then mount the virtual hard drive locally (using Computer Management in Windows) and given a drive letter. To the operating system this iSCSI device appears in exactly the same way as a local attached drive and full drive block level access is supported. The read/ write access is also quicker than a windows share and most importantly for backups, incremental imaging is fully supported.

One thing to note, is that generally an iSCSI device is only mounted by one Client at a time. There are advanced clustering capabilities in some iSCSI services to allow multiple servers to connect but in general, an iSCSI share is assigned to only one client at a time (think of them as remote dedicated hard drives).

How do I get an iSCSI server?

There are a few options for building an iSCSI server, you can purchase quite expensive SAN devices that can be configured as iSCSI shares and there are also cheaper NAS devices that are better suited to the SMB environment that also support iSCSI. Alternatively you can install the free iSCSI target initiator provided by Microsoft for Windows 2008 server here. 

For step by step instructions on how to configure this I would suggest you have a look at this excellent Technet blog post by Jose Barreto here.

(source: – follow the setup instructions from the section labelled ‘Loading the iSCSI initiator’.)

If you are new to iSCSI and decide to give this a try, I’d be interested to hear how you get on – also if you have any other iSCSI with BackupAssist related comments please feel free to post them below!

5 thoughts on “The benefits of using iSCSI for BackupAssist image backups

  1. Pingback: RecoverAssist (BackupAssist 6.4) – beta testers needed! | Zen Software blog

  2. Pingback: Testing the BackupAssist beta (v6.4): Windows image backups to an iSCSI target | Zen Software blog

  3. Microlights have been running iSCSI drives with BackUp Assist for a couple of years now. We have 2 Thecus i4500 4tb ( Raid 5 to 3 TB) Devices, one of which holds user data, which is shared through normal AD shares, the other which is the backup of the first. This second one is offsite, connected by 2 CAT5 cables, so is an effective off site back up in the event of fire.

    If you can avoid it, reduce the number of Windows shares on a iSCSI device to a minimum, as in the event of your server failing, you will be able connect your iSCSI device to a new server quickly, but you may run into difficulties with accessing the data if your permissions are locked to a specific (and possibly dead ) server.

    Also ensure you only connect one server to an iscsi device at a time !! Make sure you know how to check whats connected to each device before adding another one – sound obvious, but it is so easy to cock this up !!

    We have just purchased a Thecus 7700Pro with 10tb of data which will be used for VSS backups of our HyperV investment, and will also utilise BackupAssist rSync for offsite storage of SQL transaction logs. Tests are ongoing but heed the 2TB warning – all iSCSI drives must be smaller than 2TB, else you get error messages from Microsoft which are misleading and will get you chasing shadows !!

    I will be looking at 6.4 carefully as the direct to iSCSI reduces the potential to connect to the same iSCSI device from 2 servers and overwrite or corrupt data !!

  4. Pingback: BackupAssist 6.4 is here! Super fast image backups, custom boot media and more… | Zen Software blog

  5. Pingback: Happy New Year + 2012 blog highlights… | Zen Software Blog |

Let us know what you think....

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s