Comments
Sort by recent activity
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...
I am the support engineer that is investigating this issue you have posted. I am responding to this request via the support case that this forum thread has created. From initial investigation this might be related to hardware resourcing.
The best thing to confirm would be if the network connection is not a bottleneck. If possible also confirm if the destination location is not a disk that needs to be defragged?
The other possibility to consider is the long filenames at the destination. This might cause the issue as well.
One more thing that I can suggest is that you try the same command but point the destination as a UNC location that is on the same server. For eg put the location as \\servername\diskdrivelocation. This way the network redirector will be used but will point to the local destination. This will confirm that the network port is the bottleneck.
Thanks so much for your patience and feedback in this matter. / comments
I am the support engineer that is investigating this issue you have posted. I am responding to this request via the support case that this forum thread has created. From initial investigation this ...
Thanks for your feedback and the enhancement request. I have put this along side two more other customers who have requested similar features.
The other two scenarios that were requested are:
Allow saving of templates in Scheduled Backup wizard
Easy migration of templates between servers
I will put your request again in the triage queue and should have an update when this is looked at by product management. The jira number for your reference is SB-3470.
I should be in a position to notify you when this is triaged and updated.
Thanks for your feedback in this matter. / comments
Thanks for your feedback and the enhancement request. I have put this along side two more other customers who have requested similar features.
The other two scenarios that were requested are:
Allow...
I am the support engineer that is investigating this issue you have raised. Thank you for the suggestion and the feature request. I would like to discuss this with you in a little more detail and offer some preliminary advice if possible.
The compression analyser works on the data types and then depending on the values it parses it makes an estimate of the compression it can achieve. This information is normally very accurate as the data type and size information rarely changes very quickly.
In regards to calculating time and CPU the analyser would be a little bit off the mark as there are other variables like activity on the server, type of the disk subsystem etc that make a big difference to the outcome.
For eg. The location could be network or local and this in itself will make a difference to the time calculations. Hence to err on the side of only providing realistic information we currently provide only information about how much we can compress the data.
If you feel really strongly about this feature I can create a change request and triage this with product management if that suits?
Thanks for taking the time to put this feature request in. This is a good thing either ways as other SQL Backup users will be reviewing this information and adding their thoughts as well.
Thanks for your feedback in this matter. / comments
I am the support engineer that is investigating this issue you have raised. Thank you for the suggestion and the feature request. I would like to discuss this with you in a little more detail and o...