The process of scanning an image already installed on a server and saving the data into an archive format.
An archived form of an image. A captured image is identified with a name assigned by DynaCenter.
A reusable packaged collection of files that is distributed by DynaCenter to a target server during the deploy process.
A packaged collection of files that must be converted into a component before DynaCenter can distribute it to target servers as part of the image deploy process.
Content files are supplemental files, scripts, patches, etc. that you deploy in a component to customize your deployed image.
Control files store attributes and metadata for component content files. DynaCenter creates
.info.xml when it builds a component and places these control files in the directory above the
root in the component directory.
Script run by DynaCenter to allow for special processing during the deploy process.
The process of moving a captured image from the image depot to a target server for provisioning.
An image that has been provisioned onto a server.
A server that has been provisioned with an image; a target server becomes a deployed server after the deploy task completes successfully.
In an Amazon environment, the subnet where the source server is being migrated to (for example, your production subnet).
A complete software image (OS, applications, data) that can be booted and run on a server.
Storage container for captured images. The depot must be routable to the MWS and to servers being managed by DynaCenter. There can be more than one depot.
The process of capturing an image of a source server and deploying that image to a target server.
Note: The DynaCenter migration operation significantly reduces the time to migrate a server by combining the capture and deploy operations into a single operation.
The Management Workstation (MWS) runs DynaCenter and in some configurations serves as a NAS for the image depot.
DynaCenter uses an ostype string to identify the operating system name, version, and platform. These strings follow a specific syntax with well-known values in certain positions to make parsing easier. The syntax is rigid and the full specifier includes many details. Partner-specific scripts might be needed to convert another notion of operating system and hardware platform to an ostype before it is passed to DynaCenter.
Settings that can be used to specify the storage to be captured for a server and that can replace the default configuration already in the image for deployment.
NAS-based storage location known to DynaCenter that holds metadata for images, files that are part of software components, and other data necessary for provisioning and manipulating images.
A physical or virtual server capable of running software images.
A server that is managed by DynaCenter for the purposes of capturing images.
Note: The terms source server and managed server are used interchangeably.
Any device that contains storage. Storage servers will typically be NAS or SAN devices that are large enough to store many captured images. The MWS functions as storage server that contains at least a repository of software components.
A server that is managed by DynaCenter for the purposes of deploying images.