Create Rubrik SLAs from a CSV File

If you own a Brik, you are familiar with creating new SLAs as it is one of the first things you would do after getting a Brik deployed.

In the world of Rubrik, everything is build around Service Level Agreements. With Rubrik’s unique approach to use SLAs for Backup and Recovery tasks, we have dramatically simplified the Backup Admin’s daily work. Traditionally a Backup Admin would create multiple backup jobs for full, incremental, hourly, daily, weekly, monthly and yearly backups. Additionally the backup admin would create some archival and replication jobs. With Rubrik’s SLA approach all of this can done within a single SLA and dramatically simplify the operational overhead associated with backup jobs.

Sometimes, a single or even a handful of SLAs might not be enough. In this case using the Rubrik interface becomes time-consuming. Luckily Rubrik has an API-First Architecture which means everything you can do in the GUI, can also be done via the APIs.

To make Rubrik’s API even easier to digest, we have a build-in API Explorer. You can get access to it via https:///docs/v1/playground

Read More

Pipedrive and Zendesk Integration

If your Customer Service System and your Sales CRM are separated it is important to integrate the systems. Without a proper integration either your Sales or Customer Service team might be missing important informations. This free Pipedrive and Zendesk integration will help you solve this issue.

Recently I had to use Zendesk as our customer success system and Pipedrive as our Sales CRM. I have worked with Salesforce for the past 6-8 years and love it. Moving to Zendesk and Pipedrive was quiet a bit of change for me. While these two systems are cheaper than Salesforce they do have a couple of drawbacks. When I started out with both systems I was looking for a Pipedrive and Zendesk integration and came across the official Pipedrive plugin for Zendesk. Read More

Corrupt Snapshot Causing View Composer Service Crash

Error during provisioning:Unexpected VC fault from View Composer

The above error might show up in Horizon View, if you try to use a corrupt snapshot for the deployment of new VMs.

How To Identify If  A Corrupt Snapshot Is The Cause?

  • Look at the Microsoft System Event Log on your View Composer
    • You should see something like this:

      The VMware View Composer service terminated unexpectedly. M It has done this 2 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

       

  • Search for FATAL messages in the vmware-viewcomposer.log
    • The following message will indicate a corrupt snapshot

      2015-10-06 17:52:53,956 | WFE thread 9 | FATAL | ServiceCore.WorkflowEngine.WorkflowEngine – Unexpected exception occurred.Error reading single property ‘config.hardware.device’ from managed object: snapshot-15587

       

Read More