Comments
Sort by recent activity
thank you... / comments
thank you...
I thought that would be the issue.. Thanks for your response / comments
I thought that would be the issue.. Thanks for your response
There has been nothing written to that log since the upgrade to SQL 2005. I usually run the backup from a command line and that is where I'm getting the error. If I try to run in in GUI it just continues to run and no file is created.
This is an example of the script I usually run
cd \Program Files\Red Gate\SQL Backup\(LOCAL)
SQLBackupC -SQL "BACKUP DATABASE [DATABASE_NAME] TO DISK = 'E:\DIRECTORY_NAME\DATABASE_NAME_zzz01.sqb', DISK = 'E:\DIRECTORY_NAME\DATABASE_NAME_zzz02.sqb',DISK = 'E:\DIRECTORY_NAME\DATABASE_NAME_zzz03.sqb',DISK = 'E:\DIRECTORY_NAME\DATABASE_NAME_zzz04.sqb' WITH COMPRESSION = 3, KEYSIZE = 256, PASSWORD = 'PASSWORD', VERIFY" / comments
There has been nothing written to that log since the upgrade to SQL 2005. I usually run the backup from a command line and that is where I'm getting the error. If I try to run in in GUI it just c...
Yes that is the case. What's the work around for that??? / comments
Yes that is the case. What's the work around for that???
I was afraid you were going to say that. I think we may just have to bite the bullet and upgrade.
Any issues restoring redgate backups from 2000 to 2005? / comments
I was afraid you were going to say that. I think we may just have to bite the bullet and upgrade.
Any issues restoring redgate backups from 2000 to 2005?
I can't really do that since the data does not reside on our system yet. We depend on receiving data from our customer as a red gate backup. We then turn around and restore the data to our system. However, this is a new set of data and we cannot restore the redgate backup. When I try to run the restore via command line I receive the following error.
SQL Backup log file
11/1/2006 9:53:09 AM: Red Gate SQL Backup 4.5.0.704, (c) Red Gate Software Ltd 2004 - 2006
11/1/2006 9:53:09 AM:
11/1/2006 9:53:09 AM: Restoring DBNAME (database) from:
C:\backup\zzz\DBNAME01.sqb
C:\backup\zzz\DBNAME02.sqb
C:\backup\zzz\DBNAME03.sqb
C:\backup\zzz\DBNAME04.sqb
11/1/2006 9:53:09 AM: RESTORE DATABASE [DBNAME] FROM DISK = 'C:\backup\zzz\DBNAME01.sqb', DISK = 'C:\backup\zzz\DBNAME02.sqb', DISK = 'C:\backup\zzz\DBNAME03.sqb', DISK = 'C:\backup\zzz\DBNAME04.sqb' WITH RECOVERY, MOVE 'Software_Data' TO 'C:\13Software\DBNAME.MDF', MOVE 'Software_Log' TO 'C:\Software\DBNAME_log.LDF', REPLACE', PASSWORD = 'XXXXXXXXXX'
11/1/2006 9:53:09 AM: Server: Msg 3013
RESTORE DATABASE is terminating abnormally.
11/1/2006 9:53:09 AM: Server: Msg 3205
Too many backup devices specified for backup or restore; only 64 are allowed. / comments
I can't really do that since the data does not reside on our system yet. We depend on receiving data from our customer as a red gate backup. We then turn around and restore the data to our system...
We've already considered points 2, 3 & 4. I'll look at the other 2 options to see if they provide a working solution for us.
Thanks / comments
We've already considered points 2, 3 & 4. I'll look at the other 2 options to see if they provide a working solution for us.
Thanks
Sorry for the delay in my post.
The situation that we're running into is not the fact that we're copying data from machine A to machine B within our network. The problem occurs when we receive a backup of our customer's data to host on our website. The encrypted backups are sent to us across the internet via SSH. When we recieve the data the file size is the same but the checksum for one of the files is off. SQL Backup does not recognize this and starts restoring the data but never finishes and leaves the database in the "Loading" state. This problem is getting worse as we bring more customers on. Is there some way we can escalate this issue that we are running into, because I can only see this issue getting worse as we convert more of our customers over to our new data structure. / comments
Sorry for the delay in my post.
The situation that we're running into is not the fact that we're copying data from machine A to machine B within our network. The problem occurs when we receive a b...
We're actually breaking the backup into 4 files via command line, but they are the same size. Even if I try to restore via the GUI interface it is telling me that I have valid files. However, here's what I've generated from the md5 generator.
MD5: F63F443902C3C2FAAA4FB2A0BDA7A370 > DATA01.sqb
MD5: A60DF2B22A5D3BE79AF329B3355355C8 > DATA02.sqb
MD5: BD779D8C2C5749E20163A28504659CAF > DATA03.sqb
MD5: 48BAECB601A51064025C910F4069B0EC > DATA04.sqb / comments
We're actually breaking the backup into 4 files via command line, but they are the same size. Even if I try to restore via the GUI interface it is telling me that I have valid files. However, her...
Yes, the md5 values are different. I'm guessing that something is getting messed up during the file transfer process. I'm not too sure that there is anything that can be done about that. / comments
Yes, the md5 values are different. I'm guessing that something is getting messed up during the file transfer process. I'm not too sure that there is anything that can be done about that.