Found a minor issue with SQLBackup 5.4.0.35
We run SQLBackup on a cluster running multiple instances of SQL Server.
I have used the following path in the SQLBackup log file directory
F:\SQLLogs\MEDPOL\<INSTANCE>\SQLBackup
This works ok with log files being created in the directories according to the SQL Server instance name ie
F:\SQLLogs\MEDPOL\INSTA\SQLBackup
F:\SQLLogs\MEDPOL\INSTB\SQLBackup
The issue is that with the path set with the <INSTANCE> tag in it that SQL Backup will not perform the delete operation.
If I change the path to not include the tag then the SQL Backup will delete the log files.
Looks as if SQL backup ignores the tag when performing deletes.
Only a minor issue but thought I would report it. Should I not use tags in the SQL backup log file directory.
We run SQLBackup on a cluster running multiple instances of SQL Server.
I have used the following path in the SQLBackup log file directory
F:\SQLLogs\MEDPOL\<INSTANCE>\SQLBackup
This works ok with log files being created in the directories according to the SQL Server instance name ie
F:\SQLLogs\MEDPOL\INSTA\SQLBackup
F:\SQLLogs\MEDPOL\INSTB\SQLBackup
The issue is that with the path set with the <INSTANCE> tag in it that SQL Backup will not perform the delete operation.
If I change the path to not include the tag then the SQL Backup will delete the log files.
Looks as if SQL backup ignores the tag when performing deletes.
Only a minor issue but thought I would report it. Should I not use tags in the SQL backup log file directory.