# Localized	02/22/2014 02:57 PM (GMT)	303:4.80.0411 	Dedup.psd1
# Localized	02/29/2012 05:58 AM (GMT)	303:4.80.0411 	Dedup.psd1
#
# Dedup BPA Localization File
#

ConvertFrom-StringData @'
###PSLOC - Start Localization

    # check role service installed
FeatureInstalled_Title=Manually scanning a role service that is not installed is unnecessary
FeatureInstalled_Problem=A scan was run for the Data Deduplication role service on a server that does not have the role service installed.
FeatureInstalled_Impact=The scan did not need to be run.
FeatureInstalled_Resolution=Scan only servers that have the Data Deduplication role service installed, or ignore this rule.
FeatureInstalled_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check volumes are enabled with Dedup if qualified
EnableDedup_Title=Enable Data Deduplication on large volumes that have minimal available disk space remaining
EnableDedup_Problem=Volumes {0} have minimal available disk space remaining.
EnableDedup_Impact=If the volumes become full, users or applications may be unable to create or modify files on the volumes.
EnableDedup_Resolution=Use Ddpeval.exe to check if Data Deduplication can free up sufficient disk space on the volume. If so, enable Data Deduplication on the volume using Server Manager. If not, allocate more disk space and extend the volume, move data, or delete data to free up space.
EnableDedup_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check at least one Throughput schedule is created
EnableThroughputSchedule_Title=Ensure Data Deduplication Optimization for throughput mode is enabled
EnableThroughputSchedule_Problem=Optimization is not enabled for throughput mode.
EnableThroughputSchedule_Impact=Data Deduplication may not have sufficient time to process data on the volume, leading to less space savings than expected.
EnableThroughputSchedule_Resolution=Enable throughput mode for Optimization.
EnableThroughputSchedule_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check at least one GarbageCollection schedule is created
EnableGarbageCollectionSchedule_Title=Ensure Deduplication Garbage Collection jobs are enabled
EnableGarbageCollectionSchedule_Problem=Garbage Collection jobs are not enabled.
EnableGarbageCollectionSchedule_Impact=Data Deduplication may not achieve maximum space savings as space freed up by deleted or modified files will not be reclaimed by Garbage Collection.
EnableGarbageCollectionSchedule_Resolution=Create a Garbage Collection job to run weekly or bi-weekly during server idle times.
EnableGarbageCollectionSchedule_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check at least one Scrubbing schedule is created
EnableScrubbingSchedule_Title=Ensure Deduplication Scrubbing jobs are scheduled
EnableScrubbingSchedule_Problem=Scrubbing jobs have not been scheduled.
EnableScrubbingSchedule_Impact=During Scrubbing, problems such as bad-sector or checksum-mismatch are reported. Detection and repair of such conditions may not occur if Scrubbing is not scheduled.
EnableScrubbingSchedule_Resolution=Create a Scrubbing job to run weekly during server idle times.
EnableScrubbingSchedule_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check all volumes optimization should keep up with the policy
OptimizationKeepUpWithPolicy_Title=Ensure Data Deduplication is keeping up with data
OptimizationKeepUpWithPolicy_Problem=Data Deduplication of volumes {0} is less than 75% complete.
OptimizationKeepUpWithPolicy_Impact=Maximum space savings are not being realized.
OptimizationKeepUpWithPolicy_Resolution=If Data Deduplication is used for the first time and initial optimization is still ongoing, no action is required. Otherwise, ensure you create a Data Deduplication schedule and provide time for the scheduled job to complete.
OptimizationKeepUpWithPolicy_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check all volumes saving should achieve a certain goal
VolumeNotSavingMuch_Title=Ensure Data Deduplication is applied to appropriate volumes and files
VolumeNotSavingMuch_Problem=Data Deduplication is not realizing appreciable space savings on volumes {0}
VolumeNotSavingMuch_Impact=If Data Deduplication is not realizing space savings on the volumes, the benefits of using it are limited.
VolumeNotSavingMuch_Resolution=Review which volumes and files are included for Data Deduplication and make applicable changes. Use the Ddpeval.exe tool to measure potential savings.
VolumeNotSavingMuch_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check all volumes should get scrubbed constantly
VolumeNotScrubbedForAWhile_Title=Verify Scrubbing is performed regularly on Data Deduplication volumes
VolumeNotScrubbedForAWhile_Problem=Scrubbing has not been performed for a month, failed, or was cancelled the last time it ran on volumes: {0}
VolumeNotScrubbedForAWhile_Impact=Scrubbing did not complete successfully for over a month. As a result, bad-sector or checksum-mismatch problems may not be reported and repair operations may not have occurred.
VolumeNotScrubbedForAWhile_Resolution=Create a Scrubbing job to run weekly during server idle times. If the last Scrubbing job did not complete successfully, review the event logs to determine cause of failure and re-run Scrubbing manually using Windows PowerShell.
VolumeNotScrubbedForAWhile_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check all volumes should get garbage collected constantly
VolumeNotGCedForAWhile_Title=Verify Garbage Collection is performed regularly on Data Deduplication volumes
VolumeNotGCedForAWhile_Problem=Garbage Collection has not been performed for a month, failed, or was cancelled the last time it ran on volumes: {0}
VolumeNotGCedForAWhile_Impact=Data deduplication Garbage Collection did not complete successfully for over a month. As a result, data deduplication cannot reclaim space referenced by deleted or modified files.
VolumeNotGCedForAWhile_Resolution=Create a Garbage Collection job to run weekly or bi-weekly during server idle times. If the last Garbage Collection job did not complete successfully, review the event logs to determine cause of failure and re-run Garbage Collection manually using Windows PowerShell.
VolumeNotGCedForAWhile_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check all volumes should not have byte level verification enabled
ByteLevelVerifyNotNeeded_Title=Check if byte-by-byte verification mode is enabled
ByteLevelVerifyNotNeeded_Problem=Byte-by-byte verification is enabled for optimization of volumes: {0}
ByteLevelVerifyNotNeeded_Impact=Optimization jobs will run slower and storage performance will decrease when byte-by-byte verification is enabled.
ByteLevelVerifyNotNeeded_Resolution=Data Deduplication is using a strong cryptographic hash to detect duplicate chunks. In most situations, this level of verification is not required. It is recommended to disable byte-by-byte verification.
ByteLevelVerifyNotNeeded_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


###PSLOC - End Localization
'@