Recommended backup strategy for SQL Server

%3CLINGO-SUB%20id%3D%22lingo-sub-916502%22%20slang%3D%22en-US%22%3ERecommended%20backup%20strategy%20for%20SQL%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916502%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20would%20you%20advise%20or%20recommend%20as%20a%20backup%20strategy%20for%20customers%20using%20SQL%20Server%20hosted%20in%20the%20cloud%20(Azure%20VM's%20or%20AWS%20EC2).%20We%20have%20SQL%20Server%20Enterprise%20deployed%20in%20an%20AAG%20configuration.%20Currently%20we%20have%20weekly%20full%20backups%20on%20a%20Friday%20evening%20which%20are%20stored%20on%20a%20volume%20on%20a%20different%20server%20(domain%20controller%20-%20don't%20ask!).%20It%20does%20take%20a%20long%20time%20and%20doesn't%20seem%20to%20be%20an%20efficient%20way%20of%20backing%20up.%20Also%2C%20the%20primary%20SQL%20server%20is%20currently%20the%20active%20server%20for%20performing%20the%20backups%2C%20but%20would%20prefer%20this%20to%20be%20passed%20on%20to%20the%20secondary%20server%20-%20however%2C%20for%20some%20reason%20this%20was%20failing%20as%20it%20didn't%20support%20the%20backup%20method%20and%20required%20'copy%20only'%20backups%20-%20but%20don't%20fully%20understand%20this.%3CBR%20%2F%3EThe%20server%20also%20performs%20transaction%20log%20backups%20every%2015%20minutes.%3C%2FP%3E%3CP%3ECan%20you%20suggest%20anything%20else%20we%20can%20and%20should%20consider%20including%20the%20use%20of%20snapshots%20to%20ensure%20application%20consistency%20and%20ensure%20we%20can%20recover%20from%20failure%20without%20any%20data%20loss%20(or%20at%20least%20no%20more%20than%2015%20minutes).%3C%2FP%3E%3CP%3Ethanks%20%26amp%3B%20regards%2C%3CBR%20%2F%3EBaronne%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

What would you advise or recommend as a backup strategy for customers using SQL Server hosted in the cloud (Azure VM's or AWS EC2). We have SQL Server Enterprise deployed in an AAG configuration. Currently we have weekly full backups on a Friday evening which are stored on a volume on a different server (domain controller - don't ask!). It does take a long time and doesn't seem to be an efficient way of backing up. Also, the primary SQL server is currently the active server for performing the backups, but would prefer this to be passed on to the secondary server - however, for some reason this was failing as it didn't support the backup method and required 'copy only' backups - but don't fully understand this.
The server also performs transaction log backups every 15 minutes.

Can you suggest anything else we can and should consider including the use of snapshots to ensure application consistency and ensure we can recover from failure without any data loss (or at least no more than 15 minutes).

thanks & regards,
Baronne