No, Database Vault does not run as a Windows service. The application executes its backup tasks through the Windows Task Scheduler using the specific credentials provided when the task is created. This design is intentional, as it avoids running a persistent background process and instead triggers operations only at defined intervals.

This matters for server efficiency and operational control. Traditional services consume resources continuously and start at boot, while scheduled tasks run on demand with full access to Windows-native scheduling features, conditions, logging, and security contexts. The result is reduced overhead during non-backup periods and the ability for advanced users to apply fine-grained execution rules without custom service development.

#Windows Services Compared to Scheduled Tasks

Windows services are long-running executables managed by the Service Control Manager. They typically start automatically, run under dedicated accounts, and maintain state across system events. They suit always-on applications such as database engines or monitoring agents. Database Vault focuses on periodic backup jobs, making the Task Scheduler the better fit. The scheduler launches the backup process at precise times or in response to events, handles retries, records history in the event log, and supports complex triggers without requiring a resident service. This keeps the system lean while still delivering dependable automation.

#Benefits of Using the Windows Task Scheduler

  • Precise scheduling including daily, weekly, or event-based triggers with start times aligned to off-peak hours.
  • Fine-grained security context by running under specific domain or local accounts with only the rights required for database access and file I/O.
  • Minimal resource consumption because no process idles between backup windows.
  • Straightforward maintenance since updates to the backup binary do not involve stopping and restarting a service.
  • Built-in Windows capabilities for failure retries, conditional execution (such as only when CPU is below threshold), detailed history, and integration with Task Scheduler's GUI or command-line tools.

#Configuring Backup Tasks in Practice

Begin by identifying or creating a service account that can authenticate to your databases, read source data, and write to the backup destination. Grant this account the "Log on as a batch job" right through secpol.msc. When creating the task, supply these credentials; they are stored encrypted by the operating system. Use the Task Scheduler MMC snap-in for simple setups or PowerShell for repeatable scripting across servers. After creation, run the task manually to validate output and review the History tab for execution details.

powershell 
# Example: Register a daily Database Vault full backup task
$action = New-ScheduledTaskAction -Execute "C:\Program Files\DatabaseVault\dvbackup.exe" -Argument "--type full --output D:\backups"
$trigger = New-ScheduledTaskTrigger -Daily -At 3:00AM
Register-ScheduledTask -TaskName "DatabaseVault-FullBackup" -Action $action -Trigger $trigger -User "svc_dbvault" -Password "StrongP@ssw0rd123" -RunLevel Highest -Description "Automated full backup via Database Vault"

The example above registers a task that executes once per day. Adjust the trigger for weekly runs or add additional actions for chained operations such as compression or offsite copy. After registration, open taskschd.msc, locate the task, and enable the "Run with highest privileges" option if elevated access is required. Always test immediately and confirm backup files are created with correct permissions.

#Troubleshooting and Best Practices

Scheduled tasks can fail for reasons unrelated to Database Vault itself. Common root causes include expired passwords on the run-as account, insufficient NTFS or database permissions, disabled tasks, or system policies blocking batch logon. Enable the task history log via Task Scheduler -> Action -> Enable All Tasks History to capture start, finish, and result codes. Cross-reference failures against the Application event log and any logs written by the backup executable. Microsoft recommends service accounts with non-expiring passwords and strict least-privilege rights.

  • Access denied (0x80070005): Confirm the account can traverse directories, read database files, and write to the target path; check UAC settings.
  • Task never triggers: Verify the schedule, ensure the task is enabled, and confirm the server clock is accurate.
  • Non-zero last run result: Inspect Database Vault's own log files for database connection or backup logic errors.

Practical takeaway: The Task Scheduler gives Database Vault reliable, controllable execution without the overhead of a Windows service. Create tasks with dedicated service accounts, test restores regularly, review history logs weekly, and update credentials promptly when passwords change. Consult the knowledge base article on securing Windows service accounts for additional hardening steps.