Comments
Sort by recent activity
There will need to be 2 jobs. For the hourly log backups, look into the RESTORE LOG command in SQL Backup. It allows you to specify a search pattern for the transaction log backup files, which it will then restore automatically for you in sequential order, then move the files to a different folder so that it will not be restored again. So it's one T-SQL job that may look something like this: EXEC master..sqlbackup '-sql "RESTORE LOG mydb FROM DISK = [\\backupfiles\mydb\logs\*.sqb] WITH STANDBY = [g:\dbundo\mydb.und], MOVETO = [\\backupfiles\mydb\logs\restored\]"' For the weekly full backup, look into using the LATEST_FULL option. This instructs SQL Backup to look for and restore the latest full backup file(s) in a given folder. It's a T-SQL job that may look something like this:
EXEC master..sqlbackup '-sql "RESTORE DATABASE mydb FROM DISK = [\\backupfiles\mydb\full\*.sqb] LATEST_FULL WITH STANDBY = [g:\dbundo\mydb.und]"'
/ comments
There will need to be 2 jobs.For the hourly log backups, look into the RESTORE LOG command in SQL Backup. It allows you to specify a search pattern for the transaction log backup files, which it w...
Could you please raise a support ticket so that we can follow up on this internally? Thank you. / comments
Could you please raise a support ticket so that we can follow up on this internally? Thank you.
Could you please run this query on the instance hosting the secondary replica and post the results? Thanks.
SELECT c.secondary_role_allow_connections, d.primary_replica
FROM master.sys.databases a
INNER JOIN master.sys.dm_hadr_availability_replica_states b ON a.replica_id = b.replica_id
INNER JOIN master.sys.availability_replicas c ON a.replica_id = c.replica_id
INNER JOIN master.sys.dm_hadr_availability_group_states d ON b.group_id = d.group_id
WHERE a.name = 'ActuarialUpdates'
AND b.role = 2
AND c.replica_server_name = @@SERVERNAME / comments
Could you please run this query on the instance hosting the secondary replica and post the results? Thanks.
SELECT c.secondary_role_allow_connections, d.primary_replica
FROM master.sys.databases...
By design, SQL Backup checks the rights of the user backing up the database, and also retrieves the database size and other details from the database that is being backed up. If your secondary replica does not allow connections, SQL Backup attempts to get those details from the primary replica. As you pointed out, this is failing because the instance the primary replica is running on a non-default port. Can you confirm that your secondary replica does not allow connections? Thanks. / comments
By design, SQL Backup checks the rights of the user backing up the database, and also retrieves the database size and other details from the database that is being backed up.If your secondary repli...
On the machine where the SQL Server instance is running, open the folder where SQL Backup is installed e.g. C:\Program Files (x86)\Red Gate\SQL Backup 10\<instance name>\ Open the file named log4backup.config. Change the restrictedToMinimumLevel setting to debug. Now open a command prompt window and navigate to the same folder. Run the following: sqbhostedstorageclient.exe authorize --instance <SQL Server instance name> --azure "<Azure account name>" "<Azure access key>" "<blob container name>" replacing <SQL Server instance name>, <Azure account name>, <Azure access key>, and <blob container name> with your values. Run the command, and a detailed log will be generated in the C:\ProgramData\Red Gate\Logs\SQL Backup 10\ folder. Send us that log so we can see where the authorization process is failing in detail. / comments
On the machine where the SQL Server instance is running, open the folder where SQL Backup is installed e.g.C:\Program Files (x86)\Red Gate\SQL Backup 10\<instance name>\Open the file named log4back...
What application are you using, that led you to believe that the SQL Backup Agent service is consuming excessive bandwidth? The SQL Backup Agent service runs as a Windows service, and communicates almost exclusively (more on that later) with the SQL Server instance running on the same machine. This is done via the use of interprocess-communication objects (IPC) and local SQL Server connections, hence no ports are actually required/used by the SQL Backup Agent service. When you use the SQL Backup GUI, the GUI first connects to the SQL Server instance, which in turn communicates with the SQL Backup Agent service via IPC objects. There is no direct communication between 'outside' components and the SQL Backup Agent service. The only exception is when your backup job is set to upload the backup file to a cloud storage provider (Amazon, Azure, etc). An external process (SQBHostedStorageClient.exe) is started by the SQL Backup Agent service to perform the upload. That is the only situation I know of where you can measure the bandwidth consumed by the SQL Backup Agent service (indirectly, since it's actually consumed by the uploader). / comments
What application are you using, that led you to believe that the SQL Backup Agent service is consuming excessive bandwidth?The SQL Backup Agent service runs as a Windows service, and communicates a...
The Maintenance Plan Wizard only supports SQL Server versions 2005, 2008 and 2012. Unfortunately, it falls back to the SQL Server 2005 libraries for any post-2012 versions, which explains why it's looking for such an old .Net version. / comments
The Maintenance Plan Wizard only supports SQL Server versions 2005, 2008 and 2012. Unfortunately, it falls back to the SQL Server 2005 libraries for any post-2012 versions, which explains why it's...
The process log files deletion is triggered at the end of every SQL Backup process. So something like this will trigger it to run: EXEC master..sqlbackup 'BACKUP DATABASE model TO DISK = [<AUTO>]"' Which logs are not getting deleted? Is it those in the primary log file folder, or those in the LOGTO folder? / comments
The process log files deletion is triggered at the end of every SQL Backup process. So something like this will trigger it to run:EXEC master..sqlbackup 'BACKUP DATABASE model TO DISK = [<AUTO>]"'...