Veeam Endpoint Backup: error in SQL Server logs, why?

Backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)

Re: Veeam Endpoint Backup: error in SQL Server logs, why?

Veeam Logoby xpg934 » Wed Feb 22, 2017 2:56 pm

This screenshot I gave an example to show that enable or disable "application-aware processing" does not affect the fact that VAW is backing up the sql database.
Ie, even if "application-aware processing" disabled - VAW still performs the backup. As if "application-aware processing" enabled.

Now "application-aware processing" is disabled, but the log of the sql server still shows that VAW produces a backup of the database (VAW backup is scheduled at 3:00 every night):

Image

Code: Select all
02/22/2017 03:00:48,Backup,Unknown,Database backed up. Database: MyDatabase creation date(time): 2014/03/13(15:52:54) pages dumped: 17194202 first LSN: 1450614:2434:48 last LSN: 1450614:2456:1 number of dump devices: 1 device information: (FILE=1 TYPE=VIRTUAL_DEVICE: {'{44AB0DD1-24ED-47CA-A7AB-CDC5064B3924}1'}). This is an informational message only. No user action is required.
02/22/2017 03:00:46,spid56,Unknown,I/O was resumed on database MyDatabase. No user action is required.
02/22/2017 03:00:46,spid56,Unknown,I/O is frozen on database MyDatabase. No user action is required. However if I/O is not resumed promptly you could cancel the backup.
02/22/2017 02:06:42,Backup,Unknown,Database backed up. Database: MyDatabase creation date(time): 2014/03/13(15:52:54) pages dumped: 17194430 first LSN: 1450614:2379:86 last LSN: 1450614:2421:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {'D:\database.backup\MyDatabase.bak'}). This is an informational message only. No user action is required.
02/22/2017 00:00:37,spid29s,Unknown,This instance of SQL Server has been using a process ID of 1400 since 13.02.2017 23:09:03 (local) 13.02.2017 20:09:03 (UTC). This is an informational message only; no user action is required.

02/21/2017 03:00:48,Backup,Unknown,Database backed up. Database: MyDatabase creation date(time): 2014/03/13(15:52:54) pages dumped: 17175850 first LSN: 1450226:508:48 last LSN: 1450226:530:1 number of dump devices: 1 device information: (FILE=1 TYPE=VIRTUAL_DEVICE: {'{281C2BE9-D019-4B64-AAEA-32E327168473}1'}). This is an informational message only. No user action is required.
02/21/2017 03:00:47,spid56,Unknown,I/O was resumed on database MyDatabase. No user action is required.
02/21/2017 03:00:47,spid56,Unknown,I/O is frozen on database MyDatabase. No user action is required. However if I/O is not resumed promptly you could cancel the backup.
02/21/2017 02:06:34,Backup,Unknown,Database backed up. Database: MyDatabase creation date(time): 2014/03/13(15:52:54) pages dumped: 17176126 first LSN: 1450226:372:290 last LSN: 1450226:495:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {'D:\database.backup\MyDatabase.bak'}). This is an informational message only. No user action is required.
02/21/2017 00:00:16,spid25s,Unknown,This instance of SQL Server has been using a process ID of 1400 since 13.02.2017 23:09:03 (local) 13.02.2017 20:09:03 (UTC). This is an informational message only; no user action is required.

02/20/2017 03:00:47,Backup,Unknown,Database backed up. Database: MyDatabase creation date(time): 2014/03/13(15:52:54) pages dumped: 17156285 first LSN: 1449790:5036:185 last LSN: 1449790:5114:1 number of dump devices: 1 device information: (FILE=1 TYPE=VIRTUAL_DEVICE: {'{F8E090B0-95D6-4CDF-98BF-16B77013CF61}1'}). This is an informational message only. No user action is required.
02/20/2017 03:00:45,spid55,Unknown,I/O was resumed on database MyDatabase. No user action is required.
02/20/2017 03:00:45,spid55,Unknown,I/O is frozen on database MyDatabase. No user action is required. However if I/O is not resumed promptly you could cancel the backup.
02/20/2017 02:06:37,Backup,Unknown,Database backed up. Database: MyDatabase creation date(time): 2014/03/13(15:52:54) pages dumped: 17156590 first LSN: 1449790:3485:195 last LSN: 1449790:4348:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {'D:\database.backup\MyDatabase.bak'}). This is an informational message only. No user action is required.
02/20/2017 00:00:47,spid30s,Unknown,This instance of SQL Server has been using a process ID of 1400 since 13.02.2017 23:09:03 (local) 13.02.2017 20:09:03 (UTC). This is an informational message only; no user action is required.
xpg934
Influencer
 
Posts: 12
Liked: never
Joined: Fri Feb 10, 2017 2:15 pm
Full Name: Alexey Trizno

Re: Veeam Endpoint Backup: error in SQL Server logs, why?

Veeam Logoby Dima P. » Wed Feb 22, 2017 4:34 pm

Hello Alexey,

You need to enable the application aware processing (so server edition is required) and add your database to exclusion list via special regkey:

Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup

Multi-String value with the name ExcludeSqlDatabasesFromBackup
Add the instance/database name in any format like below. One entry per string.

IntanceName:DatabaseName;
InstanceName:;
:DatabaseName;
Dima P.
Veeam Software
 
Posts: 6743
Liked: 482 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: Veeam Endpoint Backup: error in SQL Server logs, why?

Veeam Logoby xpg934 » Mon Feb 27, 2017 8:41 am

Hello Dmitry,

Thanks, I'll try this today.

If it helps, maybe this setting should be configurable in UI?
xpg934
Influencer
 
Posts: 12
Liked: never
Joined: Fri Feb 10, 2017 2:15 pm
Full Name: Alexey Trizno

Re: Veeam Endpoint Backup: error in SQL Server logs, why?

Veeam Logoby xpg934 » Tue Feb 28, 2017 8:35 pm

Hello Dmitry,

Nothing has changed. VAW still performs backup of the database at 3:00 to a virtual device, and it goes on for 2 seconds, judging by the SQL Server log. Regular backup of the database is much longer (base >130Gb). In the log of VAW can be seen that all of databases on this server added to the skipdb, but it still does some work with SQL Server (backup of main working database), which is not needed, it seems, because we need only file-level backup.
xpg934
Influencer
 
Posts: 12
Liked: never
Joined: Fri Feb 10, 2017 2:15 pm
Full Name: Alexey Trizno

Re: Veeam Endpoint Backup: error in SQL Server logs, why?

Veeam Logoby Dima P. » Wed Mar 01, 2017 2:54 pm

Thanks Alexey. Can I ask you to open a support case - would like to get our QA team involved, so need your VAW logs.
Dima P.
Veeam Software
 
Posts: 6743
Liked: 482 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Previous

Return to Veeam Agent for Windows



Who is online

Users browsing this forum: No registered users and 1 guest

cron