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

Adding a Note: After the Final Migration to Flexible Server, the Source Single Server Will Be Shut Down, Rollback Will Not Be Possible, and Deletion Will Be Irreversible—Applicable to Server Recovery in this Document #37

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rarandiv
Copy link

Adding a note- After the final migration to Flexible Server, the source Single Server will be shut down, and rolling back from Flexible Server to Single Server will not be possible. Additionally, once the Single Server is deleted, it cannot be recovered. Which is applicable in this doc which refer to server recovery.

Adding a note- After the final migration to Flexible Server, the source Single Server will be shut down, and rolling back from Flexible Server to Single Server will not be possible. Additionally, once the Single Server is deleted, it cannot be recovered.
Which is applicable in this doc which refer to server recovery.
Copy link
Contributor

@rarandiv : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 10f10f2:

✅ Validation status: passed

File Status Preview URL Details
articles/postgresql/single-server/how-to-restore-dropped-server.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Sep 12, 2024

@code-sidd

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Sep 12, 2024
@rarandiv
Copy link
Author

Hi @Court72 , any update on this as well?

@Court72
Copy link
Contributor

Court72 commented Sep 24, 2024

I sent a Teams message to the author today.

@code-sidd
Copy link

#assign @varun-dhawan

@Court72
Copy link
Contributor

Court72 commented Sep 24, 2024

@kabharati, @varun-dhawan

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

@code-sidd code-sidd removed their assignment Sep 24, 2024
@kabharati
Copy link
Contributor

@shriram-muthukrishnan to confirm

Copy link

github-actions bot commented Oct 8, 2024

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Oct 8, 2024
@rarandiv
Copy link
Author

rarandiv commented Oct 8, 2024

@Court72 just checking to see an updates.

@github-actions github-actions bot removed the inactive This PR is inactive for more than 14 days label Oct 9, 2024
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants