August 6, 2016 at 4:32 am
Hi,
I've got a situation where I need to re-set up Always On for a database. I just want to check my chain of thought due to the database being 100GB in size and being in use on the primary.
The Primary does a full backup at 00:00 each day and then hourly log backups. So what I was thinking was;
1. Take the full backup from Day 1 and restore it on to the secondary. I seem to remember due to copying between data centres this may take about 36 hours.
2. Meanwhile the primary will continue to take log backups every hour.
3. Once the secondary full restore has finished I can start to apply the logs from the primary to catch up, once caught up I can then set up the Always On for the database.
My questions are this;
1. Does the above make sense?
2. Whilst the secondary does the full backup restore (36 hours worth) the primary will want to do another full backup, am I best disabling this so I just have the logs to restore or will I (I think I will be able to) just skip it in the restore). so on the secondary I'd restore as follows;
1. Restore the full backup from Day 1.
2. Then restore all the log backups from Day 1 in order.
3. Skip over the full backup from Day 2 in order.
4. Restore all the log backups from Day 2.
I hope I've explained myself, feel free to ask if you need more info,
Thanks,
Nic
August 6, 2016 at 5:28 am
So I built a test for this which did the following;
1. Create a database
2. Insert 2 records into a table and take a full backup (FB1).
3. Insert 2 more records and do a log backup (LB1).
4. Insert 2 more records and do another log backup (LB2).
5. Insert 2 more records and then do a second full backup (FB2).
6. Insert 2 more records and do another log backup (LB3).
The I dropped the database and restored;
1. FB1
2. Then LB1
3. Then LB2
4. Then LB3
And LB3 applies without any problems.
Thanks,
Nic
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply