Backup Windows for LabTech

On March 28, 2016, in Projects, Scripting, by Cubert aka (Cube Dweller)


Integrated LabTech Backups

Squidworks released today the most cost effective backup solution integrated with LabTech available, coming in at a whopping $1 per agent!

If you are like me, then backups are pretty costly at an average of $40 dollars a server license. If you have a 100 servers to backup, then your monthly bill is $4,000.00 per month; at 12 months is $48,000.00 dollars a year for backup software. What if I told you we can do the same thing, with even more built-in LabTech features and at just $100 bucks?  Yes, $1200 bucks a year is all it will cost the average MSP with 100 server agents to backup every server they manage. For those occasions where you need more, $125.00 bucks get you unlimited agents! Backup every Windows 7 to Windows 10 system and Windows 2008 to Windows 2012 R2 you manage for a single flat fee. Have all the power LabTech can give you with mass management to control and monitor your backups. Get great logging, metrics and history from our intuitive gauges and graphs or see in just a single click where you stand with the safety of your clients files. No guess work needed!

Take command of your backups again!

Here is a peek at what they been working on. Everything you see done here is done inside LabTech never touching the end PC.

Backups a system in four steps



Restore a system in 4 steps



See and access available restore points



See available event logs relevant to backups



See your global statuses fast and easy



Easy to understand metrics



See individual and global restore point time lines




Get the plugin at

Tagged with:

14 Responses to “Backup Windows for LabTech”

  1. Ben says:

    Just curious is this image based backups or just files?

    I see VSS so clearly its utilizing VSS snaps … Even files only would be good at that price …

  2. Both, You are getting a Microsoft HyperV disk that you can mount anywhere, access the full image for barebones restores and or file and folder level restores. There are limitations based on OS type so you would need to read up on what is available at each version of Windows. Windows 7 is a single daily recovery point where Servers are multiple recover point and both simple file and folder restores and full volumes, barebones and such.

    All based on Microsoft Backup Services.

  3. Ben says:

    This is great, going to check it out .. we were just reviewing some alternate options. Right now we use ShadowProtect and then use FTP to manage the backups offsite, but I bet I could do this with normal FTP app if i can access the files/updates individually. I will take a look, good work! keep them coming

  4. m says:

    Looks like a potential time-(and data :)-saver.

    Are there any docs on implementation and/or best practices and/or example setup, etc?

  5. Stefan says:

    – Is the backup data stored on the labtech server?
    – When you have a full backup, and the next day you do another full backup will it be twice the size or will it only check if files have been changed ?

  6. cubert says:

    Stefan, depending on your scenario, yes or no based on selections to options for backup and type of OS.

    WIndows servers have both VSS Full and VSS Copy and will also do auto disk management so that you never run out of backup storage..

    Very cool stuff.

  7. m says:

    Following on to Stefan’s questions (and expanding on mine) will this work across the wire? I.e. could you have a remote site backing up *directly* to a datacenter location?

  8. Seth says:

    So… Both check marks are set and logic would say that to push an installation, I’d do so either from the Backup Windows console or from scripts>backup and recovery>Backup Windows. Not seeing that. Do I need to wait for this to populate? In otherwords, how do you deploy? Console opens up just fine, but not seeing how to deploy.

  9. cubert says:

    Check out our Video Channel for backup video. Should help out

  10. Stuart says:

    Quick one. One of the strongest advantages of Windows Backup on a server is that it doesn’t use drive letters for backups (and therefore hides the drive from viewing and also doesn’t care if the drive letter changes on replacement). From screenshots, it looks like the destination is set by drive letter. Is this correct?

  11. cubert says:

    We support all forms of targets. Using the custom target option you define a target by ID, drive letter or network share.

  12. Eliot says:

    Can the deployment and configuration be scripted? We have 130 workstations we want to back up, and would prefer not to have to install each one manually and touch each one to configure it. Thank you.

  13. Cubert says:

    The one great thing about CW Automate is that anything can be done.

    Once the plugin is installed it created the SQL tables used to store config data about each enabled agent. If you know what data the tables need (agentID, Source drive, Destination Drive, Etc..) You can add that info to the plugins tables during a script execution where you push out commands to setup Windows Backups.

    The plugin does this on a one by one application but if you know what your parameters are going to be for each agent then you can easily script the setup and have script insert into SQL the info needed for plugin to manage moving forward.

Leave a Reply