CVS on AWS Flashcards
What is Cloud Manager?
Cloud Manager simplifies enterprise cloud storage management by providing cloud monitoring, administration and orchestration frontend for NetApp ONTAP storage systems on-premises and in the cloud. Enterprise-Class Management Platform That Keeps You in Control of Your Data No Matter Where It IsCentralized platform for viewing and managing your on-premise and cloud storage, supporting hybrid, multiple providers and multiple accounts. Empowers IT professionals to provide their internal and external users with optimized cloud storage services.
What does Cloud Manager do?
Centralized Management
Unify your siloed storage systems on a single-pane console. Control multiple NetApp ONTAP storage systems, on-premise and in the AWS and Azure cloud.
Simplified Provisioning
Empower IT professionals to meet business objectives with simple provisioning tools. Allocate optimized storage capacity for internal and external customers with automatic capacity scaling.
Data Fabric Enabler
Allows automation and orchestration of cloud storage operations with RESTful API support and integrations with other NetApp cloud managment systems.
Simple and Fast Migration to the Cloud
Streamline your migration to cloud storage using point-and-click without rewriting your applications. Cloud Manager automatically creates the necessary cloud infrastructure to meet your operational data storage requirements.
Orchestrate a Mix of Hardware and Virtual Storage Nodes
Connect disparate storage environments into a single seamless data fabric.On-premise ONTAPsMultiple Cloud Volumes ONTAPsMultiple cloud provider accounts
Allocating Storage for Internal Users
Easily assign storage capacities to various users in your organization (e.g. development teams) and define access roles to offload the storage administration and management effort.
Cost Savings Dashboard
Cloud Manager monitors and tracks your cloud resource utilitzation and cost. Get visibility into your real-time storage environment cost savings.
What is Snap Mirror?
SnapMirror is a feature of Data ONTAP that enables you to replicate data. SnapMirror enables you to replicate data from specified source volumes or qtrees to specified destination volumes or qtrees, respectively. You need a separate license to use SnapMirror.
You can use SnapMirror to replicate data within the same storage system or with different storage systems.
After the data is replicated to the destination storage system, you can access the data on the destination to perform the following actions:
You can provide users immediate access to mirrored data in case the source goes down.
You can restore the data to the source to recover from disaster, data corruption (qtrees only), or user error.
You can archive the data to tape.
You can balance resource loads.
You can back up or distribute the data to remote sites.
You can configure SnapMirror to operate in one of the following modes:
Asynchronous mode: SnapMirror replicates Snapshot copies to the destination at specified, regular intervals.
Synchronous mode: SnapMirror replicates data to the destination as soon as the data is written to the source volume.
Semi-synchronous mode: SnapMirror replication at the destination volume lags behind the source volume by 10 seconds. This mode is useful for balancing the need for synchronous mirroring with the performance benefit of asynchronous mirroring.
SnapMirror can be used with traditional volumes and FlexVol volumes.
How does SnapMirror work?
SnapMirror replicates data from a source volume or qtree to a partner destination volume or qtree, respectively, by using Snapshot copies. Before using SnapMirror to copy data, you need to establish a relationship between the source and the destination.
You can specify a SnapMirror source and destination relationship between volumes or qtrees by using one of the following options:
The /etc/snapmirror.conf file
The snapmirror.access option
The /etc/snapmirror.allow file
The SnapMirror feature performs the following operations:
Creates a Snapshot copy of the data on the source volume.
Copies it to the destination, which can be a read-only volume or qtree.
Updates the destination to reflect incremental changes on the source, as per the schedule you specify.
The result of this process is an online, read-only volume or qtree that contains the same data as the source at the time of the most recent update.
Each of the following replication methods consists of a pair of operations, one operation each at the source storage system and the destination storage system:
Volume SnapMirror replication
Qtree SnapMirror replication
SnapVault replication
If a storage system is the source for one replication and the destination for another replication, it uses two replication operations. Similarly, if a storage system is the source as well as the destination for the same replication, it uses two replication operations.
What is SnapVault
SnapVault is a disk-based storage backup feature of Data ONTAP. SnapVault enables data stored on multiple systems to be backed up to a central, secondary system quickly and efficiently as read-only Snapshot copies.
In the event of data loss or corruption on a system, backed-up data can be restored from the SnapVault secondary system with less downtime and uncertainty than is associated with conventional tape backup and restore operations.
The following terms are used to describe the SnapVault feature:
Primary system—a system whose data is to be backed up
Secondary system—a system to which data is backed up
Primary system qtree—a qtree on a primary system whose data is backed up to a secondary qtree on a secondary system
Secondary system qtree—a qtree on a secondary system to which data from a primary qtree on a primary system is backed up
Open systems platform—a server running AIX, Solaris, HP-UX, Red Hat Linux, SUSE Linux, or Windows, whose data can be backed up to a SnapVault secondary system
Open Systems SnapVault agent—a software agent that enables the system to back up its data to a SnapVault secondary system
SnapVault relationship—the backup relationship between a qtree on a primary system or a directory on an open systems primary platform and its corresponding secondary system qtree
SnapVault Snapshot copy—the backup images that SnapVault creates at intervals on its primary and secondary systems
SnapVault Snapshot copies capture the state of primary qtree data on each primary system. This data is transferred to secondary qtrees on the SnapVault secondary system. The secondary system creates and maintains versions of Snapshot copies of the combined data for long-term storage and possible restore operations.
SnapVault Snapshot basename—a name that you assign to a set of SnapVault Snapshot copies using the snapvault snap sched command. As incremental Snapshot copies for a set are taken and stored on both the primary and secondary systems, the system appends a number (0, 1, 2, 3, and so on) to the basenames to track the most recent and earlier Snapshot updates.
SnapVault baseline transfer—an initial complete backup of a primary storage qtree or an open systems platform directory to a corresponding qtree on the secondary system
SnapVault incremental transfer—a follow-up backup to the secondary system that contains only the changes to the primary storage data between the current and last transfer actions
