StoreGrid SP 4.3 Rolling Out

We’re rolling StoreGrid SP 4.3 out to all of our partners right now. Most notably in 4.3, we introduced auto merge for disk backups, AES based encryption, WHMCS ticketing integration, customer level migration for resellers and made disk-image backups 3x faster.

AutoMerge Disk Backups
Disk Image Synthetic Automerge will have volume changes getting periodically merged on top of existing full/synthetic backups with user triggered settings and  also provide instant restores from it’s latest merged VHD to boot up directly in Virtual servers or physical machines.

AES Encryption Support
StoreGrid’s encryption standard will offer another encryption option – AES encryption, apart from the already existing encryption standards of 3DES and Blowfish.

Block Rogue Clients
With this feature, StoreGrid will provide a mechanism by blocking out intruders or rogue clients in the backup server. StoreGrid will check with a block list and allow a client to connect only if the client name does not exist in the block list.

WHMCS Ticketing
StoreGrid server now is integrated with the WHMCS platform for generating service tickets as well, other than invoicing. StoreGrid integrates with the WHMCS tool  to create Service Tickets in WHMCS when, a backup or a restore fails in the StoreGrid backup server.

Customer Migration
Another feature to ease administration for service providers. This feature will allow a customer to move from one reseller to another reseller from the user interface itself.

Learn more from the release notes or download it from partner zone. We look forward to your feedback!

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS
  • http://www.hikingmike.com/ hikingmike

    Blocking rogue clients will be nice. We’ve set up a separate customer to move them to because they keep coming back since the clients took no action, and that way we can keep them deactivated. However the blocking is a better way.

    What does it say on the client end if they are being blocked?

    • Vidhya

      Hi hikingmike,

      Thanks for your feedback. If the client has been blocked in the server, and the user tries to schedule a backup from that client, ” The client (client_name) is restricted by server” will be shown in the backup progress window.

      • http://www.hikingmike.com/ hikingmike

        Ok thanks!

  • http://www.facebook.com/bart.riley.10 Bart Riley

    Is there a way to keep an un-encrypted copy of a VHD locally for rapid mounting, but encrypt to be replicated off-site?

    • Vidhya

      @Bart, Thanks for your inputs. Currently we don’t support having an unencrypted local copy and an encrypted copy at the remote location from the same configuration. We will definitely keep this in mind and try to include it in our roadmap. But if you are looking for a faster local recovery, we would recommend that you backup locally to a server and then replicate to an offsite server. This way you will have the local copy for rapid recovery and the advantage of a redundant copy in your offsite location in case the local server fails.

    • Vidhya

      @Bart, Thanks for your inputs. Currently we don’t support having an unencrypted local copy and an encrypted copy at the remote location from the same configuration. We will definitely keep this in mind and try to include it in our roadmap. But if you are looking for a faster local recovery, we would recommend that you backup locally to a server and then replicate to an offsite server. This way you will have the local copy for rapid recovery and the advantage of a redundant copy in your offsite location in case the local server fails.

  • http://www.hikingmike.com/ hikingmike

    I don’t see any information about upgrade paths in any of the documentation, release notes, or partner zone. Can I apply the 4.3 patch to 4.2 installations (branded client and unbranded server)?

    All that I see is “There is no need to request for a new branded v4.3.0 builds since you
    can upgrade to v4.3.0 from branded v4.2.1 or v4.2.5 installations.” Not from 4.2?

    My goal is just trying to keep up to date here. I don’t want to get stuck too many versions behind.

    • Vidhya

      Hi hikingmike,

      If you running 4.2, then you need to apply 4.2.1 patch on top of 4.2 and then apply the 4.3 patch.You can follow this upgrade path for both branded client and non branded server but remember to upgrade your servers first and then proceed to upgrade your clients. Let us know if you face any issues in the upgrade process.

      • http://www.hikingmike.com/ hikingmike

        Got it. Thank you.