RE: Licensing.

December 17, 2013, 12:08 am

≫ Next: ERASEFILES on remote server fails for just 1 DB

≪ Previous: RE: Licensing.

$

0

0

It is safest to test the backup by actually restoring it, as there can be errors in the backup file that a RESTORE VERIFYONLY process cannot catch, but that can prevent a successful restore.

Could you please try using the SQBConverter.exe command line interface?

---

ERASEFILES on remote server fails for just 1 DB

December 19, 2013, 1:14 pm

≫ Next: RE: ERASEFILES on remote server fails for just 1 DB

≪ Previous: RE: Licensing.

$

0

0

Server Version 7.6.0.29 but has been having issues for many months on prior 7.x versions.

I have 8 databases including the system and 2 SSRS DBs.

Two of them are copied over the network to the exact same folder on the backup file server.

They both copy the full and tranlog backups, full to folder-1, tranlog to folder-2, both 1st-level folders on the FS. No subfolders are involved.

I have to periodically stop the SQL Backup service on the production instance (not a great plan!) in order to release the "file is being used by another process" lock on file deletion. As space is scant, I have to keep tabs on this. Having last week, as in under 10 days ago, manually deleted files that are months older than the 15-day retention (remote), I reviewed the jobs in detail today only to find that the largest database's tranlog backup jobs are "Successful (with warnings)". Those warnings are ALL concerning the kind of message shown below:

Code:

SQL Backup log file 7.6.0.29   -SQL "BACKUP LOG [MyDatabase] TO DISK = 'E:\DB_Backups\<database>\<AUTO>.sqb' WITH ERASEFILES = 2, ERASEFILES_REMOTE = 15, FILEOPTIONS = 4, CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4, COPYTO = '\\FileServer\MYSERVER_logs',  INIT, THREADCOUNT = 6, VERIFY "   -----------------------------  ERRORS AND WARNINGS -----------------------------     12/19/2013 12:01:05 PM: Deleting old backup file: E:\DB_Backups\MyDatabase\LOG_MYSERVER_MyDatabase_20131217_114600.sqb 12/19/2013 12:01:05 PM: Deleting old backup file: E:\DB_Backups\MyDatabase\LOG_MYSERVER_MyDatabase_20131217_120100.sqb 12/19/2013 12:01:05 PM: Deleting old backup file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_051600.sqb 12/19/2013 12:01:06 PM: Warning 161: ERASEFILES error: Failed to delete file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_051600.sqb.  Error code: 32 (The process cannot access the file because it is being used by another process). 12/19/2013 12:01:06 PM: Deleting old backup file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_053100.sqb 12/19/2013 12:01:07 PM: Warning 161: ERASEFILES error: Failed to delete file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_053100.sqb.  Error code: 32 (The process cannot access the file because it is being used by another process). 12/19/2013 12:01:07 PM: Deleting old backup file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_054600.sqb 12/19/2013 12:01:09 PM: Warning 161: ERASEFILES error: Failed to delete file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_054600.sqb.  Error code: 32 (The process cannot access the file because it is being used by another process). 12/19/2013 12:01:09 PM: Deleting old backup file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_060100.sqb 12/19/2013 12:01:10 PM: Warning 161: ERASEFILES error: Failed to delete file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_060100.sqb.  Error code: 32 (The process cannot access the file because it is being used by another process). 12/19/2013 12:01:10 PM: Deleting old backup file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_113100.sqb 12/19/2013 12:01:11 PM: Warning 161: ERASEFILES error: Failed to delete file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_113100.sqb.  Error code: 32 (The process cannot access the file because it is being used by another process). 12/19/2013 12:01:11 PM: Deleting old backup file: \\FileServer\MYSERVER_logs\LOG_MYSERVER_MyDatabase_20131204_114600.sqb

Diagnosis, please.

RE: ERASEFILES on remote server fails for just 1 DB

December 21, 2013, 4:17 pm

≫ Next: RE: ERASEFILES on remote server fails for just 1 DB

≪ Previous: ERASEFILES on remote server fails for just 1 DB

$

0

0

The next time this happens, could you please run

EXEC master..sqbutility 9997

to generate a stack trace file, and send me the file (peter.yeoh@red-gate.com)? This file is named SQBCoreService_<instance name>_bugreport.txt, and is located in 'C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\' on Windows 2003 and older, and 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer.

Thanks.

RE: ERASEFILES on remote server fails for just 1 DB

December 23, 2013, 5:57 am

≫ Next: Any attention should pay when format disks?

≪ Previous: RE: ERASEFILES on remote server fails for just 1 DB

$

0

0

Hi

Another quick thing to check for, if you have an anti-virus application that performs an on-access or real-time check of a file when it is opened to read, edited or being created. This may prevent SQL Backup reading the backup file header and deleting the backup file if it meets the criteria for deletion.

Many Thanks
Eddie

Any attention should pay when format disks?

December 23, 2013, 10:34 pm

≫ Next: RE: Any attention should pay when format disks?

≪ Previous: RE: ERASEFILES on remote server fails for just 1 DB

$

0

0

Any attention should pay when format disks?
With the development of society, most of people usually use the PC to work. Obviously, it exits many potential danger. For example, many important e-mails or information are lost incidentally.
We should back up our information in addition to happening misfortune things.
Some of my friends tell me one way. Download some ext3 data recovery software to back up your files is a good choice.
http://www.easeus.com/data-recovery/partition-recovery-software/recover-deleted-lost-ext2-ext3-partition.htm
But i also want to know there is other way to solve this problem.
If you know how to solve this problem, please reply to me.[/url]

RE: Any attention should pay when format disks?

December 26, 2013, 9:05 am

≫ Next: RE: SQL error 3013 Backup Database is terminating abnormally

≪ Previous: Any attention should pay when format disks?

$

0

0

Unfortunately our tool SQL Backup does not address the problem you are looking for a solution to.
SQL Backup Pro creates compressed, encrypted backups of Microsoft SQL Server databases.
http://documentation.red-gate.com/display/SBU7/SQL+Backup+Pro+7+documentation#

RE: SQL error 3013 Backup Database is terminating abnormally

December 9, 2013, 5:52 am

≫ Next: RE: Cannot install on windows 2012 cluster

≪ Previous: RE: Any attention should pay when format disks?

$

0

0

Based on the following in the output:

Quote:

SQL error 3043: BACKUP 'Interfax' detected an error on page (1:8650358) in file 'G:\Data\Interfax_DataNew.MDF'.

It looks like your database has a consistency issue. Try running DBCC CHECKDB on that database to see if the same error is reported.

RE: Cannot install on windows 2012 cluster

January 2, 2014, 1:44 pm

≫ Next: RE: SQL Backup 7.2.1.4

≪ Previous: RE: SQL error 3013 Backup Database is terminating abnormally

$

0

0

My company uses SQL Backup 6 for all databases. We plan to add a new windows cluster for some of our servers, but have the same installation issues as the OP when installing SQL Backup 6 on a proof-of-concept system.

Does any version of SQL Backup currently support windows clustering with SQL Server 2012 sp1 on Windows Server 2012 R2?

Note: we don't plan to use availability groups.

---

RE: SQL Backup 7.2.1.4

January 6, 2014, 2:49 am

≫ Next: RE: ERASEFILES on remote server fails for just 1 DB

≪ Previous: RE: Cannot install on windows 2012 cluster

$

0

0

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 v7.4.0.23 � I had to exit the upgrade by stopping the process via Task Manager, but it appears to have completed correctly.

RE: ERASEFILES on remote server fails for just 1 DB

January 7, 2014, 11:28 am

≫ Next: RE: ERASEFILES on remote server fails for just 1 DB

≪ Previous: RE: SQL Backup 7.2.1.4

$

0

0

eddie davis wrote:

Hi Another quick thing to check for, if you have an anti-virus application that performs an on-access or real-time check of a file when it is opened to read, edited or being created. This may prevent SQL Backup reading the backup file header and deleting the backup file if it meets the criteria for deletion. Many Thanks Eddie

The odd thing, Eddie, is that of all the database backup being copied, this is the only database experiencing issues, and the UNC location is identical for another database on the same instance. If an Anti-virus tool is interfering, why would it choose just this ONE database's files?

RE: ERASEFILES on remote server fails for just 1 DB

January 7, 2014, 11:40 am

≫ Next: RE: ERASEFILES on remote server fails for just 1 DB

≪ Previous: RE: ERASEFILES on remote server fails for just 1 DB

$

0

0

petey wrote:

The next time this happens, could you please run EXEC master..sqbutility 9997 to generate a stack trace file, and send me the file (peter.yeoh@red-gate.com)? This file is named SQBCoreService_<instance name>_bugreport.txt, and is located in ... 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer.

Having found that the latest (2 minutes after execution) had also failed to delete files, I ran the command on my Windows 8.1 laptop. Having searched for the file on both the SQL Cluster and my Laptop, no such file exists.

Please advise.

RE: ERASEFILES on remote server fails for just 1 DB

January 7, 2014, 4:28 pm

≫ Next: RE: ERASEFILES on remote server fails for just 1 DB

≪ Previous: RE: ERASEFILES on remote server fails for just 1 DB

$

0

0

Are you able to manually delete any one of the files listed as being in use, from the primary server, and also from the file server?

RE: ERASEFILES on remote server fails for just 1 DB

January 7, 2014, 6:27 pm

≫ Next: sqlbackup.exe

≪ Previous: RE: ERASEFILES on remote server fails for just 1 DB

$

0

0

Only if I restart the SQB Core Service. Restarting appears to release whatever enduring lock the Service retains upon alleged completion of the file transfer.

I only dealt with the remote files as they're the only ones cited in any "Completed with warnings" log messages.

sqlbackup.exe

January 9, 2014, 11:58 am

≫ Next: RE: sqlbackup.exe

≪ Previous: RE: ERASEFILES on remote server fails for just 1 DB

$

0

0

We have a windows 2012 R2 cluster, sql 2012, with two nodes, call them:
ServerA
ServerB
Sql virtual name: Sql_Cluster

We log ship some databases to above cluster, or will be, we're setting up/testing this now. I've run into a problem trying to run command line of sql backup (SqlBackupC.exe).
We only use default instances, don't have any sql servers with a named instance. On our current servers (not the cluster ) we can run :
SqlBackupC.exe -SQL "RESTORE LOG [DB] FROM DISK = [E:\backup\DB_10140108_123550_LOG.sqb]
WITH STANDBY = [E:\backup\StandByFiles\DB.dat], PASSWORD = [DBPWD], MOVETO=[Complete\db]" -E

and will run fine.
If I run same script on our cluster, I get error
SQL error 17: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Server :
Windows authentication
1/9/2014 7:48:51 AM: Failed to connect to SQL Server instance:

My user account is a sys admin on this sql. It looks to me like it is trying to use machine name as name of sql server, so trying to connect to sql named: serverA, we don't have that, since is cluster, sql is called sql_cluster. In trying to force it to connect to proper sql name, I looked for a -S or some parameter to pass in server name, but only saw -I for instance name. if i try -I and put in sql_cluster, it fails, looking for server: serverA/sql_cluster, we don't have named instance like that so that fails.
If a use -I (local) it works,
Somehow it uses different method to find sql server name if I omit it, different than if I pass -I (local) ? That seems strange, so maybe I'm missing something? I would expect all clusters to have this make up, where have 2 + servers, and sql on it but w/ diff name than the actual server name. Might our cluster not be set up right?

RE: sqlbackup.exe

January 9, 2014, 11:26 pm

≫ Next: Any way to automate triggering of "new" DB backup?

≪ Previous: sqlbackup.exe

$

0

0

It's a bug in SQL Backup when the default instance is a clustered instance. The workaround is as you mentioned: use the -I parameter with (local) or . i.e.

sqlbackupc -sql "BACKUP ..." -I (local)

or

sqlbackupc -sql "BACKUP ..." -I .

A bug report has been raised (SB-5555).

---

Any way to automate triggering of "new" DB backup?

January 10, 2014, 8:44 am

≫ Next: RE: Any way to automate triggering of "new" DB backup?

≪ Previous: RE: sqlbackup.exe

$

0

0

Hi,
There are 2 things we'd like to automate.
We have weekly full backup and daily differentials, we do both by specifying:
BACKUP DATABASES [*] TO DISK

1. The first problem is that if someone created anew DB and didn't notify DBA then this newly created DB will produce an error while trying to do differential backup and Full backup wouldn't happen till scheduled day.
Any automated way to fix this issue other than to monitor this manually?

2.Master Database differential backup is not allowed, any way to specify in the synttax "Backup All DBs But... ?

Many Thanx

S

RE: Any way to automate triggering of "new" DB backup?

January 10, 2014, 9:01 am

≫ Next: Setting up Log Shipping under fire

≪ Previous: Any way to automate triggering of "new" DB backup?

$

0

0

Thank you for your support request.

To answer your questions:

Quote:

1. The first problem is that if someone created anew DB and didn't notify DBA then this newly created DB will produce an error while trying to do differential backup and Full backup wouldn't happen till scheduled day. Any automated way to fix this issue other than to monitor this manually?

Assuming that you are using SQL Backup V7.1 or higher you need to add FULLIFREQUIRED keyword to your backup syntax by manually editing the job within SSMS -SQL Server Agent ->Jobs. Further information can be found in this HELP article.

Quote:

2.Master Database differential backup is not allowed, any way to specify in the synttax "Backup All DBs But... ?

You can only perform Full backups of the master database, SQL will not allow you to perform differential or transaction log backups of the master database.

Many Thanks
Eddie

Setting up Log Shipping under fire

January 12, 2014, 10:53 am

≫ Next: RE: Setting up Log Shipping under fire

≪ Previous: RE: Any way to automate triggering of "new" DB backup?

$

0

0

I've got a production db that has users in it from 6:00 AM to 11:00 PM and runs batch processes from 11:30 PM to 1:00 AM. After that it does maintenance jobs to be RTG at 6:00 AM the next morning.

I want to set up log shipping. I've got another server ready to go, but I'm not clear on just what the steps are when the db is in production like that.

Does the target server need to have RedGate Backup Pro installed?

When should I take the backup that goes on the second server to be the basis for the log shipping?

How do I insure that the shipping starts up smoothly if the database is in use?

Am I making this harder than I need to?

RE: Setting up Log Shipping under fire

January 12, 2014, 5:55 pm

≫ Next: Feature Request

≪ Previous: Setting up Log Shipping under fire

$

0

0

Quote:

Does the target server need to have RedGate Backup Pro installed?

Yes it does.

Quote:

When should I take the backup that goes on the second server to be the basis for the log shipping?

Usually off production hours so as not to affect your users' activities, but that would depend on how long the backup would take and if your production server has more than adequate CPU and disk I/O to spare for the backup.

Quote:

How do I insure that the shipping starts up smoothly if the database is in use?

You can take full and transaction log backups even when the database is in use.

Feature Request

January 13, 2014, 12:35 pm

≫ Next: RE: Feature Request

≪ Previous: RE: Setting up Log Shipping under fire

$

0

0

I would like to be able to set a database size threshold that governs whether or not to split a database backup into multiple files. I manage a few hundred databases that range in size from a couple of MB to a couple of TB. Rather than to have to create and manage multiple backup jobs just to handle specific databases (and have to make changes as the databases grow), I would like to be able to set up a rule that determines whether or not to generate multiple backup files based on the size of the database. Furthermore, I would like to set it up so that the number of backup files that are created is determined by the size of the database.

I realize that I could probably write a powershell wrapper around the Red Gate command line to do this. But, hey, I'm a lazy DBA and I'm paying you for support, so I figure I'd ask you guys to do it for me.

Regards,
Rob