Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New-DbaDbSnapshot: Support Basic Availability Group Secondaries #9631

Open
ReeceGoding opened this issue Mar 25, 2025 · 0 comments · May be fixed by #9632
Open

New-DbaDbSnapshot: Support Basic Availability Group Secondaries #9631

ReeceGoding opened this issue Mar 25, 2025 · 0 comments · May be fixed by #9632
Labels
feature triage required New issue that has not been reviewed by maintainers

Comments

@ReeceGoding
Copy link
Contributor

ReeceGoding commented Mar 25, 2025

Summarize Functionality

At present, there seems to be no support for Basic Availability Group secondaries from New-DbaDbSnapshot. T-SQL supports this whereas the failure given by New-DbaDbSnapshot today is very quiet.

Is there a command that is similiar or close to what you are looking for?

Yes

Technical Details

I believe that this is a very close duplicate of #5631 . A similar fix ought to work. However, I've hunted around our codebase and I've yet to see a way that we have to test if a database is a BAG secondary.

@ReeceGoding ReeceGoding added feature triage required New issue that has not been reviewed by maintainers labels Mar 25, 2025
@ReeceGoding ReeceGoding changed the title New-DbaDbSnapshot: Support Basic Availability Groups Secondaries New-DbaDbSnapshot: Support Basic Availability Group Secondaries Mar 25, 2025
ReeceGoding added a commit to ReeceGoding/dbatools that referenced this issue Mar 25, 2025
@ReeceGoding ReeceGoding linked a pull request Mar 25, 2025 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature triage required New issue that has not been reviewed by maintainers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant