SQL Backup 7.3 doesn't seem to have fixed the issue. ![Surprised]()
(
(
RE: Object Level Recovery error
↧
↧
RE: Hosted Storage
Hi Luis,
Thanks for your post. I'm not sure I have understood your question correctly. Do you mean, is it possible to overwrite a backup in a SQL Backup Pro Hosted Storage account by uploading another backup with the same name? The answer to this is no: the upload timestamp is appended to the backup file name, ensuring that each file in a hosted storage account has a unique file name. This means that you can upload multiple backups of the same name (eg "mybackup.sqb") to a Hosted Storage account without overwriting older files.
I hope that answers your question. Please let me know if you need more information.
Thanks,
Marianne
Thanks for your post. I'm not sure I have understood your question correctly. Do you mean, is it possible to overwrite a backup in a SQL Backup Pro Hosted Storage account by uploading another backup with the same name? The answer to this is no: the upload timestamp is appended to the backup file name, ensuring that each file in a hosted storage account has a unique file name. This means that you can upload multiple backups of the same name (eg "mybackup.sqb") to a Hosted Storage account without overwriting older files.
I hope that answers your question. Please let me know if you need more information.
Thanks,
Marianne
↧
SQL2012 AlwaysOn Availability Groups and SQLBackup
Hi,
We are just setting up two SQL2012 Servers that will be clustered to use Availability Groups. Because some of the databases are large we still want to use Red Gate SQLBackup as we use split backups and SQLBackup gives us uniquely named backup files that maintenance plans will not do. From what I understand if we create a database on one node or restore to it and then take a full backup it would automatically replicate to the other node(s) in the Availability Group. This could be a long process for large databases.
Is anybody using SQLBackup with SQL2012 Availability Groups that could give advice on best practices?
Thanks
Chris
We are just setting up two SQL2012 Servers that will be clustered to use Availability Groups. Because some of the databases are large we still want to use Red Gate SQLBackup as we use split backups and SQLBackup gives us uniquely named backup files that maintenance plans will not do. From what I understand if we create a database on one node or restore to it and then take a full backup it would automatically replicate to the other node(s) in the Availability Group. This could be a long process for large databases.
Is anybody using SQLBackup with SQL2012 Availability Groups that could give advice on best practices?
Thanks
Chris
↧
RE: Hosted Storage
Hi Marianne,
Thanks for you replay.
In that case my suggestion, in future releases, is to have override option.
In my opinion has the same name as backup or not, should be a user decition.
Thanks,
Luis
Thanks for you replay.
In that case my suggestion, in future releases, is to have override option.
In my opinion has the same name as backup or not, should be a user decition.
Thanks,
Luis
↧
Backup locally then network copy. Or ... network then Local?
Hi,
I am having some SAN issues (writes) that it is indirectly affecting my backup jobs.
Current jobs are set to backup locally 1st (dedicated backup LUN for that) and then copy to network path. That's the order when the backup job was created. So I played around a bit and inverted the order. I put the UNC path on what suppose to be the local path (1st field). Then I specified the local path for what suppose to be the UNC for the network location.
The results confused me even more and not what I was expecting.
I checked with SQL monitor the network utilization and found that 2nd option (backup to network and copy locally) has a spike in network utilization, 40% for a 10GB database, but it keeps using SAN communication for until the job ends.
Now, when backing up to local path 1st then copy to network drive via UNC, the network utilization remains at 20% for the whole duration of the job. However, it is not until the end, than the iSCSI or SAN is used, I guess that for the verify step?
So ... what it's more convenient ? Also, does SQL Backup 7 do backups in parallel when using local then network option? Based on the network graph, it looks that's what the job is doing.
By the way, tweaking the SAN is not an option and it's something that was discussed already. However, average output stays consistent at 44MB/sec when using SAN. When using network, output goes up to 60 or even more.
I am having some SAN issues (writes) that it is indirectly affecting my backup jobs.
Current jobs are set to backup locally 1st (dedicated backup LUN for that) and then copy to network path. That's the order when the backup job was created. So I played around a bit and inverted the order. I put the UNC path on what suppose to be the local path (1st field). Then I specified the local path for what suppose to be the UNC for the network location.
The results confused me even more and not what I was expecting.
I checked with SQL monitor the network utilization and found that 2nd option (backup to network and copy locally) has a spike in network utilization, 40% for a 10GB database, but it keeps using SAN communication for until the job ends.
Now, when backing up to local path 1st then copy to network drive via UNC, the network utilization remains at 20% for the whole duration of the job. However, it is not until the end, than the iSCSI or SAN is used, I guess that for the verify step?
So ... what it's more convenient ? Also, does SQL Backup 7 do backups in parallel when using local then network option? Based on the network graph, it looks that's what the job is doing.
By the way, tweaking the SAN is not an option and it's something that was discussed already. However, average output stays consistent at 44MB/sec when using SAN. When using network, output goes up to 60 or even more.
↧
↧
RE: UNC path and backups over the network
Sorry for my late reply.
I wanted to confirm I used UNC path. And appreciate the answer and follow up. Hope my thread helps someone in the future.
Thanks again!
I wanted to confirm I used UNC path. And appreciate the answer and follow up. Hope my thread helps someone in the future.
Thanks again!
↧
RE: LogShipping BizTalk databases
Is there any way I could use the native log backups that it generates with SQL Backup log shipping job running on the destination server?
Theoretically you could modify the jobs created by SQL Backup logshipping to use native SQL Server syntax for backup and restore.(I wouldn't recommend this.)
In other words, can the Restore command handle a native backup?
The SQL Backup restore command will not be able to handle the native backup file.
Is there a converter program from native to .sqb?
We do not have a converter for .bak to .sqb.
I would recommend that you use native log shipping in your case.
Here is an article I found that should point you in the right direction to get that set up.
http://www.mssqltips.com/sqlservertip/2301/step-by-step-sql-server-log-shipping/
Theoretically you could modify the jobs created by SQL Backup logshipping to use native SQL Server syntax for backup and restore.(I wouldn't recommend this.)
In other words, can the Restore command handle a native backup?
The SQL Backup restore command will not be able to handle the native backup file.
Is there a converter program from native to .sqb?
We do not have a converter for .bak to .sqb.
I would recommend that you use native log shipping in your case.
Here is an article I found that should point you in the right direction to get that set up.
http://www.mssqltips.com/sqlservertip/2301/step-by-step-sql-server-log-shipping/
↧
RE: SQL2012 AlwaysOn Availability Groups and SQLBackup
SQL Backup provides limited support for AlwaysOn Availability Groups introduced in SQL Server 2012. SQL Backup must be installed on each SQL Server instance separately; you cannot use the cluster installation. In the event of a failover, any scheduled jobs from the old primary server must be created manually on the new primary server.
↧
RE: SQL2012 AlwaysOn Availability Groups and SQLBackup
Thanks Manfred. As I read more about AlwaysOn Availability Groups I see that most things have to be duplicated.
Chris
Chris
↧
↧
RE: Backup locally then network copy. Or ... network then Local?
Hi,
Our recommendation is to backup to a local drive, and then "Copyto" to a network location. This is because the copyto option includes network resilience to retry the copy if there's a temporary loss of connection etc.
This sort of makes sense- you'd see an initial spike as the backup is done directly to the san (assuming you mean network communication to the san device?) and then the continual access following on until the end would be the file being copied.
This makes less sense to me- i'd assume the san usage to occur both with the initial backup and also the copy (assuming both the "local" and the "network" locations are actually on the san, just different sections of it)?
Our recommendation is to backup to a local drive, and then "Copyto" to a network location. This is because the copyto option includes network resilience to retry the copy if there's a temporary loss of connection etc.
| Quote: |
checked with SQL monitor the network utilization and found that 2nd option (backup to network and copy locally) has a spike in network utilization, 40% for a 10GB database, but it keeps using SAN communication for until the job ends. |
This sort of makes sense- you'd see an initial spike as the backup is done directly to the san (assuming you mean network communication to the san device?) and then the continual access following on until the end would be the file being copied.
| Quote: |
Now, when backing up to local path 1st then copy to network drive via UNC, the network utilization remains at 20% for the whole duration of the job. However, it is not until the end, than the iSCSI or SAN is used, I guess that for the verify step? |
This makes less sense to me- i'd assume the san usage to occur both with the initial backup and also the copy (assuming both the "local" and the "network" locations are actually on the san, just different sections of it)?
↧
RE: Hosted Storage
I got a solution for my problem also as i was confused about it.
↧
7.3.0.383 Issue: Refreshing Connection for 20m & counting
Just upgraded the SQL Cluster's 7.2.x to 7.3 and am STILL waiting for the only connection defined to the UI to refresh, while actually RDP'd to the primary node.
The server components were installed first, then the UI started, which gave me the updates-ready notification, so downloaded, installed and started the updated UI. Said YES to the Cache Compress that appears compulsory.
I can see jobs, in progress, but the green-spinner just keeps on spinning...
UI is utterly unusable for any Activity Monitoring.
Failing the cluster over/rebooting is not an option.
Actions:
I closed the UI and restarted it. Same issue.
D.O.A. can we say?
Windows Server 2008 R2 Enterprise SP1 Build 7601.
SQL Server 2012 Enterprise CU5.
The server components were installed first, then the UI started, which gave me the updates-ready notification, so downloaded, installed and started the updated UI. Said YES to the Cache Compress that appears compulsory.
I can see jobs, in progress, but the green-spinner just keeps on spinning...
UI is utterly unusable for any Activity Monitoring.
Failing the cluster over/rebooting is not an option.
Actions:
- 1. Open the UI.
2. Click on the Server.
3. Wait forever.
I closed the UI and restarted it. Same issue.
D.O.A. can we say?
Windows Server 2008 R2 Enterprise SP1 Build 7601.
SQL Server 2012 Enterprise CU5.
↧
RE: SQL2012 AlwaysOn Availability Groups and SQLBackup
I am also interested in the permissions. Our current method involves using the windows account that runs SQL Server to be the account used to run SQLBackup. To install SQLBackup I had made this account a sysadmin. I then changed that to db_creator when I wanted to restore. We use a proxy to run the actual backup jobs. Now I believe that I would have to give the proxy account the availability groups permissions.
Chris
Chris
↧
↧
RE: 7.3.0.383 Issue: Refreshing Connection for 20m & counting
Hi Stephen,
We've had one or two reports of this in the latest version and I'm not sure the underlying cause has been identified so far. In short, it seems like the local data store is encountering trouble after the cache compress.
You may find it springs into life after some time - how long have you left it?
If it's still not working after being left alone for ages, the quickest way to get things working again is to let it create a fresh file. It'll import history from SQL Server, but you'll lose the more detailed history specific to SQL Backup (such as compression rates etc.)
To do this, stop the SQL Backup service, and then locate the data.sdf file. On a cluster, this is usually installed to a shared folder between the nodes somewhere, and on a single server would be in c:\programdata\red gate\sql backup\data\<instance name>. Rename / move the file elsewhere, and then start the service again. A new file should get created, and things should come back to life.
We've had one or two reports of this in the latest version and I'm not sure the underlying cause has been identified so far. In short, it seems like the local data store is encountering trouble after the cache compress.
You may find it springs into life after some time - how long have you left it?
If it's still not working after being left alone for ages, the quickest way to get things working again is to let it create a fresh file. It'll import history from SQL Server, but you'll lose the more detailed history specific to SQL Backup (such as compression rates etc.)
To do this, stop the SQL Backup service, and then locate the data.sdf file. On a cluster, this is usually installed to a shared folder between the nodes somewhere, and on a single server would be in c:\programdata\red gate\sql backup\data\<instance name>. Rename / move the file elsewhere, and then start the service again. A new file should get created, and things should come back to life.
↧
How to restore encrypted backups?
I posted this question few minutes ago in a discontinued forum and then realized my mistake. So, posting in the correct forum now.
I am having some issues with the restore command when trying to restore encrypted backup. This is what I ran to take a backup:
EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE AjayDB TO DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH COMPRESSION = 1, THREADCOUNT = 4, KEYSIZE = 256, PASSWORD = ''<ENCRYPTEDPASSWORD>abc12defLHG</ENCRYPTEDPASSWORD>''"'
Now, when I try to restore it via GUI, I supply the same password as above: abcd12defLHG. But it says: bad password. I tried to do it thru script as well, but did not help. I tried both of the following commands - none helped.
EXECUTE master.dbo.sqlbackup N'-SQL "RESTORE DATABASE [AjayDB] FROM DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH DISCONNECT_EXISTING, PASSWORD = ''abc12defLHG'', REPLACE, MOVE ''AjayDB'' TO ''Z:\WrkFolder\AjayDB.mdf'', MOVE ''AjayDB_log'' TO ''Z:\WrkFolder\AjayDB.ldf'', RECOVERY"'
EXECUTE master.dbo.sqlbackup N'-SQL "RESTORE DATABASE [AjayDB] FROM DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH DISCONNECT_EXISTING, PASSWORD = ''<ENCRYPTEDPASSWORD>abc12defLHG</ENCRYPTEDPASSWORD>'', REPLACE, MOVE ''AjayDB'' TO ''Z:\WrkFolder\AjayDB.mdf'', MOVE ''AjayDB_log'' TO ''Z:\WrkFolder\AjayDB.ldf'', RECOVERY"'
This is the msg generated:
SQL Backup v7.0.6.2
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Restoring AjayDB (database) from:
Z:\WrkFolder\AjayDB_201304011011_full.bak
Error 710: Wrong password entered.
SQL Backup exit code: 710
(6 row(s) affected)
name value
---------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
exitcode 710
sqlerrorcode 0
filename001 Z:\WrkFolder\AjayDB_201304011011_full.bak
(3 row(s) affected)
Can you help?
Thanks.
Ajay
I am having some issues with the restore command when trying to restore encrypted backup. This is what I ran to take a backup:
EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE AjayDB TO DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH COMPRESSION = 1, THREADCOUNT = 4, KEYSIZE = 256, PASSWORD = ''<ENCRYPTEDPASSWORD>abc12defLHG</ENCRYPTEDPASSWORD>''"'
Now, when I try to restore it via GUI, I supply the same password as above: abcd12defLHG. But it says: bad password. I tried to do it thru script as well, but did not help. I tried both of the following commands - none helped.
EXECUTE master.dbo.sqlbackup N'-SQL "RESTORE DATABASE [AjayDB] FROM DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH DISCONNECT_EXISTING, PASSWORD = ''abc12defLHG'', REPLACE, MOVE ''AjayDB'' TO ''Z:\WrkFolder\AjayDB.mdf'', MOVE ''AjayDB_log'' TO ''Z:\WrkFolder\AjayDB.ldf'', RECOVERY"'
EXECUTE master.dbo.sqlbackup N'-SQL "RESTORE DATABASE [AjayDB] FROM DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH DISCONNECT_EXISTING, PASSWORD = ''<ENCRYPTEDPASSWORD>abc12defLHG</ENCRYPTEDPASSWORD>'', REPLACE, MOVE ''AjayDB'' TO ''Z:\WrkFolder\AjayDB.mdf'', MOVE ''AjayDB_log'' TO ''Z:\WrkFolder\AjayDB.ldf'', RECOVERY"'
This is the msg generated:
SQL Backup v7.0.6.2
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Restoring AjayDB (database) from:
Z:\WrkFolder\AjayDB_201304011011_full.bak
Error 710: Wrong password entered.
SQL Backup exit code: 710
(6 row(s) affected)
name value
---------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
exitcode 710
sqlerrorcode 0
filename001 Z:\WrkFolder\AjayDB_201304011011_full.bak
(3 row(s) affected)
Can you help?
Thanks.
Ajay
↧
RE: 7.3.0.383 Issue: Refreshing Connection for 20m & counting
I left it over 20 minutes before posting a bug report. When I returned to the server, a {sa} crash had been trapped and sent to Red Gate.
I don't care about the detailed stats as I'll have a fresh set after the cache is rebuilt and the daily Full backups have run. Thanks for the workaround.
MINOR POTENTIAL PROBLEM: one of the SQL Backup instances is on a cluster and the cluster manage is aware of the service - do NOT want to accidentally fail the beast over![Smile]()
Any advice?
Can we say NO to the Cache Compress? I have FIVE more machines to upgrade and don't want to have to fudge around on all ten machines, so far...
I don't care about the detailed stats as I'll have a fresh set after the cache is rebuilt and the daily Full backups have run. Thanks for the workaround.
MINOR POTENTIAL PROBLEM: one of the SQL Backup instances is on a cluster and the cluster manage is aware of the service - do NOT want to accidentally fail the beast over
Any advice?Can we say NO to the Cache Compress? I have FIVE more machines to upgrade and don't want to have to fudge around on all ten machines, so far...
↧
RE: How to restore encrypted backups?
You need to provide the plain text (non-encrypted) password in order to restore the database.
E.g. when you back up a database or set up a backup job using the GUI, it encrypts the password you entered so that anyone looking at the script will not know the plain-text password.
If SQL Backup allowed users to restore the database using the same encrypted value, it defeats the purpose of encrypting the password. Thus, you need to know the plain text password to restore the database.
E.g. when you back up a database or set up a backup job using the GUI, it encrypts the password you entered so that anyone looking at the script will not know the plain-text password.
If SQL Backup allowed users to restore the database using the same encrypted value, it defeats the purpose of encrypting the password. Thus, you need to know the plain text password to restore the database.
↧
↧
RE: How to restore encrypted backups?
Thanks for your reply. As you can see in the backup code I posted below, I passed the value for password as abc12defLHG. I think what you are saying is that since this value is enclosed between <ENCRYPTEDPASSWORD> and </ENCRYPTEDPASSWORD> tags, this is the encrypted form of the password. Well, in that case, I don't have the non-encrypted password. So, to fix my code for future, this is what I need to run to take backup:
EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE AjayDB TO DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH COMPRESSION = 1, THREADCOUNT = 4, KEYSIZE = 256, PASSWORD = ''abc12defLHG''"'
And then use abc12defLHG as password to restore when needed. Is my understanding correct?
Ajay
EXECUTE master..sqlbackup N'-SQL "BACKUP DATABASE AjayDB TO DISK = ''Z:\WrkFolder\AjayDB_201304011011_full.bak'' WITH COMPRESSION = 1, THREADCOUNT = 4, KEYSIZE = 256, PASSWORD = ''abc12defLHG''"'
And then use abc12defLHG as password to restore when needed. Is my understanding correct?
Ajay
↧
Kitchen Units Belfast
12 kitchen units plus oven set for only £595. www.solidwoodkitchen.co.uk. Best value kitchen units in Belfast. Tel 01616-694785. Kitchen Units Belfast.
↧
RE: 7.3.0.383 Issue: Refreshing Connection for 20m & counting
The server.dat is located under the "roaming" part of your user-profile rather than local.
I'd start by just removing the numbered .dat file and the localDataCache.dat. If you delete the servers.dat you'll need to re-add your servers into the console.
I'd start by just removing the numbered .dat file and the localDataCache.dat. If you delete the servers.dat you'll need to re-add your servers into the console.
↧
More Pages to Explore .....
