blob: ce9fdffc399ca8dddfba50678237b8026b01a656 [file] [log] [blame]
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///C:/Program%20Files%20(x86)/Publican/DocBook_DTD/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="primary-storage-outage-and-data-loss">
<title>Primary Storage Outage and Data Loss</title>
<para>When a primary storage outage occurs, all hosts in that cluster are rebooted. This ensures
that affected VMs running on the hypervisor are appropriately marked as stopped. Guests that are
marked for HA will be restarted as soon as practical when the primary storage comes back on
line. With NFS, the hypervisor may allow the virtual machines to continue running depending on
the nature of the issue. For example, an NFS hang will cause the guest VMs to be suspended until
storage connectivity is restored. Primary storage is not designed to be backed up. Individual
volumes in primary storage can be backed up using snapshots.</para>
<note>
<para>If there are multiple primary storage servers in a cluster and only one goes down, VMs
using a healthy primary storage will also be affected, because all hosts are rebooted.</para>
</note>
<para/>
</section>