Comments
Sort by recent activity
Hi-
Yes, our server (Serv-U) allows you to see the name an in-progress file via "LS", but returns a 450 error when you try to download it. I'm not sure why they don't make the filename totally invisible, but whatever.
On the client side, we download files to a temporary directory then do an atomic "Move" operation when it's complete so that you don't have the same problem on the backup machine.
So far it seems to be working fine---we download the new TX logs every hour, then restore them via a scheduled task on the backup machine overnight. We can deploy this to as many backup machines as we want this way.
Cheers!
-Mike
petey wrote:
I'm interested to know how you avoided downloading files that are in the process of being copied. Was this a feature of the FTP server you were using?
Thanks.
/ comments
Hi-
Yes, our server (Serv-U) allows you to see the name an in-progress file via "LS", but returns a 450 error when you try to download it. I'm not sure why they don't make the filename totally inv...
Hi-
We actually just finished writing a little FTP utility which downloads everything from a directory (via a filename pattern) and deletes it. The strategy we're just about to deploy is this:
1) configure the TX log backup routine so that it creates a copy in a separate directory on the main MSSQL machine.
2) keep the FTP synchronization service running on the remote backup machine to download from that directory to a particular local directory
3) run sqlbackup from the task scheduler to restore everything from that local directory, then move it elsewhere (or delete it).
Using FTP is not ideal, but it should be ok for a simple setup like ours.
Thanks!
-Mike
petey wrote:
Try the FTPTool utility, downloadable here.
## This is not an official Red Gate tool, just something I threw together. No warranties are expressed or implied here.
FTPTool copies files from a source folder to a ftp site. It stores names of files it has already copied to a file, and skips copying those files again when it next runs. It's a companion tool to CopyTool, described here. Note that it can only 'push' files to a ftp site, and cannot 'pull' files.
Feedback welcomed.
/ comments
Hi-
We actually just finished writing a little FTP utility which downloads everything from a directory (via a filename pattern) and deletes it. The strategy we're just about to deploy is this:
1)...
Hi Brian,
Thanks for the pointer. I've just started working on selecting the files in the file transfer script, but if that doesn't work I'll have a closer look at doing it from the SQL side. I suspect that managing this outside SQL will be easier, because there are some issues to address such as avoiding applying partially-downloaded files.
Thanks!
-Mike
Brian Donahue wrote:
Hi Mike,
It may work to make some sort of script that queries MSDB for the latest full backup checkpoint LSN and then examine the header of each backup file to find the next one to restore. I'm not 100% sure that this would work, but hopefully it will give you an idea of where to start!
/* get the database checkpoint LSN */
SELECT TOP 1 checkpoint_lsn FROM msdb.dbo.backupset
WHERE database_name = 'MyDb'
AND TYPE='D'
ORDER BY backup_finish_date DESC
/* Check the SQL Backup file header LSN */
execute master..sqlbackup '-sql "RESTORE SQBHEADERONLY FROM DISK=''d:\sql2005\mssql.1\mssql\backup\Log_MyDb.sqb'' WITH PASSWORD=''x''"'
/ comments
Hi Brian,
Thanks for the pointer. I've just started working on selecting the files in the file transfer script, but if that doesn't work I'll have a closer look at doing it from the SQL side. I s...
Hi-
This would be a very cool feature---it would mean you could create multiple offsite backups without any scripting just by having client machines access the transaction logs. Once they're all accessible in a particular directory (either locally or across a network), it'd just be a matter of the clients pointing to that directory with the sqlbackup "restore" function.
The only issue requiring scripting (apart from transferring the files) is figuring out which TX logs haven't been applied yet.
Cheers!
-Mike
petey wrote:
No, SQL Backup does not yet have a function to selectively restore only transaction log files that have not been applied.
/ comments
Hi-
This would be a very cool feature---it would mean you could create multiple offsite backups without any scripting just by having client machines access the transaction logs. Once they're all a...
Hi-
I noticed that the 5.3 version of SqlBackup has a documentation bug---on the "The RESTORE Command" page in the Windows help file, the MAILTO_ONERROR and MAILTO_ONERRORONLY have identical descriptions.
Thanks,
-Mike
petey wrote:
That is a bug, and will be fixed in the next release. Thank you for taking the time to report this.
MAILTO_ONERROR should send email notification on all warnings and errors. Version 5.3 introduced a new keyword, MAILTO_ONERRORONLY, that sends email notification only when errors are encountered.
/ comments
Hi-
I noticed that the 5.3 version of SqlBackup has a documentation bug---on the "The RESTORE Command" page in the Windows help file, the MAILTO_ONERROR and MAILTO_ONERRORONLY have identical descri...
Hi-
Ok, running SQBServerSetup.exe manually seems to install the proper version of the DLL. I was able to get it running after this.
Thanks!
-Mike / comments
Hi-
Ok, running SQBServerSetup.exe manually seems to install the proper version of the DLL. I was able to get it running after this.
Thanks!
-Mike
Hi-
I'm also encountering this problem---is there any workaround for it until 5.2 is released? Or any technique for avoiding it? It's been "Checking backup files...." for 30 minutes on a backup that has level-1 compression, created with a single thread.
Thanks,
-Mike
Dan J Archer wrote:
Hi all,
Another update: we've isolated the problem to use of the RESTORE FILELISTONLY command with backups created with multiple threads. SQL Backup 5.0 and 5.1 end up verifying the entire file during this process, which naturally takes some time if the file is large. The UI uses this command in order to work out which files each backup file contains.
We've got a fix in progress for this at the moment. This should make it into the 5.2 release of SQL Backup. I don't have an exact timetable for that release as yet, but if anyone has an urgent need for a fix for this, please private message me and I'll see what I can do [image]
All the best,
Dan
/ comments
Hi-
I'm also encountering this problem---is there any workaround for it until 5.2 is released? Or any technique for avoiding it? It's been "Checking backup files...." for 30 minutes on a backup t...
Ok, apparently this is a GUI issue---the "Checking backup files..." screen never goes away, but the "Next >" button does indeed become available. (This might be an issue with logging in via Remote Desktop?)
-Mike
mikebridge wrote:
Hi-
I'm also encountering this problem---is there any workaround for it until 5.2 is released? Or any technique for avoiding it? It's been "Checking backup files...." for 30 minutes on a backup that has level-1 compression, created with a single thread.
Thanks,
-Mike
/ comments
Ok, apparently this is a GUI issue---the "Checking backup files..." screen never goes away, but the "Next >" button does indeed become available. (This might be an issue with logging in via Remote...
Yeah, I've been bitten with the stale cache bug a few times now and it's pretty frustrating. The AP-<tab>+autocomplete would save me *so* much time, but redoing lost changes offsets any time savings I might have had.
Refreshing the cache takes a fraction of a second on my machine---I wouldn't notice if it did it automatically when an ALTER PROCEDURE command is executed.
Are there any plans to make any changes to this caching issue?
Thanks!
-Mike
CodantiM wrote:
Maybe the Alter object function in SQL Prompt should pull directly from the DB and not the cache, what do you think Red Gate is that possible?
Maybe an option to have the cache auto-refresh just before pulling the object? (That could be problematic since the refresh only refreshes the current DB, and you may be pulling an object from a different DB.)
/ comments
Yeah, I've been bitten with the stale cache bug a few times now and it's pretty frustrating. The AP-<tab>+autocomplete would save me *so* much time, but redoing lost changes offsets any time savin...
Wow, perfect, thanks!
-Mike
CodantiM wrote:
You can do something similar with SQL Prompt. See this older thread about the same thing: http://www.red-gate.com/MessageBoard/vi ... php?t=9493
/ comments
Wow, perfect, thanks!
-Mike
CodantiM wrote:
You can do something similar with SQL Prompt. See this older thread about the same thing:http://www.red-gate.com/MessageBoard/vi ... php?t=9493