Overview
Parameter: BACKUPPATH
Category: Custom
Default value: \\server\freigabe\
Product: eTASK.Other (Custom)
What does this parameter do?
BACKUPPATH defines the network path where database backups created via the portal control are stored. The system automatically saves backup files there with a timestamp in the format Datenbankname_JJJJMMDDhhmm.bak.
What is this parameter used for?
The parameter is used when:
Administrators want to create manual database backups from within the portal
Quick ad hoc backups need to be created before major changes
Backup files must be stored in a network path accessible to the application server
Additional backups need to be created in parallel with automated backup schedules
Technical Details
Format: UNC network path (Universal Naming Convention)
Default value: \\server\freigabe\
Valid values:
UNC path:
\\servername\freigabename\ordner\Example:
\\backup-server\sql-backups\portal\Local path (not recommended):
C:\Backups\
Important notes:
The path must be accessible from the application server for the "Network Service" user
The backup function uses the "copy only" option (COPY_ONLY) and does not interfere with existing backup schedules
Backups are created with a timestamp:
Datenbankname_JJJJMMDDhhmm.bakThe backup timeout is set to 10 minutes
When should you change this value?
Change the value (enter a new path) if:
You set up a dedicated backup server or a central backup share
The current storage location does not have sufficient capacity for backups
You want to store backups in a different network environment
Permission issues arise with the current path
Leave the value at the default if:
The placeholder path has not yet been replaced by an actual backup path
You are not using the portal backup feature
You work exclusively with automated SQL Server maintenance plans
Important Notes
Network permissions required
The SQL Server service (often running under "Network Service" or a specific service account) must have write permissions to the specified network path. Without this permission, backup attempts will fail.Use UNC
paths Always use UNC paths (\\server\freigabe\) instead of drive letters, as network drives may not be available to system services.Sufficient storage space
Ensure that the destination location has enough free space for multiple backups. A typical Portal backup can be several gigabytes in size.No conflict with maintenance plans
The Portal backup feature uses COPY_ONLY, so it does not interrupt the backup chain of SQL Server maintenance plans. Full and differential backups are not affected.Path must exist
The network path and all subfolders must already exist. The system does not automatically create missing directories.
Security
Does changing this parameter affect security?
Yes, configuring this parameter has significant security implications, as database backups contain sensitive corporate data.
Positive aspects:
Enables secure storage of backups outside the production system
Supports centralized backup strategies with dedicated backup servers
The COPY_ONLY option prevents disruptions to existing backup concepts
Note:
Backup files contain the entire database with all sensitive information
The network path must be protected against unauthorized access
Unencrypted backups can lead to data leaks if the backup server is compromised
Incorrect permissions can cause backups to fail or be read by unauthorized users
Recommendation: Use a dedicated, well-secured backup server with restricted access. Implement encryption for backup files (Transparent Data Encryption or backup encryption in SQL Server). Regularly monitor who has access to the backup path, and implement retention policies to automatically delete old backups.
Practical example
Initial situation: A company is using the portal in production and has a dedicated backup server with the share \\backup-srv01\sql-backups\. The IT department wants to create a manual backup before a major portal update without disrupting the automatic nightly backup schedule.
Configuration: 1. Administrator opens the system configuration in the portal 2. Locates the BACKUPPATH parameter 3. Changes the value from \\server\freigabe\ to \\backup-srv01\sql-backups\portal\ 4. Saves the change 5. Ensures that the SQL Server service has write permissions to \\backup-srv01\sql-backups\portal\
After the change:
The administrator navigates to Portal Control → Backup Function
Click on "Create Backup"
The system creates a file such as
eTASK_202511261430.bakbelow\\backup-srv01\sql-backups\portal\The backup file contains a complete copy of the database as of the current time
The automatic nightly backup schedule continues as usual (COPY_ONLY backup)
Result: The IT department has a current backup prior to the update and can quickly revert to the previous version if problems arise. The regular backup schedule has not been disrupted, and all backups are stored centrally on the backup server.
Recommended setting
For standard installations:\\backup-server\sql-backups\portalname\(customer-specific UNC path)
Reason:
Centralized backup storage on a dedicated server
Separation of production and backup data
Simpler management and monitoring of backups
Better disaster recovery capabilities
Exceptions (small installations):
For smaller installations without a dedicated backup server, a local path on a different drive can be used:
D:\SQLBackups\Portal\Ensure that local paths are also regularly backed up externally
Never store them on the same drive as the database files
note43450b5f-b93a-4dbd-a901-3e4c31a1cad7
Tip: After configuration, test the backup function manually once and verify that the file was created in the correct location. Implement automatic cleanup of old backup files to free up storage space. Document the backup path in your IT documentation for disaster recovery.
Tip: After configuration, test the backup function manually once and verify that the file was created in the correct location. Implement an automatic cleanup of old backup files to free up storage space. Document the backup path in your IT documentation for disaster recovery.