0

The secondary server is very far from the primary server. The database size is too huge to copy over the internet. Physically copying the file to an external device and then taking it over to the secondary site, copying it back in a drive to the new server and then restore is also time consuming.

Is there a way to add the secondary server to the Always on configuration without having the need to restore the database first on the secondary server creating a blank database on secondary server to start sync?

PS Note: Secondary server configuration we need it to be read only.

Kasim Husaini
  • 392
  • 3
  • 14

1 Answers1

0

Is there a way to add the secondary server to the Always on configuration without having the need to restore the database first on the secondary server creating a blank database on secondary server to start sync? PS Note: Secondary server configuration we need it to be read only.

It's not clear what you're expecting as an answer.

Firstly, a secondary AG replica is always read only.

You can choose to add a database to an AG using Automatic Seeding, or you can add an existing database by backing up the database and its transaction log from the primary and manually restoring on the secondary.

You can only only join a database to an availability group where its last committed LSN is within the range of the current active log.

Either way, the database(s) you want to add to the AG will have the data copied to the secondary somehow, whether that's over the internet by using automatic seeding, manually copying backup files (the most reliable option in my experience) or by physical media.

Last time I checked, by magic was not an option! :-)

Stu
  • 30,392
  • 6
  • 14
  • 33
  • The connectivity between the two servers is slow. For Automatic Seeding option it may take more than a week to sync. Physically transferring backup is a bit difficult between the two sites but seems the only option available as of now. – Kasim Husaini Jul 28 '21 at 04:50