- RSS Channel Showcase 2034876
- RSS Channel Showcase 4424473
- RSS Channel Showcase 9445923
- RSS Channel Showcase 7962150
Articles on this Page
- 08/27/13--01:32: _RE: red gate activi...
- 08/27/13--01:36: _Feature Request.
- 08/28/13--00:51: _同...
- 08/01/13--16:59: _RE: Full Text not o...
- 08/30/13--00:09: _RE: Feature Request.
- 09/09/13--01:30: _SQL2012 AlwaysOn Av...
- 09/09/13--09:35: _RE: SQL Backup 7.4
- 09/09/13--14:59: _RE: Warning 130: MO...
- 09/10/13--10:34: _RE: SQL2012 AlwaysO...
- 09/19/13--09:01: _Network resilience ...
- 09/22/13--19:27: _RE: Network resilie...
- 09/23/13--15:15: _Deleting old backup...
- 09/23/13--15:25: _Registry permission...
- 09/23/13--21:31: _RE: Registry permis...
- 09/23/13--21:37: _RE: Deleting old ba...
- 09/24/13--00:07: _RE: Registry permis...
- 09/24/13--00:09: _RE: Deleting old ba...
- 09/25/13--08:43: _RE: Network resilie...
- 09/25/13--19:49: _RE: SQL2012 - Avail...
- 11/06/13--18:41: _RE: [SQL Backup 7]C...
- 08/27/13--01:32: RE: red gate activity history constant refresh state
- 08/27/13--01:36: Feature Request.
- 08/01/13--16:59: RE: Full Text not observing MOVE on a RESTORE
- 08/30/13--00:09: RE: Feature Request.
- 09/09/13--01:30: SQL2012 AlwaysOn Availability Groups
- 09/09/13--09:35: RE: SQL Backup 7.4
- 09/09/13--14:59: RE: Warning 130: MOVETO error: Failed to move file
- 09/10/13--10:34: RE: SQL2012 AlwaysOn Availability Groups
- 09/19/13--09:01: Network resilience and where it applies
- 09/22/13--19:27: RE: Network resilience and where it applies
- 09/23/13--15:15: Deleting old backups from other server with Erase command
- 09/23/13--15:25: Registry permission issue with SQLbackup 18.104.22.168/SQL2012
- 09/23/13--21:31: RE: Registry permission issue with SQLbackup 22.214.171.124/SQL2012
- 09/23/13--21:37: RE: Deleting old backups from other server with Erase command
- 09/24/13--00:07: RE: Registry permission issue with SQLbackup 126.96.36.199/SQL2012
- 09/24/13--00:09: RE: Deleting old backups from other server with Erase command
- 09/25/13--08:43: RE: Network resilience and where it applies
- 09/25/13--19:49: RE: SQL2012 - Availability Groups - backing up via replica
- 11/06/13--18:41: RE: [SQL Backup 7]Cannot conduct database backup (exitcode 669)
I found the only way to get the backup history to display quickly, was to reduce the amount of history data held down to 5 days worth. Even then it takes about 30 seconds to refresh.
I am not sure if this is the right place to post this, but I could ask that the following feature be put into SQL Backup:
It would be good to be able to filter the Activity History by the diffrent columns, not just being able to sort by them. I.E Show only full backups, or show backups taken during a date range, only backups that failed etc.
It would help a lot in searching for problems and quickly filtering out data.
タイトリストは、長い長い時間のためのアイアンのために "700''番号を使用しています。それは金属の森、900 NUM-BERをを使用しています。 "7"は新しい年モデル、2012年に "12"のスタンドしながら、アイロンの略です。アクシネットは、この検証プロセス中に受信したフィードバックは、タイトリスト VG3 アイアン 価格世界中のゴルフショップで利用できるタイトリスト製品のデザイン、仕様に影響を及ぼすと言います。 712アイアンは、小売で利用できるようになります時にはまだ言葉はなし。
新しいMBとCBアイアン：新しいMBとCBアイアンはクラシックなライン、プロフィール、固体音、感触とクラシックな鍛造品のショットシェーピング精度を維持。しかし、彼らはまた、現代的なプレイアビリティ、プレイヤーの研究開発の30年以上から得られる利益、技術革新や製造プロセスの進歩を提供します。 712 CB アイアン 価格が振り返る、感じるとパフォーマンスの高い熟練したプレイヤーdemand.While新しいCB、また偽造、浅いキャビティバックデザインが特徴を実現鍛造アイアン古典的な筋肉です。新しいMBとCBの両方が戻って渡って多面的な面を備えています愛情として知って再設計されたバック特色 "犬の骨"をインパクトエリアの後ろに狭めながら表面はかかととつま先が大きい。もっと質量の背後にこの機能は、位置従来の固体のためのインパクトエリアは、ブレードアイアンから期待感じる。
"我々は新しいMBとCBの設計のための計画を策定し始めたとき、我々は、プロジェクトが完了し再発明ではない、再解釈されることを知っていた、"スティーブPelisek、ゼネラルマネージャー、タイトリストのゴルフクラブは言った。 "オリジナルのMBとCBモデルは非常によくツアーで、同様に我々は従来のブレードプレーヤーと共振し、コアの設計の基礎を提供することに成功していた知っていた市場で受信された。我々は、我々は新しいオデッセイ プロタイプ ツアー シリーズ パターモデルに組み込まれた改良を、作ることができるいくつかの地域が、世界最高の選手たちとの仕事を通じて識別でした。新しいMBとCBは、まだ非常によく受け入れられる第一世代を作ったそれらの重要な設計要素を体現しています。 "
I could not reproduce your error using SQL Backup 188.8.131.52. It doesn't make sense why there is a secondary data file named ftrow_KBIndex.ndf in the target full-text folder.
Could you please try restoring this backup on another server, and see if you get the same results?
I am the support engineer that is investigating this issue you have raised. Thanks for posting your desired feature request in our forums. At this stage what I can suggest is that if you would like is that I put this forward as a feature/change request to our product management.
I can also suggest that you put this in the SQL Backup user voice section of our website. This is a forum-style thread where backup users can put in their desired features for the product.
Thanks for your feedback in this matter.
Does anyone know if there are any plans to be able to use a replica server within SQL Backup anytime soon?
Or, has anyone actually managed to get SQL Backup installed on an Availability Group at all?
I am upgrading SQL Backup from V184.108.40.206 to v220.127.116.11 on our servers.
Last Thursday I upgraded our test server and it worked perfectly.
On Friday I upgraded the first of our 3 live servers, but the upgrade appeared to hang at the first step of the upgrade. I waited over 30 mins before I thought to check the value in the server properties, which showed the 'Upgrade available' icon gone and the properties window showing the version as v18.104.22.168 I had to exit the upgrade by stopping the process via Task Manager, but it appears to have completed correctly.
Today I had exactly the same experience on our second server (apart from the fact that I only waited 5 mins before checking the server).
I plan to upgrade our third server tomorrow at 5:00pm I thought I would report this to you in case you wanted to observe what is happening on our system (or in case this is a known issue which you have a fix for)
Please contact me tomorrow on email@example.com or by phone on (020) 7343 1885 if you want to see the problem in action (assuming it happens again )
Peter - Are there any plans to include an option in a future release to force the removal of a source file even if the destination file already exists in a MOVETO configuration?
SQL Backup Pro can be installed on SQL Server instances included in AlwaysOn Availability Groups (introduced in SQL Server 2012), but does not support the features of Availability Groups. SQL Backup Pro 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 failed server must be created manually on the new primary server.
See Technical notes on the requirements page.
On step 5 of the Schedule Backup Jobs wizard, we have settings for Network resilience. Does this apply to both the folders in step 4?
For example, I'm currently using a UNC path in the "Backup location" and not using the "copy backup to network" option. Will I still get the Network resilience retries?
Yes, the network resilience settings apply to both the backup process and the file copy process.
In the past weeks we have moved all out SQL databases to new servers with SQL 2012. While moving our databases we also moved our old SQL backups to this new servers, because we always maintain a backup history of 45 days.
To remove backups older then 45 days we use a SQL agent job with the command
EXECUTE master..sqlbackup '-SQL "ERASE FULL_BACKUPS FOR [database name] FROM DISK = ''Local Path to backup folder]'' KEEP = 45 "'
We have used this job for ages, but on our new servers the job does not seem to delete any old SQLbackups, almost resulting in full harddisks
After a lot of debugging i found that the command only deletes files created by the server running the job. Probably it compares the servername with the servername from the backup header.
Because we moved the backups grom our old servers to the new servers, the backups originaly made by one of the old servers are not being deleted after 45 days.
I cannot find anything about this issue in the documentation, is this by design?
Is there a way to work around this behaviour?
The last 2 weeks we implemented 12 new SQL 2012 servers and installed the latest version of SQLbackup (22.214.171.124)
After (succesfull) installation SQLbackup refused to work and evey time we configured the Server options these values disappeared after restarting the GUI.
Finaly after a lot of debugging we found this issue was caused by the user running sqlbackup having no rights on the redgate registry hyves
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\(LOCAL)
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\(LOCAL)
After manualy granting the nessesairy permissions everything now works OK, but this is probably a bug in the setup, probably popping up because we don't assign sqlserver local admin rights
Could you please let me know the Windows operating system version you installed SQL Backup on?
Yes, that is by design. We always want to minimize the number of accidental deletions, hence why the strict deletion conditions.
At present, there is no workaround for this.
The OS is Windows Server 2012 Standard edition.
SQL server is SQL Server 2012, als standard edition.
I understand the desission, but it would be nice to have some kind of override for this.
Thanks, petey. You have saved me some time and provided help that was not explicitly found elsewhere.
The error you are seeing:
|08/06/2013 10:51:40: Error 880: BACKUP DATABASE permission denied in database: (AManagement) |
08/06/2013 10:51:40: SQL error 978: The target database ('AManagement') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online.
was raised because SQL Backup is attempting to access the database to check if you have rights to back up that database. You can disable that check altogether, by creating a DWORD registry entry, SkipChecks, with the value 1. This entry needs to be created in the
HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>
registry node. However, this means that all users with permission to run the sqlbackup extended stored procedure will be able to back up and restore any database on that instance.
This workaround isn't perfect in that SQL Backup will still try to access the database to get its size but fail with the following warning:
|Warning 167: Failed to get database size from server.|
SQL error 978: The target database (xxx') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online.
but at least you're able to back up the secondary replica database.
Thanks, the issue is caused by Group assignment of Domain ID.
(We through the Domain admin added the domain ID to a domain group that have local administrator privilege, but they actually not.)
I grant the access privilege directly to the domain account that starting SQL backup Agent service and the problem is solved.