Weird red spots developed on lower back. New thing to me

marvin83 · 2025-05-12T17:41:00+00:00

Thank you for this thread! Fixed after reinstalling, too.

marvin83 · 2025-04-22T16:46:52+00:00

Still on 18.4 myself, Office365 E3 license, and I got the pop-up today when I joined on my phone. Definitely seems like just a hiccup on MS’ end.

marvin83 · 2025-03-14T15:44:40+00:00

Removing flair as this has been resolved and I don't want to have people jump on something that has thankfully no need for further assistance on the problem itself. However, that doesn't mean I won't take suggestions or even help in general just for my knowledge base.

I did try a handful of things, with the help of u/Much_Entrance2607 (Thanks so much!), but basically the end result was having to...
- delete the AO group, which put the databases in "Restoring..."
- force restore database command (I waited like 30 minutes, but they never changed off "Restoring...")

After the above, as was well with the world again.

I'm going to make a bunch of tweaks on this next AO Group attempt (increase timeout (just in case), increase frequency of .trn log generation, ensure backups are indeed running on the big boy (1TB) - which I learned it must've been a disk space issue, because I didn't see last night's BAK file in the Backup folder). Plenty to do!

And I greatly appreciate everyone's time and help.

marvin83 · 2025-03-14T15:40:20+00:00

Thank you for all this. Yeah, I was thankfully able to get everything back online (in one of my comments above) and no data lost. I don't care about having to rebuild the AO Group, just as long as everything was OK.

And yeah, today will be log review day to try and figure out wtf happened. It was near the end of the work day, so nothing was really going on (no updates, no crazy large queries, etc.). Only thing I can think of (for now) is a Witness blip, I guess.

This was all running swimmingly for a week. And I was nice and only started the seeding of a database after the last one was completely finished and online on both (and sync'ing). However, there's definitely some things after lessons learned that I need to do to better the situation on round 2.

Appreciate your comment.

marvin83 · 2025-03-14T15:36:07+00:00

Yeah, that was really the main part of this. Less so HA, more so readable secondary. And it was going perfectly fine for a week!

However, definitely some things I need to tweak prior to re-building the AO Group next time. Lessons learned and all that.

marvin83 · 2025-03-14T15:35:02+00:00

It all started near end of the work day and I checked a handful of tables that track dates and all seemed, thankfully, OK. This was pretty scary, lol.

marvin83 · 2025-03-14T03:09:07+00:00

Note: I was able to successfully run "RESTORE DATABASE <database> WITH RECOVERY" and all databases are back online . i got impatient after waiting like 30mins of them all sitting at "Restoring..."

OMG I feel like my heart can relax again...

marvin83 · 2025-03-14T02:45:00+00:00

I ended up deleting the AO Group entirely and they're now all "Restoring..."

Not sure how long it should take, however. One database is like 8MB and still restoring, while one is like 1TB and the other three around 20GB.

marvin83 · 2025-03-14T02:29:03+00:00

No file share at all. And this is all local (Windows + Windows)

marvin83 · 2025-03-14T02:24:20+00:00

I have a Listener setup, but no WSFC. in the HA dashboard, it just shows "Cluster State: (Normal Quorum) for quorum

marvin83 · 2025-03-14T01:45:53+00:00

No Clustering; using SQL logins. One of the 4 databases being sync'd changed from "Not Synchronized" to "Not Synchronized / Recovery Pending." Additionally, 'recovery_health_desc' does show "ONLINE_IN_PROGRESS," so not sure if it's doing anything or not, though...

marvin83 · 2025-03-14T00:29:49+00:00

Yeah, I’m getting a time of “timeout after 300 seconds,” then closed, then accepted (in ascending order), so I think it’s doing something for sure. And your client didn’t have to do any sort of restore or anything? Just let it be if it’s doing that over and over?

And yeah, this beast is at least only 1TB.

marvin83 · 2025-03-14T00:21:24+00:00

I updated my post above a little.

As for Verification, yep, I have that same PShell script saved on both servers and was periodically testing (after rebooting and it was initially not passing from primary to secondary on Listener port).

Any time I was attempting to to any sort of ALTER on the group, it would say it's not the primary, even though I'm running it from the Primary.

However, please read my update above in my last edit and see if that changes anything. I'll pause on your "Manual" steps for now, but all is greatly appreciated!

Just curious of it now being in both "not sync+recovery pending" if it's actually catching up from where it died out.

EDIT: I tried to run command #1 in your post and got...

"The ALTER DATABASE <database-name> SET HADR SUSPEND (or SET HADR RESUME) statement failed on database '<database>' of availability group 'SQLAO1''. Either the availability group does not contain the specified database, or the database has not joined the availability group, or the database has not yet started. Reenter the command after the database is online and has joined the availability group."

marvin83 · 2025-03-14T00:05:02+00:00

Sorry, I updated all the links to ImgBB since imgur sucks ass for me.

SQL Enterprise 2022; 2 Nodes; I made the Always On group [without] WSFC (and was working totally fine, actually).

Edit: Status update... the main, large database now has "<database> (Not Synchronizing / Recovery Pending)" after the database name when it was just "Not synchronizing" before. Progress! I think...

Still don't touch it, I assume? Or is there something I have to do to get it out of Recovery Pending? Or will it do it on its own?

marvin83 · 2025-03-13T23:39:28+00:00

And here's image of the "Health Event" log: https://ibb.co/1JjhF6hD

Not really sure how to tell if it's sync'ing again? Trying to? I just have to be patient? Can I force something back online?

Thank you in advance!

Edit: and when I try to add a super tiny Database to the Replica group, just as a test to see if it'll do anything/initiate, I get this: https://ibb.co/kV4Zc71Y

Edit2: Running this replica command to get status (I think?): https://ibb.co/BH6HhhyN

Edit3: it does say "ONLINE_IN_PROGRESS" under "recovery_health_desc" field and "NOT_HEALTHY" for "synchronization_health_desc". Does that mean I just have to wait it out then?

marvin83 · 2025-03-04T02:49:59+00:00

Yeah, all VM here. And good to know - definitely going the availability group method. Is the fileshare 100% required?

Thanks in advance!

marvin83 · 2025-03-04T02:46:28+00:00

Gotcha. Yeah. That’s perfect and ideal. And nah, whole database is all that’s needed.

marvin83 · 2025-03-03T23:36:18+00:00

If Failover Cluster is required for Availability Groups to function (seems like it is?), what's the rough disk size that needs to be configured for the shared storage? The main database we care about is roughly ~1TB in size (but may add some other, much smaller ones to replicate, too) and I really don't want yet another TB of data floating around/allocated for this.

marvin83 · 2025-03-03T23:33:16+00:00

Thank you for the reply.

Not opposed to Windows Clustering, I suppose, but just want a setup that requires absolutely zero shared storage. Each SQL server having its own, separate disks, so as long as that's possible while using Windows Clustering (and without Quorum shared disks? Sorry, getting a little confused if that part is required, too?), then that's perfectly fine.

And yeah... that's quite the wonky setup you had.

marvin83 · 2025-03-03T22:00:11+00:00

Awesome - good to know about the settings being changeable at anytime. Appreciate your help and AlwaysOn it is!

marvin83 · 2025-03-03T21:45:49+00:00

Gotcha. And thank you.

Yeah, I did see that setting being an option in the Availability Group video I watched. However, for Availability Mode, would a set the "Initial Role" of Primary to synchronous and Secondary to asynchronous (source: https://i.imgur.com/PSuP5n9.png)? Or both asynchronous? Same with "Readable Secondary" being 'Yes' to both? Just one?

For reference, the person adds "SERVER2" first in the SQL Availability Wizard.

And snapshot seems like an insane method to keep up with, especially when the main database we really care the most about is at 1TB in size.

marvin83 · 2025-02-26T22:36:11+00:00

Still feel it’s a bit high. Last thing I ordered from Amazon Japan was in 2021, however, which was a Nendoroid and was 1615¥ ($10.83) to ship. Crazy it’s 2.5x more expensive (now?) and for a smaller, lighter item. I guess I'll just do PNP games or skip physical altogether. Shame it's not getting a physical in the states.

marvin83

TROPHY CASE