Change in behaviour for Availability Group backups?

[btripz]

Hi,

We have recently updated the Maintenance Solution on our QA SQL Servers instances. On 2 of the servers we have 1 database that is part of an availability group, we also have other databases that aren't.

Before the update availability group backups used to run on the secondary server, Backup Preference is set to 'Prefer Secondary', so this is expected. The backup on the secondary server was also switched to a CopyOnly backup, again as expected.

Now however backups are only taken on the Primary server.

This is despite the log suggesting that the backup should be taken

Database: [SITE] [SQLSTATE 01000]
State: ONLINE [SQLSTATE 01000]
Standby: No [SQLSTATE 01000]
Updateability: READ_WRITE [SQLSTATE 01000]
User access: MULTI_USER [SQLSTATE 01000]
Recovery model: FULL [SQLSTATE 01000]
Encrypted: No [SQLSTATE 01000]
Is accessible: Yes [SQLSTATE 01000]
Availability group: SITS_AG [SQLSTATE 01000]
Availability group role: SECONDARY [SQLSTATE 01000]
Availability group backup preference: SECONDARY [SQLSTATE 01000]
Is preferred backup replica: Yes [SQLSTATE 01000]
Differential base LSN: 1301188000000329400223 [SQLSTATE 01000]
Last log backup LSN: 1301200000011711300001 [SQLSTATE 01000]
Allocated extent page count: N/A [SQLSTATE 01000]
Modified extent page count: N/A [SQLSTATE 01000]
[SQLSTATE 01000]

If we specify CopyOnly='Y' then the backup is taken on the Secondary server, but the other databases on the server also have CopyOnly backups taken!! (This is not really a problem as I believe that T-log backups can be applied to a CopyOnly backup).

Is this now the expected behaviour of the DatabaseBackup?

If so is the only solution to create 2 backup tasks, one for the Availability Group backup and one for the normal database backups?

Thanks in advance