Veritas InfoScale™ 8.0 Virtualization Guide - Linux
- Section I. Overview of Veritas InfoScale Solutions used in Linux virtualization
- Overview of supported products and technologies
- About Veritas InfoScale Solutions support for Linux virtualization environments
- About Kernel-based Virtual Machine (KVM) technology
- About the RHEV environment
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- Veritas InfoScale Solutions configuration options for the kernel-based virtual machines environment
- Installing and configuring Cluster Server in a kernel-based virtual machine (KVM) environment
- Configuring KVM resources
- Getting started with basic KVM
- Section III. Implementing Linux virtualization use cases
- Application visibility and device discovery
- Server consolidation
- Physical to virtual migration
- Simplified management
- Application availability using Cluster Server
- Virtual machine availability
- Virtual machine availability for live migration
- Virtual to virtual clustering in a Red Hat Enterprise Virtualization environment
- Virtual to virtual clustering in a Microsoft Hyper-V environment
- Virtual to virtual clustering in a Oracle Virtual Machine (OVM) environment
- Disaster recovery for virtual machines in the Red Hat Enterprise Virtualization environment
- Disaster recovery of volumes and file systems using Volume Replicator (VVR) and Veritas File Replicator (VFR)
- Multi-tier business service support
- Managing Docker containers with InfoScale Enterprise
- About the Cluster Server agents for Docker, Docker Daemon, and Docker Container
- Managing storage capacity for Docker containers
- Offline migration of Docker containers
- Disaster recovery of volumes and file systems in Docker environments
- Application visibility and device discovery
- Section IV. Reference
- Appendix A. Troubleshooting
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
Migrating Docker Daemons and Docker Containers
InfoScale Enterprise also addresses the use case related to migrating both the infrastructure and container data. In this scenario, you need to bring down the Docker Daemon and Docker Container on the primary node and bring them up on the secondary node.
While migrating containers, ensure that you stop the Docker Daemon and Docker Container on the primary node before you migrate them to the secondary node.
To configure the Docker Daemon and containers using SFCFS
- Create a shared disk group and volume and do mkfs.
# vxdg -s init dockdg disk1 disk2 disk3
# vxassist -g dockdg make vol7 10G
# mkfs -t vxfs /dev/vx/dsk/dockdg/vol7
- Mount the volume on each cluster node.
# mount -t vxfs -o cluster /dev/vx/dsk/dockdg/vol7 /docvol
Where docvol is the directory used by the Docker Daemon for Docker infrastructure.
- Configure Docker to start the Docker Daemon on newly created CFS mount point,
/docvol
.Note:
Docker stores all its data, metadata, containers on alloted CFS shares. Though this CFS share is visible on all cluster nodes, Docker Daemon should be started from only one node a time.
- To initialize the migration make sure Docker Daemon is stopped from the source node and CFS share is not being consumed by Docker Daemon.
# systemctl stop docker
- Start the Docker Daemon on target node by appending -g /docvol in the
OPTIONS
field in the/etc/sysconfig/docker
configuration file..# systemctl start docker
The Docker Daemon is initialized on the target node. After migration is complete, Docker containers will be in exited state. User may need to manually start the containers.
Note:
To configure Docker Containers with VCS, refer to the Cluster Server Agent for Docker Installation and Configuration Guide guide.