8000 Prepare for Server Transfer and Re-deployment · Issue #29 · pipelinelabo/DatalaiQ · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Prepare for Server Transfer and Re-deployment #29

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.

Sign up for GitHub

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

Jump to bottom
Open
u-stack opened this issue Aug 12, 2024 · 0 comments
Open

Prepare for Server Transfer and Re-deployment #29

u-stack opened this issue Aug 12, 2024 · 0 comments

Comments

@u-stack
Copy link
u-stack commented Aug 12, 2024

Ensure the stability and readiness of the Internal DatalaiQ and Internal TIDR servers for transfer and re-deployment due to instability issues with bHive.
Backup Verification: Confirm the successful backup of Internal DatalaiQ. Ensure all necessary data has been securely stored.
Perform any additional backups needed for Internal TIDR to prevent data loss during the transfer.
Server Stabilization: Assess the current status of both servers, especially bHive, to understand the extent of instability.
Implement temporary fixes, if possible, to keep the servers running until transfer is initiated.
Transfer Preparation: Prepare both servers for transfer by documenting all configurations, settings, and dependencies.
Identify and document any potential risks associated with the transfer process.
Cloud Provider Evaluation: Research and evaluate suitable cloud providers for re-deployment, focusing on reliability, compatibility, and cost-effectiveness.
Compile a recommendation report for management, outlining the best options.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@u-stack
0