{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "slug": "dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand", "url": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/" }, "title": "Reschedule deduplication jobs around measured workload demand", "summary": "When should a deduplication job schedule or resource allowance be changed?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:16:19+00:00", "modified_at": "2026-09-08T18:20:21+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 216, "potentially_affected": "Use this review for a workload already using deduplication.", "dse_recommendation": "Collect a representative timeline of application activity and deduplication work.", "primary_source": { "name": "Advanced Data Deduplication settings", "url": "https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/advanced-settings", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft says the default advanced settings should suit recommended deduplication workloads; changes mainly target other workload patterns. Schedules and resource allowances can be adjusted so jobs run during idle periods or use different resource amounts. Deduplication jobs are visible in Windows Task Scheduler, and dedicated PowerShell cmdlets expose, create, modify, and remove their schedules. Microsoft documentation.

\n

Applicability

\n

Use this review for a workload already using deduplication. Identify the jobs, current schedule, resource settings, and periods of application demand. Review the documented usage type before changing the default behavior.

\n

DSE recommendation

\n

Collect a representative timeline of application activity and deduplication work. Propose one specific schedule or resource change with a measurable objective. Have the workload owner confirm the intended idle window and identify any maintenance conflict. Retain the original settings and schedule an explicit review of the pilot, rather than leaving the change in place without evidence.

\n

Verification

\n

Compare job completion, resource observations, and application response before and after the approved change. Observe more than one scheduled run when the workload varies. Check that moving a job did not leave its intended work unfinished. Record the final schedule and the circumstances that would trigger another review, such as a changed backup or application cycle.

\n

Official references

\n

Microsoft Learn: Advanced Data Deduplication settings. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft says the default advanced settings should suit recommended deduplication workloads; changes mainly target other workload patterns. Schedules and resource allowances can be adjusted so jobs run during idle periods or use different resource amounts. Deduplication jobs are visible in Windows Task Scheduler, and dedicated PowerShell cmdlets expose, create, modify, and remove their schedules. Microsoft documentation.\nApplicability\nUse this review for a workload already using deduplication. Identify the jobs, current schedule, resource settings, and periods of application demand. Review the documented usage type before changing the default behavior.\nDSE recommendation\nCollect a representative timeline of application activity and deduplication work. Propose one specific schedule or resource change with a measurable objective. Have the workload owner confirm the intended idle window and identify any maintenance conflict. Retain the original settings and schedule an explicit review of the pilot, rather than leaving the change in place without evidence.\nVerification\nCompare job completion, resource observations, and application response before and after the approved change. Observe more than one scheduled run when the workload varies. Check that moving a job did not leave its intended work unfinished. Record the final schedule and the circumstances that would trigger another review, such as a changed backup or application cycle.\nOfficial references\nMicrosoft Learn: Advanced Data Deduplication settings. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft says the default advanced settings should suit recommended deduplication workloads; changes mainly target other workload patterns. Schedules and resource allowances can be adjusted so jobs run during idle periods or use different resource amounts. Deduplication jobs are visible in Windows Task Scheduler, and dedicated PowerShell cmdlets expose, create, modify, and remove their schedules. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/advanced-settings).\n\n## Applicability\n\nUse this review for a workload already using deduplication. Identify the jobs, current schedule, resource settings, and periods of application demand. Review the documented usage type before changing the default behavior.\n\n## DSE recommendation\n\nCollect a representative timeline of application activity and deduplication work. Propose one specific schedule or resource change with a measurable objective. Have the workload owner confirm the intended idle window and identify any maintenance conflict. Retain the original settings and schedule an explicit review of the pilot, rather than leaving the change in place without evidence.\n\n## Verification\n\nCompare job completion, resource observations, and application response before and after the approved change. Observe more than one scheduled run when the workload varies. Check that moving a job did not leave its intended work unfinished. Record the final schedule and the circumstances that would trigger another review, such as a changed backup or application cycle.\n\n## Official references\n\n[Microsoft Learn: Advanced Data Deduplication settings](https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/advanced-settings). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "url": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Reschedule deduplication jobs around measured workload demand", "item": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "url": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/", "headline": "Reschedule deduplication jobs around measured workload demand", "description": "When should a deduplication job schedule or resource allowance be changed?", "abstract": "When should a deduplication job schedule or resource allowance be changed?", "articleBody": "Source facts\nMicrosoft says the default advanced settings should suit recommended deduplication workloads; changes mainly target other workload patterns. Schedules and resource allowances can be adjusted so jobs run during idle periods or use different resource amounts. Deduplication jobs are visible in Windows Task Scheduler, and dedicated PowerShell cmdlets expose, create, modify, and remove their schedules. Microsoft documentation.\nApplicability\nUse this review for a workload already using deduplication. Identify the jobs, current schedule, resource settings, and periods of application demand. Review the documented usage type before changing the default behavior.\nDSE recommendation\nCollect a representative timeline of application activity and deduplication work. Propose one specific schedule or resource change with a measurable objective. Have the workload owner confirm the intended idle window and identify any maintenance conflict. Retain the original settings and schedule an explicit review of the pilot, rather than leaving the change in place without evidence.\nVerification\nCompare job completion, resource observations, and application response before and after the approved change. Observe more than one scheduled run when the workload varies. Check that moving a job did not leave its intended work unfinished. Record the final schedule and the circumstances that would trigger another review, such as a changed backup or application cycle.\nOfficial references\nMicrosoft Learn: Advanced Data Deduplication settings. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:19+00:00", "dateModified": "2026-09-08T18:20:21+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-052-reschedule-deduplication-jobs-around-measured-workload-demand/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Reschedule deduplication jobs around measured workload demand" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 216, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Advanced Data Deduplication settings", "url": "https://learn.microsoft.com/en-us/windows-server/storage/data-deduplication/advanced-settings" } } ] } }