How can we help?

Search our guides and tutorials, or browse the categories below.

Physical Server Pre-Transportation Checklist

Physical Server Pre-Transportation Checklist for managers using physical Server is both the verification work. Steps are sorted to advance the problem without growing and return it whenever necessary.

Menu names may vary according to the version used. Therefore, write the target on the screen, the service to be affected and the expected value after processing. Verify the hardware health, remote management and backup return plan before processing.

Before the process starts

  • Verify the name and type of service of the target account.
  • Note the current value with date information.
  • Do not test the current backup can be read.
  • Specify the contact person during maintenance.

Step by step app

  1. Determine the target of the transaction in writing the account to be affected and the existing configuration.
  2. Get up-to-date backup for return and verify that the backup can really be read.
  3. Simply apply the setting on the target service, at least by authorization and at low traffic time.
  4. Check that the change is permanent by re-reading the value that appears on the panel after recording.
  5. Test the app with a real transaction on both the management screen and on the user side.
  6. Review error logs and resource usage and get back in unexpected situation.

Verification and troubleshooting

The response code should be evaluated with time and content. For example, HTTP It should not be considered successful in the queue, which appears to be delivered to an empty page or 200 rotating, but the remaining message on the tail should not be accepted.

  • Does the content of the response carry the expected data?
  • Is the process time in normal range?
  • Is there a job waiting on the tail?

Safety and continuity notes

Temporary test files, open debug mode and wide allowlist records should not be forgotten after the transaction. Add clearly the removal of them to the final checklist.

Return to the final successful situation instead of adding new settings in the unforeseen situation. Check the records at the trading time and repeat the same test with one variable.

Frequently Asked Questions

When should I open support request?

Stop new trials if there is unopened error on logs, data integrity risk or access loss; ask for support with time stamp and masked evidence.

For similar content Physical Server Information Bank You can review the section.

Was this helpful?

Thanks for your feedback!

Still Need Help?

Our support team is here around the clock for anything you can't find above.