Batch Data Collection Tool

This Fling generates and collects DCT/SVI logs on multiple Horizon View components, remotely, batchly, and in parallel.

View Components

  • View Connection Server (DCT log)
  • View Security Server (DCT log)
  • View Transfer Server (DCT log)
  • View Agent (DCT log, agent)
  • View Composer Server (SVI log)

Features

  • Support parallel execution mode, and sequential execution mode
  • Configurable and fully automated, so it can be used as a scheduled task
  • Delete old logs, according to setting, to maintain log size
BatchDCT_screenshot_progress
  • File sharing is opened on each server [this service must be enabled and working for the tool to work. In most cases, the service should be running by default]
  • Horizon View 6
  • Windows 7, or Windows server 2008 R2

Requirements

  1. Download PsExec.exe from Microsoft, and put it in the "tools" directory
  2. All systems must be in the same or trusted domain
  3. Current user is domain profile and is system admin
  4. File sharing is opened on each server
  5. Windows 7, Windows server 2008 R2
  6. Horizon View 6

Usage

  • Edit configuration in "config.txt", including:
    1. Target systems to collect logs from
    2. Destination folder to store collected log archive
    3. (Optional) max logs to keep
    4. (Optional) parallel or not
  • Run command "BatchDCT.bat full" or "BatchDCT.bat quick"
  • There are two ways to use this tool. The "full" mode: collects the entire DCT logs, which can be big and the process takes a long time to complete. Note that the logging level depends on the current DCT logging level; BatchDCT will not change the logging level configuration on target servers. The "quick" mode: collects only the most recent log files.

For example, you can set:

  • MAX_FULL_LOGS_TO_KEEP = 2
  • MAX_QUICK_LOGS_TO_KEEP = 7 and create two scheduled tasks (e.g. in Windows Task Scheduler):
  • a) repeat every week, command: "BatchDCT.bat full"
  • b) repeat every day, command: "BatchDCT.bat quick"

If an issue happens and the logs are needed, upload at least one full log bundle (_full.zip), together with all later quick log archives (_quick.zip). Why is this necessary? The logs collected by BatchDCT are in "full" mode and "quick" mode. The "full" logs contain all the information, and the "quick" logs contain only recent updates. So a "full" log might lack recent log files (because the "full" log could have been collected several days ago), and a "quick" log could lack some of the basic information contained in the "full" log.

Known issues and noted behavior

On each target view component server to collect DCT from, the folder /vdm-sdct will be cleared. This folder, created by the DCT tool, is used as output.  This BatchDCT tool will delete that folder each time it runs.

Add a Comment
Report a Bug