Skip to content
Luca Dell'Oca Principal Cloud Architect @Veeam
Virtual To The Core Virtual To The Core

Virtualization blog, the italian way.

  • Media
  • About me
Virtual To The Core
Virtual To The Core

Virtualization blog, the italian way.

Whitepaper: Best practices for backing up virtual servers with Veeam software and StarWind storage

Luca Dell'Oca, April 4, 2012March 26, 2012

I wrote this whitepaper for StarWind Software:

Best practices for backing up virtual servers with Veeam software and StarWind storage

This document describes how to use StarWind iSCSI SAN both as a production and backup storage. It also explains how to combine StarWind SAN with Veeam Backup & Replication in order to build a reliable storage infrastructure where a user can run virtual machines and ensure their safe backup.

You can download it from the dedicated page on StarWind website, or directly from here:

Whitepaper: Best practices for backing up virtual servers with Veeam software and StarWind storage.

Share this:

  • Twitter
  • Facebook
  • LinkedIn
  • Email
  • Tumblr
  • Pinterest
  • Reddit
  • WhatsApp
  • Pocket
Tech iscsistarwindveeamwhitepaper

Post navigation

Previous post
Next post

Comments (3)

  1. James says:
    April 16, 2012 at 12:34

    I use a Starwind iSCSI target as a datastore attached to two hosts and my physical Veeam box in a test environment in exactly the way your whitepaper describes. The server running the iSCSI target has 48GB of RAM and a 256MB LSI SAS controller. I’m using write back caching as the controller has a BBU but I’m also using some of the system RAM as primary cache. Do you think this is a bad idea? Another aspect of Starwind iSCSI target configuration that I’ve had a hard time finding anything out about is the sizing of the virtual disk on the NTFS partition. Should you leave some free space? I’ve left about 10% free. Your opinion on this would be appreciated.

  2. Luca says:
    April 16, 2012 at 14:05

    Hi,
    using part of the RAM as cache is a really good idea, I totally agreed on it.
    About the size on disk, if you are not going to increase the virtual disk used by StarWind, I think 10% can be ok, maybe you can stay on a more secure situation with something around 15-20%, depending if you are going to use also snapshots created by StarWind itself.

  3. James says:
    April 16, 2012 at 15:06

    Many thanks Luca for taking the time and for your advice.

Comments are closed.

Search

Sponsors

Latest Posts

  • My Automated Lab project: #2 Create a Ubuntu template in VMware vSphere with Packer
  • My Automated Lab project: #1 Install and configure the needed tools
  • Calculate space savings of a XFS volume with reflink and Veeam fast clone
  • A new whitepaper: Veeam Backup & Replication V12 enhanced security and scalability with object storage Secure Mode
  • Enable EVC mode in an existing vSphere Cluster with VCSA and VSAN in it
©2023 Virtual To The Core | WordPress Theme by SuperbThemes