Comments
Sort by recent activity
Thanks for your forum post.
Are you able to confirm if you have followed the steps detailed in the url below: http://www.red-gate.com/supportcenter/C ... Repository
Thanks for your patience and feedback in this matter. / comments
Thanks for your forum post.
Are you able to confirm if you have followed the steps detailed in the url below:http://www.red-gate.com/supportcenter/C ... Repository
Thanks for your patience and feed...
I hope your day is off to a good start? I am sending you an update in regards to this issue. Thank you very much for your feedback in regards to this issue.
I have raised a JIRA issue for the enhancement requestion you have reported and have organised for you to be notified when this is fixed. This issue is now being triaged by development for a future sprint. The JIRA number (SE-681) that will ensure you get an automatic update.
Thanks for your patience and feedback in this investigation, This is really appreciated. / comments
I hope your day is off to a good start? I am sending you an update in regards to this issue. Thank you very much for your feedback in regards to this issue.
I have raised a JIRA issue for the enhan...
Thanks for your forum post. This does not need to be raised in a new post.
The TSQL script that you have generated using the wizard is the correct one and should work fine for that specific backup. To dynamically generate the TSQL depending on the backup will require using variables to substitute the relevant values. Unfortunately we haven't written any TSQL that can do this at the moment.
Please note this will need to be customised in your environment and depending on the number of threads, database structure the 'move syntax' will change as well.
Thanks for your patience and feedback in this matter. / comments
Thanks for your forum post. This does not need to be raised in a new post.
The TSQL script that you have generated using the wizard is the correct one and should work fine for that specific backup....
Thanks for the forum post.
The virtual restore extensions can only be used with a native TSQL Restore syntax. You are currently using the SQL Backup restore syntax. That's why the script is not work for SVR. The extensions are being ignored by hyperbac when you try any other syntax. Within current syntax SQL Backup is just doing a normal restore. / comments
Thanks for the forum post.
The virtual restore extensions can only be used with a native TSQL Restore syntax. You are currently using the SQL Backup restore syntax. That's why the script is not wor...
Your question has been passed to Product Support and has raised a support call. Please send your logs to support@red-gate.com with the following in the subject line:
F0066891 - (Forum) Databases saying offline in Windows 2008 cluster
When SQL Monitor indicates 'Offline', it often means that SQL Monitor has lost contact with the host machine and/or sql server instance.
Please check that you have entered the machine name and password correctly. Then refer to the 'Show Log' page and check that all the connections are working. If you encounter any difficulty then please send me screenshots of the 'Show Log' page and the SQL Monitor log files, which are detailed in this document: http://www.red-gate.com/supportcenter/C ... %20Monitor
Also let me know if restarting the base monitor helps fix the connection issue?
Thanks for your patience and feedback in this matter. / comments
Your question has been passed to Product Support and has raised a support call. Please send your logs to support@red-gate.com with the following in the subject line:
F0066891 - (Forum) Databases sa...
This is being looked at by my colleague via our support system.
There is no scratch pad area where backup data is staged during a restore. The error message that you are getting is because SQL Server does a size check when it starts a restore. Because you don't have enough space on that drive you are being thrown an error. The space check is done on the destination location where the database files are going to be hosted, not on the location of the backup file (unless the database files and the backup file are on the same drive).
I note that your intent is to overwrite the previous copy of the database. In this case you can execute a restore command with the 'replace' option. This will just overwrite the previous database files.
Note that you will lose that previous copy of restore database when you execute this command.
Thanks for your patience and feedback in this matter. / comments
This is being looked at by my colleague via our support system.
There is no scratch pad area where backup data is staged during a restore. The error message that you are getting is because SQL Serv...
Dear Chris,
Just letting you know that this has created a new support case in our support system. I will be posting a response via the support case to your query.
Thanks for your patience and feedback in this matter. / comments
Dear Chris,
Just letting you know that this has created a new support case in our support system. I will be posting a response via the support case to your query.
Thanks for your patience and feedb...
Dear David,
This forum post has created a new support request in our support system. I have responded to this query via that support case.
Thanks for your patience and feedback in this matter.
Regards, / comments
Dear David,
This forum post has created a new support request in our support system. I have responded to this query via that support case.
Thanks for your patience and feedback in this matter.
Rega...
-- Response from the customer:
Hi,
Sorry for not getting back to you. This case can be closed, we tracked
the issue down to our SAN.
Thanks, / comments
-- Response from the customer:
Hi,
Sorry for not getting back to you. This case can be closed, we tracked
the issue down to our SAN.
Thanks,
I am the support engineer that is investigating this issue you have raised. I am sorry you have encountered this error and apologise for the inconvenience caused.
Is it possible to let me know a few things about this system? I am after the following information:
1) Has SQL Backup restored this backup successfully before?
2) This problem seems to be related to the network connection on this system. The error message mentions a number of attempts by sql backup to try to keep the connection alive before giving up?
3) Are there any logs being created that correspond to this error in the SQL Backup logs directory other than the error message that you have attached?
4) Is it possible to have a quick look in the server's system log to see if there was any problems with the network connection?
This forum thread has opened a support request and I will continue to work with you via the support request after this email.
Thanks for your feedback in this matter. / comments
I am the support engineer that is investigating this issue you have raised. I am sorry you have encountered this error and apologise for the inconvenience caused.
Is it possible to let me know a fe...