이 페이지에서는 서버 다운타임이 필요한 베어메탈 솔루션 유지보수 이벤트의 프로세스에 대해 간략하게 설명합니다.
베어메탈 솔루션 환경의 안정성, 보안, 최신 상태를 유지할 수 있도록 Google Cloud 는 기본 베어메탈 솔루션 하드웨어와 인프라에서 예약된 유지보수를 수행하는 경우가 많습니다. Google은 서버가 실행되는 동안 많은 업데이트를 수행합니다. 그러나 일부 업데이트에는 다운타임이 필요합니다.
두 경우 모두 예약된 유지보수에 대해 알리고 유지보수를 준비하기 위해 어떠한 조치를 취해야 하는지 알려줍니다.
다음과 같은 이유로 예약된 기간에 유지보수를 실행하도록 허용하는 것이 좋습니다.
서버의 유지보수 알림을 받으면 서버가 성능 저하된 상태로 실행 중임을 의미하며, 원활하게 실행하고 예기치 않은 장애 및 다운타임이 발생할 위험을 줄이기 위해 가능한 한 빨리 해결해야 합니다.
정기적인 유지보수를 통해 장기간 서버를 계속 작동시킬 수 있습니다.
베어메탈 솔루션은 다음 두 가지 유형의 유지보수를 수행합니다.
인프라 유지보수: 데이터 센터에 있는 네트워킹 기기와 스토리지 구성요소의 유지보수를 포함합니다.
인프라 유지보수가 수행되면 Google에서 알려줍니다. 인프라 유지보수 알림은 정보 제공 목적이며 사용자가 응답할 필요가 없습니다.
서버 유지보수: 하드웨어 교체, 패치, 업그레이드, 구성 변경사항과 같은 서버 유지보수 활동이 포함됩니다.
서버에 영향을 주지 않는 유지보수 활동(예: 핫스왑 가능한 예비 전원 공급 장치 교체)의 경우 Google에서 응답하지 않아도 되는 정보 제공 목적의 알림을 보냅니다.
하지만 서버에 영향을 주고 다운타임(예: DIMM 교체)이 필요한 유지보수를 수행하려면 사용자의 허가가 필요합니다.
이러한 유지보수 활동에 관한 협력을 위해 유지보수 이벤트를 만듭니다. 유지보수 이벤트를 사용하면 유지보수 활동의 세부정보를 보고 유지보수 승인 또는 일정 변경과 같은 적절한 조치를 수행할 수 있습니다.
유지보수 작동 방법
유지보수에는 많은 계획과 조정이 필요합니다. 이는 양면적인 작업이며, 서버가 원활하게 작동하도록 Google과 사용자가 협력해야 합니다.
최소한의 지연으로 효율적으로 유지보수를 완료하려면 이 프로세스에 대해 읽고 이해하는 것이 좋습니다.
다음 플로우 차트는 베어메탈 솔루션 유지보수 프로세스와 관련된 단계를 보여줍니다.
다음 섹션에서는 각 단계를 자세히 설명합니다.
Google에서 유지보수 이벤트를 만듭니다.
서버의 유지보수 기한 2~3주 전에 유지보수 이벤트를 만드는 것이 가장 좋습니다. 이 이벤트를 사용하여 베어메탈 솔루션 환경의 중단을 방지하거나 최소화하기 위해 개발자와 협력하고 확인합니다. 이 이벤트에는 유지보수 활동에 관한 모든 세부정보와 유지보수를 준비하는 데 필요한 단계가 포함됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-19(UTC)"],[[["\u003cp\u003eBare Metal Solution requires occasional scheduled maintenance to ensure reliability, security, and up-to-date operations, which may involve server downtime.\u003c/p\u003e\n"],["\u003cp\u003eMaintenance is categorized into infrastructure maintenance, which is informational, and server maintenance, which may require user approval for downtime-inducing activities.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud creates a maintenance event two to three weeks in advance to coordinate with users, detailing the activity and required preparation steps.\u003c/p\u003e\n"],["\u003cp\u003eUsers can approve the proposed maintenance window, reschedule to a different time, or cancel if necessary, though cancellation is not recommended.\u003c/p\u003e\n"],["\u003cp\u003eUsers must complete the preparatory steps outlined in the maintenance event details before it begins, as failure to do so may lead to event cancellation and the server continuing in a degraded state.\u003c/p\u003e\n"]]],[],null,["# Bare Metal Solution maintenance\n===============================\n\nThis page provides an overview of the process for\nBare Metal Solution maintenance events that require server downtime.\n\nTo ensure that your Bare Metal Solution environment remains reliable, secure,\nand up-to-date, Google Cloud occasionally performs scheduled maintenance on the\nunderlying Bare Metal Solution hardware and infrastructure. We perform many\nupdates while your servers are running. However, some updates require downtime.\nIn either case, we notify you about the scheduled maintenance and alert you if\nyou need to take any actions to prepare for the maintenance.\n\nWe recommend that you allow the maintenance to be performed in the scheduled\nwindow for the following reasons:\n\n- If you receive a maintenance notification for your server, it means that your server is running in a degraded state and must be attended as soon as possible to keep it running well and reduce the risk of unexpected failure and downtime.\n- Regular maintenance helps keep your server functional over a long period of time.\n\nBare Metal Solution performs the following two types of maintenance:\n\n- **Infrastructure maintenance**---Includes the maintenance of the networking\n devices and storage components at the data center.\n\n We notify you when an infrastructure maintenance takes place. Infrastructure\n maintenance notifications are only informational and do not need you to\n respond.\n- **Server maintenance**---Includes server maintenance activities, such as\n hardware replacement, patches, upgrades, and configuration changes.\n\n For maintenance activities that do not impact your server (such as\n replacement of a hot-swappable and redundant power supply), we send you\n informational notifications to which you do not need to respond.\n\n However, to perform maintenance that affects your server and requires\n downtime (such as DIMM replacement), we need your permission.\n\n To collaborate with you on such a maintenance activity, we create a\n *maintenance event*. A maintenance event lets you view the details of a\n maintenance activity and take an appropriate action, such as approving or\n rescheduling the maintenance.\n\nHow maintenance works\n---------------------\n\nMaintenance takes a lot of planning and coordination. It's a two-sided operation\nand requires you and us to work together to keep your servers functioning well.\n\nTo complete maintenance efficiently with minimal delay, we recommend that you\nread about and understand this process.\n\nThe following flowchart shows the steps involved in the Bare Metal Solution\nmaintenance process:\n\nThe following sections describe each of the steps in detail.\n\n### Google creates a maintenance event\n\nIdeally, we create a maintenance event two to three weeks before your server is due for\nmaintenance. We use this event to coordinate and confirm with you to prevent or\nminimize disruption to your Bare Metal Solution environment. The event contains all the\ndetails about the maintenance activity and steps you need to take to prepare for\nthe maintenance.\n| **Note:** If we need to perform an urgent maintenance activity on your server, you might receive less than three weeks notice from us.\n\nYou can\n[view your maintenance events](/bare-metal/docs/manage-maintenance-events#view-maintenance-event)\nin the Google Cloud console.\n\nWe send you reminders about your upcoming maintenance events seven days, three\ndays, and one day before the maintenance event with preparatory steps for the\nevent to be successful.\n\n### User reviews the maintenance event\n\nWe recommend that you read the details and impact of the event carefully.\nAfter you've reviewed the maintenance event, you can take the following actions:\n\n- If you're okay with the proposed window, [approve the maintenance event](/bare-metal/docs/manage-maintenance-events#approve-maintenance-event).\n- If you're not okay with the proposed window, [reschedule the maintenance event](/bare-metal/docs/manage-maintenance-events#reschedule-maintenance-event) to propose a new window.\n\n| **Warning:** If you do not respond by five days before the scheduled start date, we might need to cancel or reschedule the maintenance event.\n\nAfter we receive your response, we schedule your maintenance event.\n\nWe do not recommend canceling a maintenance event. But, if you still need to\ncancel a maintenance event due to business-critical reasons, see\n[Cancel a maintenance event](/bare-metal/docs/manage-maintenance-events#cancel-maintenance-event).\n\n### User prepares for the maintenance event\n\nYou must complete the preparation as explained in\n[Prepare for a maintenance event](/bare-metal/docs/prepare-for-maintenance)\nbefore the maintenance event starts.\n\nYou must also complete any additional steps explained in your maintenance event.\n| **Warning:** Failure to complete the preparatory steps before the maintenance event starts can result in the cancellation of the maintenance event. If we cancel your maintenance event, then your server keeps running in a degraded state until its maintenance is done. Therefore, we recommend that you complete the preparatory steps.\n\n### Maintenance event takes place\n\nWe notify you when the maintenance event starts and when the maintenance event\nends. These notifications are informational and do not require you to\nrespond.\n\nIf the maintenance does not complete as planned, we reach out to you about the\nissues and next steps, including options to continue the maintenance event or\nrevert the server to its previous state.\n\nIf you are unreachable or unavailable to respond in time, we roll back the\nchanges and return the server to its previous state.\n\nWhat's next\n-----------\n\n- [Prepare for a maintenance event](/bare-metal/docs/prepare-for-maintenance).\n- [Manage your maintenance events](/bare-metal/docs/manage-maintenance-events#cancel-maintenance-event)."]]
