Comments
Sort by recent activity
Hi,
I'm sorry that you're experiencing all this. The second exception I presume is of the form that does terminate the application and instead appears in the error explanation popup if you click the red X? If this is the case, then an unexpected communication break between SQB and SQL Server occurred.
Since the other issue affects you more prominently, we should try to understand that first. Process Explorer is a Microsoft Sysinternals tool that gives you an overview of the processes running on your computer. It acts as a sort of extreme version Task Manager and the feature I find most useful is its handle search. It does not require installation to run (it comes as just an .exe pretty much) and the handle search can be accessed by pressed CTRL-F. This pops up a search dialogue where you can enter a filename (such as localDataCache.dat, 1.dat etc.). In the results panel you'll see the full list of processes that currently have that file open, including internal windows processes like svchost.exe. If there are any processes other than SQL Backup accessing the local data store, then this might explain the undesirable behaviour.
Since, even with a fresh install, the UI pulls history from the remote SQL Backup Agent it might also be worth checking the validity of those records. The easy way to do that would be to install the UI on another workstation and seeing if it can display the backup history as expected. If it cannot, then we know that the backup history of one or more of your servers is not in a state that SQL Backup can currently handle. The data.sdf (SQB Agent's datastore) might be corrupted or have confusing entries. In this case, you should delete this store and try again.
As for the unexpected grey entries, could you please provide a screenshot?
Regards, / comments
Hi,
I'm sorry that you're experiencing all this. The second exception I presume is of the form that does terminate the application and instead appears in the error explanation popup if you click th...
I'm not sure if this is what you're experiencing, but if the local data cache is present but inaccessible (locks, permissions etc.) you'll experience symptoms such as you describe.
The first thing I'd do is have a look to see if anything is happening to those files via Process Explorer's handle search or a similar tool.
Regards, / comments
I'm not sure if this is what you're experiencing, but if the local data cache is present but inaccessible (locks, permissions etc.) you'll experience symptoms such as you describe.
The first thing ...
Hi Paul,
The backup jobs rely on the SQL Server Agent for scheduling. Is there anything to suggest that the jobs are starting then failing? The activity history will display failed attempts.
If the jobs aren't even starting, I would examine the Agent's configuration from SQL Server Management Studio and the event log to see if it has posted any errors relating to this.
Regards, / comments
Hi Paul,
The backup jobs rely on the SQL Server Agent for scheduling. Is there anything to suggest that the jobs are starting then failing? The activity history will display failed attempts.
If the...
Hi kunderwood,
You will need to manually create the value for BrowsingUserList. Special values like this are not generated automatically by SQL Backup.
Kind regards, / comments
Hi kunderwood,
You will need to manually create the value for BrowsingUserList. Special values like this are not generated automatically by SQL Backup.
Kind regards,
Hi Steve,
When you use the restore wizard, step 1 gives you a drop down list of all the SQL Server instances you've registered with the application. If the server you wish to restore to is not on this list, you must first register it (File > Add SQL Server). Remember to change "Select from backup history" to "Browse for backups to restore" in step 1 or the wizard will only show backups from the selected test server.
Hope this helps, / comments
Hi Steve,
When you use the restore wizard, step 1 gives you a drop down list of all the SQL Server instances you've registered with the application. If the server you wish to restore to is not on t...
Hi RJ,
An example of a split backup (3 files) command is shown below:
[EXECUTE master..sqlbackup '-SQL "BACKUP DATABASE [test] TO DISK = ''E:\Backups\<AUTO>_1.sqb'', DISK = ''E:\Backups\<AUTO>_2.sqb'', DISK = ''E:\Backups\<AUTO>_3.sqb'' WITH DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4"'
When you choose this option, we open as many virtual device interfaces (VDI) to SQL Server as there are files requested by the user. Each of the datastreams that SQL Server provides to SQL Backup is identical to what you'd find in the native backups files if you gave more than one TO DISK argument in a native backup.
How does the software determine the size of each file or how many files to split the backup into?
SQL Server performs the task of how to split the data and then SQL Backup performs encryption/compression on each of the streams independently. The number of files is chosen by the user just by specifying more TO DISK arguments.
Is there a way to set a max size for each file?
As the files are written in parallel, you can't have SQL Backup write the files sequentially up to a given max file size.
Hope this answers your questions, / comments
Hi RJ,
An example of a split backup (3 files) command is shown below:
[EXECUTE master..sqlbackup '-SQL "BACKUP DATABASE [test] TO DISK = ''E:\Backups\<AUTO>_1.sqb'', DISK = ''E:\B...
Hi Redeye,
I'm sorry to hear that you're having difficulty. Can you please check the system event log to see what error message / error numbers are being reported by the service control manager when SQL Backup fails to start?
Regards, / comments
Hi Redeye,
I'm sorry to hear that you're having difficulty. Can you please check the system event log to see what error message / error numbers are being reported by the service control manager whe...
Port 1434 is the Microsoft SQL Monitor port (UDP). Perhaps opening this one may help.
Regards, / comments
Port 1434 is the Microsoft SQL Monitor port (UDP). Perhaps opening this one may help.
Regards,
Hi dharmesh1 ,
Port 1433 should be all it needs if connecting via TCP.
Can you telnet port 1433 from the machine running the UI whilst your firewall is operational?
Regards, / comments
Hi dharmesh1 ,
Port 1433 should be all it needs if connecting via TCP.
Can you telnet port 1433 from the machine running the UI whilst your firewall is operational?
Regards,
Hi jchertudi,
SQL Backup supports Windows 7 and 2008 R2. Can you please provide some details of your setup? For example, what language / localisation are you using?
Have you noticed anything unusual with the installed fonts on Windows? For example, will Arial render in bold in other applications?
Regards, / comments
Hi jchertudi,
SQL Backup supports Windows 7 and 2008 R2. Can you please provide some details of your setup? For example, what language / localisation are you using?
Have you noticed anything unusua...