Comments
Sort by recent activity
I'm sorry if you missunderstood. I didn't do anything. I didn't set a STOPAT command. The restore just stopped functioning today. I didn't touch anything. It has been working fine for 2-3 months now.
Just wondering if you all had any ideas on why it would just stop functioning. / comments
I'm sorry if you missunderstood. I didn't do anything. I didn't set a STOPAT command. The restore just stopped functioning today. I didn't touch anything. It has been working fine for 2-3 months no...
I figured it out. You can cancel. Thanks. / comments
I figured it out. You can cancel. Thanks.
Thank you very much. I was able to view the Application Data folder with the instructions that you provided. [image]
I'm not sure if I should be applying the same steps that you recommended for the previous person. Here is my exact problem. Three of the databases are receiving this same error when trying to do a restore from log shipping. Each of the actual log names are different for each of the databases.
It is says SQL Error 4326: The log in this backup set terminates at '' which is too early to apply to the database. A more recent log backup that includes '' can be restored.
Do you know what should be done to eliminate this problem? / comments
Thank you very much. I was able to view the Application Data folder with the instructions that you provided.
I'm not sure if I should be applying the same steps that you recommended for the previo...
Looks like I am having the same problem. For starters, I don't have an application data folder under the all users folder. Where else can I find this data?
I'm really confused here because I don't understand why some of the restores will work and some won't. All of my log shipping is configured the same way.
By the way, I'm using SQL Back up v5. I did a search on the area and this post appeared. / comments
Looks like I am having the same problem. For starters, I don't have an application data folder under the all users folder. Where else can I find this data?
I'm really confused here because I don't ...
Greetings:
Yes, both servers have the [image] \MSSQL Value under the registry.
I am still waiting for a response on this problem.
Your help is greatly appreciated. / comments
Greetings:
Yes, both servers have the \MSSQL Value under the registry.
I am still waiting for a response on this problem.
Your help is greatly appreciated.
I am still struggling with getting the log shipping to work and I am running out of time. [image] One thing that I noticed today is that I can do log shipping and over write a DB that was created by SQL Backup, but it still won't work when trying to over write a DB that we created. (Once while setting up the log shipping, I told SQL Backup to create a new DB on the destination server and it worked.) I have looked at the properties and permissions on both databases and they are the same.
Could you give me some ideas as to what may be the cause since I have narrowed it down to the problem being with a database that I already had :?:
I appreciate your time with helping me with this [image] / comments
I am still struggling with getting the log shipping to work and I am running out of time. One thing that I noticed today is that I can do log shipping and over write a DB that was created by SQL ...
Thanks so much for your help. I would have never thought to turn on the SQL Profiler.
Okay, this time it gave me a more descriptive error. It could not find the instance for the destination DB. From the profiler, I see that it is looking for an old server name that no longer exists. The server died on us. We were using an older version of SQL Backup to transmit data to that server. This now is very puzzling because I don't know where it is getting the old server name from.
Perhaps the program is confused [image] I have been communicating with these 2 new servers and surely the name is really changed. Here is the error that I am getting now:SQL Backup process ended.
Restoring database to destination server - Failed
This operation failed with errors.
Restoring DBName (database) from:
\\SERVERNAME\redGateBackUpsForLogShipping\SEED_DBName_20070503121132.sqb
VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had
elapsed.)
Also check that the database is not currently in use.
SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3101: Exclusive access could not be obtained because the database is in use.
SQL Backup exit code: 1010
SQL error code: 3101 / comments
Thanks so much for your help. I would have never thought to turn on the SQL Profiler.
Okay, this time it gave me a more descriptive error. It could not find the instance for the destination DB. Fro...