Database Vault supports storing of server backups on local drives (internal, external, USB attached, network attached) and FTP servers with both standard and secured connections. These methods are fully supported and work with all Database Vault features including scheduling, compression, encryption, and point-in-time restore.

Backup location choice directly affects recovery time, security posture, and resilience. Local storage minimizes latency for fast backups and restores. FTP enables off-server copies that survive local hardware failure or site-wide incidents. The engineering team updates Database Vault regularly to add new storage options.

#Supported Storage Methods

The following storage backends are available today and impose no restrictions on any Database Vault capabilities. Always verify that the target has sufficient capacity and that the account running the backup process has write access.

  • Local Drive (USB attached, internal, external, or network-attached storage)
  • FTP Server (standard FTP and secured connections)

#Local Drive Backups

Local drives deliver the highest performance because data never leaves the server or local network. Use a dedicated volume or folder separate from database files to avoid I/O contention. Network-attached storage must be mounted and visible to the service account before the backup job starts.

#Configuration Steps

  • Specify the absolute path to the target directory in the Database Vault backup job settings.
  • Confirm the SQL Server service account or backup agent has full control permissions on the folder.
  • Monitor free space with alerts; a full volume will cause backup jobs to fail.

#FTP Server Backups

FTP targets move backups off the server, supporting geographic redundancy. Provide host, credentials, and remote path. Secured connections encrypt data in transit and should be used whenever the backup traverses public or untrusted networks. Test connectivity inside Database Vault before enabling scheduled jobs.

ini 
; Example FTP target settings for Database Vault
[BackupTarget]
Type=FTP
Host=ftp.contoso.com
Port=21
Username=backupagent
Password=StrongP@ssw0rd123
RemotePath=/dbvault_backups/
Secure=true
Passive=true

Common FTP problems include firewalls blocking dynamic ports in passive mode, credential mismatches, or insufficient disk quota on the remote server. Use secured mode unless your FTP server lacks TLS support.

#Common Pitfalls

  • Path resolution failures on network shares that are not persistently mapped for the service account.
  • Unreliable WAN links causing FTP transfers to timeout during large database backups.
  • Storing backups without testing restore procedures, leaving you with unrecoverable archives.
  • Using unencrypted FTP over public networks, exposing sensitive database contents.

#Future Storage Support

Database Vault is constantly being updated to support additional storage methods. Check the release notes after each update to see newly enabled options and any configuration changes required for existing jobs.

Combine local speed with FTP offsite copies to follow a 3-2-1 backup strategy. Validate every backup location with a test restore before relying on it in production. Consult the Database Vault job configuration guide for exact UI steps.