📖
Blocky for Veeam® Administration Guide
Return to BlockyFAQPricingContact
  • Blocky for Veeam® Administration Guide
    • Chapter 1: Product Information
      • 1.1 Overview
      • 1.2 Key Features
      • 1.3 Restrictions
      • 1.4 Deduplication
    • Chapter 2: Password Protection
    • Chapter 3: Installation
      • 3.1 Installing
      • 3.1.1 Launch the Installation
      • 3.1.2 License Agreement
      • 3.1.3 Select the installation path and additional tasks
      • 3.1.4 Select Components
      • 3.1.5 Start the Installation
      • 3.1.6 Completing the Installation
      • 3.2 Updating
      • 3.3 Upgrading from Version 2.5 and earlier
      • 3.3 Uninstallation
    • Chapter 4: Configuration
      • 4.1 Start the GUI
      • 4.2 Set initial password
      • 4.3 Change password
      • 4.4. Access Control
      • 4.5 Whitelisted Applications
      • 4.5.1 Automatically whitelist applications
      • 4.5.2 Manually whitelist applications
      • 4.5.3 Whitelist via request table
      • 4.5.4 Invalid whitelist entry
      • 4.6 Notifications
      • 4.7 SMTP Server Configuration
      • 4.8 Save / Load Configuration
      • 4.9 Central GUI Mode
      • 4.10 Add Server
      • 4.11 Server selection
      • 4.12 Define a new Group
      • 4.13 Master Configuration
      • 4.14 Lisencing
      • 4.14.1 Initial Licensing
      • 4.14.2 Install License
      • 4.14.3 License upate and renewal
    • Chapter 5: Monitoring
      • 5.1 Request Table
      • 5.2 Status Information
      • 5.3 Access Log
      • 5.4 License Information
      • 5.5 Alert Notifications
      • 5.6 Windows even logs
      • 5.7 Raw volume access
    • Chapter 6: Diagnostics
      • 6.1 Service Report
      • 6.2 Missing privileges
      • 6.3 System clock tampering
    • Appx A: Setup command line parameters
    • Appx B: BlockyCLI parameters
    • Appx C: BlockyforVeeam® Change Log
    • Open Source Licenses
Powered by GitBook
On this page
  • Chapter 6: Diagnostics
  • 6.1 Service Report
  • 6.2 Missing privileges
  • 6.3 System clock tampering
  1. Blocky for Veeam® Administration Guide

Chapter 6: Diagnostics

Chapter 6: Diagnostics

6.1 Service Report

To help our service analyze unexpected behavior of our software, you can generate a service report by selecting the menu item “File >> Generate Service Report." All service information is stored in the file "C:ProgramDataGrauDataBlockyBlockyforVeeam®_Diag.zip." Generating a service report is also available via the BlockyCLI.

When using the Central GUI, the service report is generated on the active connected target server and must be collected from there once finished.

6.2 Missing privileges

The Blocky GUI requires certain privileges to run properly, so you have to make sure the user is able to gain such privileges.

The required privileges are:

  • SE_BACKUP (SeBackupPrivilege)

  • SE_RESTORE (SeRestorePrivilege)

  • SE_TAKE_OWNERSHIP (SeTakeOwnershipPrivilege)

  • SE_LOAD_DRIVER (SeLoadDriverPrivilege)

  • SE_SECURITY_NAME (SeSecurityPrivilege)

In standard installations, any local or domain admin user is allowed to gain these privileges by default. It is possible to restrict these privileges via local security policies or domain group policies. Please make sure to not restrict these policies for users who need to run the Blocky GUI.

6.3 System clock tampering

BlockyforVeeam® monitors the system clock and detects backward time manipulations. Once such system clock tampering is detected, it will be reported in the Windows event log, and access control will refuse any write access, even from whitelisted applications.

PreviousChapter 5: MonitoringNextAppx A: Setup command line parameters

Last updated 2 years ago