This efficiency enables Data Domain to protect up to Deduplicated data can be stored onsite for immediate restores and longerterm retention on disk.
The deduplicated data can also be replicated over the WAN to a remote site or a service provider site in the cloud for disaster recovery operations, eliminating the need for tape-based backups, or for consolidating tape backups to a central location.
Data Domain provides the capability to consolidate both backup and archive data on the same infrastructure allowing greater consolidation by eliminating silos of backup and archive storage and associated overhead.
Specifically, SISL leverages the continued advancement of CPU performance to continuously increase Data Domain system performance by minimizing disk accesses required to deduplicate data. SISL deduplicates data by identifying duplicate data segments in memory, which minimizes disk usage. Data Domain is designed as the storage of last resort — built to ensure you can reliably recover your data with confidence.
Inline write and read verification protects against and automatically recovers from data integrity issues during data ingest and retrieval. In addition, unlike other enterprise arrays or file systems, continuous fault detection and self-healing ensures data remains recoverable throughout its lifecycle on Data Domain.
End-to-end data verification reads data after it is written and compares it to what was sent to disk, proving that it is reachable through the file system to disk and that the data is not corrupted. Specifically, when the Data Domain Operating System receives a write request from backup software, it computes a checksum over the data. After analyzing the data for redundancy, it stores the new data segments and all of the checksums.
After all the data is written to disk, the Data Domain Operating System verifies that it can read the entire file from the disk platter and through the Data Domain, and that the checksums of the data read back match the checksums of the written data.
This confirms the data is correct and recoverable from every level of the system. Data Domain integrates easily with existing infrastructures and can be used seamlessly with leading backup and archiving applications. Integrating a Data Domain system into your environment does not require any change in process or infrastructure, so you can realize the value of deduplication quickly and efficiently.
The flexibility of DD OS enables Data Domain to be the only protection storage to simultaneously support backup and archive data. This enables Data Domain to reduce overall total cost of ownership TCO by sharing resources across backup and archive data. Data Domain cost-effectively protects archive data through integration with industryleading archiving applications including EMC SourceOne and Symantec Enterprise Vault. By consolidating to a common protection storage platform, you can eliminate silos of storage and associated overhead - including management, floor space, power and cooling.
With deduplication ratios of 10 — 30x, storage footprint is greatly reduced lowering overall TCO. DD OS also provides secure multi-tenancy, which enables large enterprises and service providers to deliver data protection as a service with Data Domain in a private or hybrid cloud.
Secure multi-tenancy allows for tenant self-service by allowing tenants visibility only to the resources they are privileged to and catering to their needs for monitoring their resources. Physical capacity measurement allows you to capture how much physical capacity is being consumed at a file, directory, MTree, tenant, or tenant-unit level. This serves as an effective mechanism for managing shared Data Domain protection storage capacity between individual departments or tenants.
As data lands on Data Domain, it can immediately begin replicating it to a disaster recovery site. DD OS replicates only unique compressed data across the network, requiring a fraction of the time, bandwidth and cost of traditional replication methods. With cross-site deduplication only unique data is transferred across any of the WAN segments.
For the highest level of security, data being replicated between Data Domain instances can be encrypted using the standard Secure Socket Layer SSL protocol. Data Domain provides flexible replication topologies including full system mirroring, bi-directional, many-to-one, one-to-many, and cascaded. In a many- to-one deployment, data from up to remote offices can be replicated to a single DD Data Domain is very simple to install and manage resulting in lower administrative and operational costs.
Initial configuration and updates can easily be made for multiple Data Domain systems, along with the monitoring of system states and operations.
If this command is run against a directory, then all files within that directory and all subdirectories have their retention locks removed. Mtree is in retention-lock compliance mode.
What happens if a retention locked file is attempted to be modified or removed? Is it possible to list all files which are retention locked? Is it possible to completely disable retention lock for an MTree after it is enabled? Once disabled, MTree list indicates that retention lock was used against the MTree but has since been disabled, that is: sysadmin dd mtree list Name Pre-Comp GiB Status Tenant-Unit Note: Once retention lock is disabled against an MTree:.
Support Wissensdatenbankartikel. Artikelnummer: Druck E-Mail English. Data Domain: Retention Lock RL frequently asked questions FAQ This article consists of an overview of Data Domain retention lock RL functionality and explains the differences between configuration and utilization of governance and compliance mode.
Zusammenfassung: This article consists of an overview of Data Domain retention lock RL functionality and explains the differences between configuration and utilization of governance and compliance mode.
Weniger anzeigen This article consists of an overview of Data Domain retention lock RL functionality and explains the differences between configuration and utilization of governance and compliance Weitere Informationen. Artikelinhalt Artikeleigenschaften Diesen Artikel bewerten. Artikelinhalt Symptome This article provides a concise overview of Data Domain Retention Lock functionality and answers to related 'frequently asked questions'.
This article provides a concise overview of Data Domain Retention Lock functionality and answers to related 'frequently asked questions'. What is retention lock? Retention lock is functionality which is used on Data Domain Restorers DDRs to prevent modification or deletion of certain sets of files for a predetermined period.
That is, retention locked files are read-only until their retention period expires. Retention lock functionality is available in two different flavors: Governance: The less strict of the two retention lock flavors that is locks against files can be reverted if necessary. Compliance: The stricter of the two flavors which adhere to several common regulatory standards. Each flavor of retention lock requires a separate license key.
Retention lock functionality is enabled on a per MTree basis. As a result, a single system can use both governance and compliance mode against separate MTrees. However, it must have separate governance and compliance licenses installed. Do not use Retention lock functionality against MTrees that are used to store Avamar data as this can prevent Avamar from functioning as expected.
Which data access protocols are supported with retention lock? The VTL protocol is only supported against MTrees using retention lock governance mode, but not with retention lock compliance mode. See the Data Domain Administration Guide to determine how to unlock retention locked tapes such that they can be written to. As of DDOS 5. When the data movement starts, all of the files that have not been modified for the specified threshold number of days are moved from the active tier to the archive tier.
Set a schedule for when the data movement should begin; for example, weekly, daily, specific days, and a time in hours and minutes. A file system clean is recommended after the data movement. De-select this option if you do not want the clean to occur.
Expand an Archive or Active Tier When a file system exists, you can expand an archive or active tier. In the Expand File System Capacity dialog box, you have the option of expanding either the active or archive tier.
Make your selection and click Next. In the Expand File System Capacity dialog box, select the size of the new archive unit. Click Configure. After the configuration completes, click Finish. Delete an Archive Unit Only empty archive units can be deleted. Disable the file system. Select the archive unit or units from the list. Click Delete to remove the archive unit. The Delete button is enabled only if the selected unit is empty. Expand an Archive Unit Only unsealed archive units can be expanded.
You can expand a file system by expanding an existing unit, or by adding new units. Note: Storage cannot be moved from the active tier to the archive tier after the file system has been created. Only unused enclosures can be added to the archive tier.
Select the archive unit from the list. Click Expand. The Expand button is disabled if the unit is sealed. The dialog box that displays shows the current archive unit size and allows you to select the size to expand the selected unit.
To expand an existing unit, select an estimated size to increase the unit from the menu and click Next. Once the file system is expanded, however, you cannot revert it to its original size.
To expand the file system using available non-configured storage, Click Configure. Ensure that the correct license is applied.
Go to System Settings and check the Feature list for the Archiver license. If enabled, disable file system encryption. This feature is not available with archive units configured. Select the Encryption tab. Click Disable. From the More Tasks menu, select Enable Archive. The Enable Archive menu option is available only if the file system has not already been configured for Extended Retention. If the file system is already enabled as a non-Extended Retention file system , you are prompted to disable it.
Click Disable to do so. After a file system is converted into an Extended Retention file system, the file system page is refreshed to include information about both tiers, and there is a new tab labeled Archive Units. Verify Space Usage summary that the compression statistics for the Active and Archive tiers. Verify that there is an Archive Units tab. Click the Options Edit button. See the DD OS 5. Pressing the Start button enables you to start the data movement. When the data movement is running, the Start button changes to a Stop button.
Pressing the Stop button stops the data movement. Disk Space Usage: This pane shows the total size, amount of space used, and amount of available space and combined totals for active and archive tiers. The amount of cleanable space is shown for a active tier. Compression: Shows the pre-compression and post-compression values that are currently used and those that have been written in the last 24 hours.
Also shows the global, local, and total compression reduction percentage factors. If the unit has been sealed, that is, no more data can be added, then the date that it was sealed is given.
There are two buttons: Delete for deleting units and Expand for adding storage to a unit. Click the diamond symbol to the right of a column heading to sort the order of the values in reverse. The compression options are none, lz, gz the default , and gzfast. Space Usage Tab You can select one of the three chart types to view space usage over time in MiB for the entire file system, or for an archive or active tier.
Select one of the duration values in the upper-right of the tab. The data is presented color-coded as pre-compression written blue , post-compression used red , and the compression factor black.
Consumption Tab The consumption graph displays the amount of post-compression storage used and the compression ratio over time, which enables you to view consumption trends. An option allows you to display the post-compression storage against total system capacity. Daily Written Tab Shows the amount of data written per day for a selected duration 7, 30, 60, or days.
Fourteen days is the default. To change the value, click Edit, enter the new value, and click OK. Upgrading from up to two major prior releases is supported. Otherwise, the process proceeds to upgrade the active tier and all available archive units, and puts the system into the state that the previous upgrade has not been verified to be complete.
This state is cleared by the file system after the file system is enabled and has verified that all archive units belonging to the file system have been upgraded. A subsequent upgrade is not permitted until this state is cleared. If an archive unit becomes available after the upgrade process has finished, the unit is automatically upgraded when it is plugged into the system, or at the next system start.
Any active tier or archive unit that is at a different version must not be connected to the new system controller until the replacement process is completed. Otherwise, the new system controller is upgraded to the version in the active tier and archive units. All visible active tier and archive units are attached to the new system controller. Otherwise, the registry in the archive unit with the most recently updated registry is installed in the new system controller.
You can use any of these methods to recover data. For more information, see the DD OS 5. The new source must be configured as a DD Extended Retention system with the same number or more archive units as are located at the destination. The file system must not be enabled on the new source until the archive units have been added to it and replication recovery has been initiated. Install the replication license on the new source.
Reset the authentication key on the destination. Reconfigure replication on both the new source and destination. Initiate recovery on the new source. The file system must not have been enabled on the new source before this step.
Check the replication status. The file system may not detect that an archive unit is lost until the file system restarts or tries to access data stored in the archive unit. The latter circumstance may trigger a file system restart. After the file system has detected that an archive unit is lost, it returns an error in response to requests for data stored in that unit. If the lost data cannot be recovered from a replica, Data Domain Support might be able to clean up the system by deleting the lost archive unit and any files that reside fully or partially in it.
Overall Recovery Strategy A system with DD Extended Retention is equipped with tools to address failures in different parts of the system. In a failure situation, perform recovery actions in the order listed below. Restore connection between the system controller and storage. If the system controller is lost, replace it with a new system controller.
If there is loss of data and a replica is available, try to recover the data from the replica. If a replica is not available, limit any loss of data by leveraging the fault isolation features of the DD Extended Retention through Data Domain Support. Reusing an Archive Unit If all of the files on an archive unit are no longer needed, deleting them makes the unit available for reuse. You can generate a file location report to make sure that the archive unit is indeed empty, delete the archive unit, then add it as a new archive unit.
0コメント