Comments
Sort by recent activity
In a clustered environment, doesn't all the nodes in a cluster usually point to the same SQL Server instance? / comments
In a clustered environment, doesn't all the nodes in a cluster usually point to the same SQL Server instance?
Are you also able to restore the database via the cmd line?
Does the password for the sa user contain any accented or non-standard characters?
Can you also start Profiler, and try to perform the restore using the Restore Wizard again? When you hit the error, what are the last few entries in Profiler? / comments
Are you also able to restore the database via the cmd line?
Does the password for the sa user contain any accented or non-standard characters?
Can you also start Profiler, and try to perform the re...
Could you pls try using the command line interface to read the file list? E.g.
sqlbackupc -sql "RESTORE FILELISTONLY FROM DISK = '<your sqb file>'" -U sa -P <password> / comments
Could you pls try using the command line interface to read the file list? E.g.
sqlbackupc -sql "RESTORE FILELISTONLY FROM DISK = '<your sqb file>'" -U sa -P <password>
I assume you are using the Restore Wizard in the GUI. At which stage of the restore steps do you encounter the error? Thanks. / comments
I assume you are using the Restore Wizard in the GUI. At which stage of the restore steps do you encounter the error? Thanks.
Let's try keeping it simple first. If you can, stop and restart the SQL Server service. Use the command line interface to perform a backup e.g.
sqlbackupc -sql "BACKUP DATABASE logtest TO DISK = '<some location>'
If using SQL Server authentication, supply also the -U and -P parameters and values.
Now, restore the database using the command line interface again e.g.
sqlbackupc -sql "RESTORE DATABASE logtest FROM DISK = '<some location>'
Does this work? / comments
Let's try keeping it simple first. If you can, stop and restart the SQL Server service. Use the command line interface to perform a backup e.g.
sqlbackupc -sql "BACKUP DATABASE logtest TO DISK = ...
COPYTO copies the backup file to x locations after it has been generated. Thus, only one backup file is generated.
MIRRORFILE creates multiple copies of the backup file as it is generated. As long as one location is still writable, the backup will proceed. / comments
COPYTO copies the backup file to x locations after it has been generated. Thus, only one backup file is generated.
MIRRORFILE creates multiple copies of the backup file as it is generated. As lon...
The problem has been resolved, and was due to a permissions error on the SQL Server service startup account to write to the C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Data folder. / comments
The problem has been resolved, and was due to a permissions error on the SQL Server service startup account to write to the C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\...
The activity log is stored in the C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Data folder. It should exist on your workstation.
A possibility is that the SQL Server service startup account does not have 'write' rights to this folder.
Try this in Query Analyzer:
master..xp_cmdshell 'dir c: > "C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Data\dir.txt"' / comments
The activity log is stored in the C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Data folder. It should exist on your workstation.
A possibility is that the SQL Server se...
The log files are usually found in C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log, assuming C:\ is your system drive.
Can you try running a simple backup process from Query Analyzer using the NOWRITE option e.g.
sqlbackup '-sql "BACKUP DATABASE pubs TO DISK = [c:\pubs.sqb] WITH INIT, NOWRITE"'
This will cause SQL Backup to skip updating the local activity history table, assuming that is the problem. / comments
The log files are usually found in C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log, assuming C:\ is your system drive.
Can you try running a simple backup process from ...
Internally, the extended stored procedure calls the command line to perform it's work. Thus, it's strange that it works from the command line but not from the extended sp.
When using the command line and the process completes, are you returned to the prompt immediately, or does it pause, waiting for you to hit a key before it returns to the prompt? / comments
Internally, the extended stored procedure calls the command line to perform it's work. Thus, it's strange that it works from the command line but not from the extended sp.
When using the command l...