Bottom line: Decide how much backup space a client may consume and where a second protected copy must exist. Keep a working Time Machine destination separate from the evidence for that additional copy.
\nThe TrueNAS Time Machine guide says maintained macOS versions allow a maximum Time Machine backup size to be set through the macOS UI. It generally recommends managing that size on the client for flexibility rather than relying on the server-side limit. Its multi-user Time Machine configuration does not automatically replicate backup data to another pool or off-site location. The guide directs administrators who need that protection to configure a replication task for the dataset.
\nThis article covers the guide’s capacity and separate-copy decisions, not a guaranteed recovery point or restore time. It does not resolve version-specific multiprotocol coexistence notices or establish that a particular Mac has completed a recoverable backup.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE recommends a client-capacity worksheet with the intended maximum for each proposed test Mac and the shared destination’s approved capacity envelope. Have the data owner choose the retention and space requirements rather than copying a convenient example value. Confirm the actual client version and available setting before the pilot.
\nPut the second-copy requirement on a separate line in the backup design. Name its destination, owner and expected protection interval. Do not mark that line complete simply because the multi-user Time Machine share has been created or appears as an available destination on a client.
\nFor a proposed two-client case, identify a harmless backup set on each Mac and record each intended size limit. Review the separate replication configuration for the backing dataset through the applicable official workflow. Keep destination encryption, credential custody and off-site access decisions in their own supported recovery plan.
\nPreserve the initial share and client configuration before changing capacity settings. Ask the recovery operator to identify where the ordinary client backup and any separately maintained copy would be found. Leave a missing replica owner or destination unresolved rather than describing the system as fully protected.
\nProposed verification: inspect each selected client’s effective limit and perform an approved harmless backup. Record the client, chosen destination and observed completion separately. Compare the actual space observations with the worksheet without promising that a size limit determines a particular retention duration.
\nVerify the separately configured dataset copy against its own schedule and destination evidence. Rehearse an authorized recovery of a harmless marker from the required backup path, including the second copy where the plan calls for it. Keep client backup completion, replication completion and demonstrated file recovery as three distinct observations.
\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: Decide how much backup space a client may consume and where a second protected copy must exist. Keep a working Time Machine destination separate from the evidence for that additional copy.\nSource fact: what the authority says\nThe TrueNAS Time Machine guide says maintained macOS versions allow a maximum Time Machine backup size to be set through the macOS UI. It generally recommends managing that size on the client for flexibility rather than relying on the server-side limit. Its multi-user Time Machine configuration does not automatically replicate backup data to another pool or off-site location. The guide directs administrators who need that protection to configure a replication task for the dataset.\nWhat the source does not establish\nThis article covers the guide’s capacity and separate-copy decisions, not a guaranteed recovery point or restore time. It does not resolve version-specific multiprotocol coexistence notices or establish that a particular Mac has completed a recoverable backup.\nApplicability questions\n\nWhich Macs and data owners will use the destination?\nWhat client-side maximum and shared capacity budget are intended?\nIs another-pool or off-site protection required, and who configures it?\nWhat independent backup and restore evidence must the owner accept?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a client-capacity worksheet with the intended maximum for each proposed test Mac and the shared destination’s approved capacity envelope. Have the data owner choose the retention and space requirements rather than copying a convenient example value. Confirm the actual client version and available setting before the pilot.\nPut the second-copy requirement on a separate line in the backup design. Name its destination, owner and expected protection interval. Do not mark that line complete simply because the multi-user Time Machine share has been created or appears as an available destination on a client.\nFor a proposed two-client case, identify a harmless backup set on each Mac and record each intended size limit. Review the separate replication configuration for the backing dataset through the applicable official workflow. Keep destination encryption, credential custody and off-site access decisions in their own supported recovery plan.\nPreserve the initial share and client configuration before changing capacity settings. Ask the recovery operator to identify where the ordinary client backup and any separately maintained copy would be found. Leave a missing replica owner or destination unresolved rather than describing the system as fully protected.\nVerification and evidence\nProposed verification: inspect each selected client’s effective limit and perform an approved harmless backup. Record the client, chosen destination and observed completion separately. Compare the actual space observations with the worksheet without promising that a size limit determines a particular retention duration.\nVerify the separately configured dataset copy against its own schedule and destination evidence. Rehearse an authorized recovery of a harmless marker from the required backup path, including the second copy where the plan calls for it. Keep client backup completion, replication completion and demonstrated file recovery as three distinct observations.\nOfficial references\n\nTrueNAS — Adding a Basic Time Machine SMB Share — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Decide how much backup space a client may consume and where a second protected copy must exist. Keep a working Time Machine destination separate from the evidence for that additional copy.\n\n## Source fact: what the authority says\n\nThe [TrueNAS Time Machine guide](https://www.truenas.com/docs/scale/25.10/scaletutorials/shares/smb/setupbasictimemachinesmbshare/) says maintained macOS versions allow a maximum Time Machine backup size to be set through the macOS UI. It generally recommends managing that size on the client for flexibility rather than relying on the server-side limit. Its multi-user Time Machine configuration does not automatically replicate backup data to another pool or off-site location. The guide directs administrators who need that protection to configure a replication task for the dataset.\n\n## What the source does not establish\n\nThis article covers the guide’s capacity and separate-copy decisions, not a guaranteed recovery point or restore time. It does not resolve version-specific multiprotocol coexistence notices or establish that a particular Mac has completed a recoverable backup.\n\n## Applicability questions\n\n- Which Macs and data owners will use the destination?\n\n- What client-side maximum and shared capacity budget are intended?\n\n- Is another-pool or off-site protection required, and who configures it?\n\n- What independent backup and restore evidence must the owner accept?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends a client-capacity worksheet with the intended maximum for each proposed test Mac and the shared destination’s approved capacity envelope. Have the data owner choose the retention and space requirements rather than copying a convenient example value. Confirm the actual client version and available setting before the pilot.\n\nPut the second-copy requirement on a separate line in the backup design. Name its destination, owner and expected protection interval. Do not mark that line complete simply because the multi-user Time Machine share has been created or appears as an available destination on a client.\n\nFor a proposed two-client case, identify a harmless backup set on each Mac and record each intended size limit. Review the separate replication configuration for the backing dataset through the applicable official workflow. Keep destination encryption, credential custody and off-site access decisions in their own supported recovery plan.\n\nPreserve the initial share and client configuration before changing capacity settings. Ask the recovery operator to identify where the ordinary client backup and any separately maintained copy would be found. Leave a missing replica owner or destination unresolved rather than describing the system as fully protected.\n\n## Verification and evidence\n\nProposed verification: inspect each selected client’s effective limit and perform an approved harmless backup. Record the client, chosen destination and observed completion separately. Compare the actual space observations with the worksheet without promising that a size limit determines a particular retention duration.\n\nVerify the separately configured dataset copy against its own schedule and destination evidence. Rehearse an authorized recovery of a harmless marker from the required backup path, including the second copy where the plan calls for it. Keep client backup completion, replication completion and demonstrated file recovery as three distinct observations.\n\n## Official references\n\n- [TrueNAS — Adding a Basic Time Machine SMB Share](https://www.truenas.com/docs/scale/25.10/scaletutorials/shares/smb/setupbasictimemachinesmbshare/) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "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/plan-truenas-time-machine-capacity-and-separate-replica-protection/", "url": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Networks & Infrastructure", "item": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "@type": "ListItem", "position": 3, "name": "Plan TrueNAS Time Machine capacity and separate replica protection", "item": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/#article", "identifier": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/", "url": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/", "headline": "Plan TrueNAS Time Machine capacity and separate replica protection", "description": "The TrueNAS Time Machine guide recommends client-side backup-size limits and warns that a multi-user share does not automatically replicate backup data…", "abstract": "The TrueNAS Time Machine guide recommends client-side backup-size limits and warns that a multi-user share does not automatically replicate backup data to another pool or off-site location.", "articleBody": "Bottom line: Decide how much backup space a client may consume and where a second protected copy must exist. Keep a working Time Machine destination separate from the evidence for that additional copy.\nSource fact: what the authority says\nThe TrueNAS Time Machine guide says maintained macOS versions allow a maximum Time Machine backup size to be set through the macOS UI. It generally recommends managing that size on the client for flexibility rather than relying on the server-side limit. Its multi-user Time Machine configuration does not automatically replicate backup data to another pool or off-site location. The guide directs administrators who need that protection to configure a replication task for the dataset.\nWhat the source does not establish\nThis article covers the guide’s capacity and separate-copy decisions, not a guaranteed recovery point or restore time. It does not resolve version-specific multiprotocol coexistence notices or establish that a particular Mac has completed a recoverable backup.\nApplicability questions\n\nWhich Macs and data owners will use the destination?\nWhat client-side maximum and shared capacity budget are intended?\nIs another-pool or off-site protection required, and who configures it?\nWhat independent backup and restore evidence must the owner accept?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a client-capacity worksheet with the intended maximum for each proposed test Mac and the shared destination’s approved capacity envelope. Have the data owner choose the retention and space requirements rather than copying a convenient example value. Confirm the actual client version and available setting before the pilot.\nPut the second-copy requirement on a separate line in the backup design. Name its destination, owner and expected protection interval. Do not mark that line complete simply because the multi-user Time Machine share has been created or appears as an available destination on a client.\nFor a proposed two-client case, identify a harmless backup set on each Mac and record each intended size limit. Review the separate replication configuration for the backing dataset through the applicable official workflow. Keep destination encryption, credential custody and off-site access decisions in their own supported recovery plan.\nPreserve the initial share and client configuration before changing capacity settings. Ask the recovery operator to identify where the ordinary client backup and any separately maintained copy would be found. Leave a missing replica owner or destination unresolved rather than describing the system as fully protected.\nVerification and evidence\nProposed verification: inspect each selected client’s effective limit and perform an approved harmless backup. Record the client, chosen destination and observed completion separately. Compare the actual space observations with the worksheet without promising that a size limit determines a particular retention duration.\nVerify the separately configured dataset copy against its own schedule and destination evidence. Rehearse an authorized recovery of a harmless marker from the required backup path, including the second copy where the plan calls for it. Keep client backup completion, replication completion and demonstrated file recovery as three distinct observations.\nOfficial references\n\nTrueNAS — Adding a Basic Time Machine SMB Share — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-29T19:49:35+00:00", "dateModified": "2026-10-29T19:50:08+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/plan-truenas-time-machine-capacity-and-separate-replica-protection/" }, "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/plan-truenas-time-machine-capacity-and-separate-replica-protection/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Plan TrueNAS Time Machine capacity and separate replica protection" }, "articleSection": [ "Networks & Infrastructure" ], "keywords": [ "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 531, "timeRequired": "PT3M", "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": "TrueNAS — Adding a Basic Time Machine SMB Share", "url": "https://www.truenas.com/docs/scale/25.10/scaletutorials/shares/smb/setupbasictimemachinesmbshare/" } } ] } }