As much as it was a very long time ago,  it was indeed the source of our issue,  once we removed the duplicated articles the issue never came back.

One option is to write the backups (full \ log) on a local EBS volume and subsequently push them to S3.  It will make restoration slightly more complex than just...

Yeah you do,  I'm not sure why it doesn't cover it as it would have made sense to.

I had similar issues when setting this up on SQL 2017.  This may be of some  help to you:

https://www.sqlservercentral.com/Forums/1924105/Always-on-and-SSISDB

Sorry for the slow reply.  I assume the URL they gave you is something like this:

April 6, 2018 at 9:03 am

#1985815

This is one way to do it:

$aws_profile = 'MyAWSProfile'
$awskey = 'XXXXXXXXXXXXX'
$awssecretkey = 'XXXXXXXXXXXXXX'
$bucket = "MyBucket"
$keyPrefix = "install/"
$localPath = "D:\install\"

Import-Module AWSPowerShell
Set-AWSCredentials...

Is using online storage not an option?  For example Amazon's S3 is secure (providing you set it up correctly), it is also one of the most redundant online storage facilities...

Thanks for the reply,  yes I have been through the pain of doing this manually in prior versions, its still not perfect in 2016 / 2017 but a marked improvement.

Turns out using the backup and restore method worked adding the database on the secondary using this method,  it would be good though if someone could confirm this is the...

One easy and free solution is to use a parameterised batch file (there are more elegant solutions), this is just a basic example.

Save the following as deploy.bat:

Sorry yes, this particular example is for SQL 2012, but the same works for SQL 2014.  We have been running this very setup for almost 2 years.  As I say...

Another workaround which avoids the use of developer edition and the licencing issues around that is as follows:

1. Install SQL Server 2014 Express edition on the host, this...