Activity overview
Latest activity by AlanMullock
I'd come to the same conclusion about the write restriction, but partially set it aside due to the fact that the log files where still being created under the same folder structure.
Anyhow, manually creating the .lic file worked and after a service restart the installation is now showing up as registered, so that's good enough for me.
Once again, thanks for your assistance Pete.
Alan. / comments
I'd come to the same conclusion about the write restriction, but partially set it aside due to the fact that the log files where still being created under the same folder structure.
Anyhow, manuall...
Created the licenses folder manually as suggested.
The error message changed to "Cannot create file" "Access is denied".
SQLBackup is configured to start as Local System and I am logged on as a Local Adminsitrator.
(Just to check, I started the service with my account, still received the error message).
I guess I'm missing a little something any suggestions as to what?
Thanks,
Alan. / comments
Created the licenses folder manually as suggested.
The error message changed to "Cannot create file" "Access is denied".
SQLBackup is configured to start as Local System and I am logged on as a Loc...
SQLBackup 4.1 License Activation Error
When trying to active my installed copy of SQLBackup, i have entered the activation code entered in the email and clicked on next to install the licence.
However i receive the message back:
Cannot ...
Yes, in Regime1, each backup is a seperate SQLAgent job, all of which have the same start time. Which means that we have 8 backups starting/running concurrently.
What is interesting about the initial failures is that they where presented by the Transaction Log backups. To simplify the pattern, it went something along these lines:
Hour 1 - All 4 concurrent transaction log tasks succeed.
Hour 2 - 1 Transaction Log backups succeeds - 3 fail with the error message given.
Hour 3 (onwards) - All transaction logs and all future backups fail.
Thanks,
Alan. / comments
Yes, in Regime1, each backup is a seperate SQLAgent job, all of which have the same start time. Which means that we have 8 backups starting/running concurrently.
What is interesting about the initi...
To give some more details on this backup implementation:
Frequency
Server has 13 databases. 2 Different backup regimes are used depending upon whether DB is in simple recovery mode or Full.
Regime 1 (Simple) - Daily Full Backup - Used on 8 databases
Regime 2 (Full) - Full Backup once/week - Differential once/day - Transaction Log Once/Hour - Used on 5 databases.
Jobs had been running successfully from 16/3 to 21/3 before starting to fail again. So therefore 5days worth of backups had run around 670 backup events had occurred in between failures.
All Backups occur to Local disk.
Using the above schedule, the most backups that are running simulatenousely are 8.
SQL Server is SQL2000 running on 32bit Windows 2000.
Ran DBCC xp_sqlbackup(FREE) for 15 mins without it completing.
Reboot of server (for unrelated reason) has enabled backups to commence running again. / comments
To give some more details on this backup implementation:
Frequency
Server has 13 databases. 2 Different backup regimes are used depending upon whether DB is in simple recovery mode or Full.
Regime...
SQLBackup 4 errors after a few days of running
I've recently upgraded one of my servers from SQLBackup v3 to SQLBackup v4.
After installation, I've configured a number of SQLServer scheduled tasks to back up my databases using calls to sqlbacku...