I have a SQL cluster running as a Basic Availability Group.
Veeam Agent install went without a problem.
Backup of the Primary Node is successful and transaction loges are truncated as expected.
Veeam Agent on the Passive node states that the databases will be skipped.
However the Agent on the Passive node then tries to truncate the transaction logs anyway, which it cannot do.
The job finishes with a warning.
So it should be a simple fix in the Agent to skip transaction log processing on a Passive node and successfully complete the job. All the required information is logged by the Agent. It just doesn't handle this correctly.
-
- Service Provider
- Posts: 34
- Liked: 7 times
- Joined: Jan 29, 2019 12:12 pm
- Full Name: Paul Hambleton
- Contact:
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Bug - SQL basic availability cluster not supported correctly
Hello Paul,
Just to clarify the setup: that's managed by Veeam B&R agent job right? Thank you!
Just to clarify the setup: that's managed by Veeam B&R agent job right? Thank you!
-
- Service Provider
- Posts: 34
- Liked: 7 times
- Joined: Jan 29, 2019 12:12 pm
- Full Name: Paul Hambleton
- Contact:
Re: Bug - SQL basic availability cluster not supported correctly
Hi. Yes it is.
I have included the log details below. So hopefully it is something that is simple to handle in the Agent code.
Case # 03441331
I have included the log details below. So hopefully it is something that is simple to handle in the Agent code.
Case # 03441331
Code: Select all
[27.02.2019 20:33:32] <01> Info Database is in basic group in secondary state and will be skipped: DbName: XXXXXXX, Uid: [2017-03-31 12:49:59 (5)], GroupDbId: 796ae4d2-dd88-48d1-b0c9-1662e806de30, SynchronizationState: Synchronizing, SynchronizationHealth: Healthy, DatabaseState: Online
[01.03.2019 02:01:09] Info <1a54> Database XXXXXXX: failed to truncate transaction logs. Error: Code = 0x80040e14
[01.03.2019 02:01:09] Info <1a54> Code meaning = IDispatch error #3092
[01.03.2019 02:01:09] Info <1a54> Source = Microsoft OLE DB Provider for SQL Server
[01.03.2019 02:01:09] Info <1a54> Description = The target database, 'XXXXXXX', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online.
Who is online
Users browsing this forum: No registered users and 19 guests