Bottom line: Write the maintenance expectation in the Proxmox Backup server’s time reference before entering a calendar expression. Keep the intended schedule, the operator’s local time and the actual observed job start as separate entries.
\nThe Proxmox Backup calendar reference says schedules use the server timezone and do not support a timezone field in the expression. For most tasks, proxmox-backup-proxy checks the job schedules every minute, even when an expression contains seconds. When the time part is omitted, the reference assigns midnight; omitted weekday or date parts include all corresponding days. Its example mon,wed,fri therefore describes those weekdays at midnight.
These syntax and evaluation rules do not promise an exact launch second, successful completion or a particular daylight-saving transition outcome. DSE does not transfer a schedule from another product merely because its format looks similar. Confirm the actual task and installed release before adopting the example.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE recommends a schedule worksheet with the saved expression, its plain-language server-local interpretation and the relevant operator-local interval. Have a second administrator expand every omitted field. For a proposed example using only weekday names, require the reviewer to state the implied time rather than supplying an intended daytime appointment from memory.
\nReview dependencies as separate tasks with their own observed completion requirements. Do not schedule a dependent operation around an assumed exact second merely because the first expression includes one. Identify who will investigate a missed or delayed job and what evidence distinguishes the configured schedule from a completed operation.
\nInclude the server timezone in change and recovery records, especially when moving the service or changing host settings. If seasonal clock behavior matters, obtain the applicable current guidance and rehearse the intended boundary in a safe test arrangement. Leave the outcome unresolved until observed rather than extending the calendar page into an unsupported clock-transition guarantee.
\nUse two proposed calendar cards in the review: one containing only the listed weekdays and one with an explicit daytime value. Ask the operator to expand both without looking at an appointment calendar. Resolve the difference before saving the production task expression.
\nProposed verification: choose a harmless supported test task and an approved schedule. Record the saved expression and server time reference, then observe actual start and completion events across several eligible checks. Compare those observations with the plain-language interpretation without treating one launch instant as a future timing promise.
\nInclude a proposed omitted-time example in a nonproduction review and have another operator identify its expected calendar points. Preserve timestamps with their time reference, task identifier, observed duration and any missed runs. Assess maintenance-window acceptance separately from mere expression validity. Recheck the worksheet after a server-timezone, task or scheduling implementation change.
\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: Write the maintenance expectation in the Proxmox Backup server’s time reference before entering a calendar expression. Keep the intended schedule, the operator’s local time and the actual observed job start as separate entries.\nSource fact: what the authority says\nThe Proxmox Backup calendar reference says schedules use the server timezone and do not support a timezone field in the expression. For most tasks, proxmox-backup-proxy checks the job schedules every minute, even when an expression contains seconds. When the time part is omitted, the reference assigns midnight; omitted weekday or date parts include all corresponding days. Its example mon,wed,fri therefore describes those weekdays at midnight.\nWhat the source does not establish\nThese syntax and evaluation rules do not promise an exact launch second, successful completion or a particular daylight-saving transition outcome. DSE does not transfer a schedule from another product merely because its format looks similar. Confirm the actual task and installed release before adopting the example.\nApplicability questions\n\nWhat timezone is configured on the actual backup server?\nWhat full expression is saved for the intended task, including omitted fields?\nWhat local staffing or workload interval must the maintenance fit?\nWhich observed start, completion or missed-run condition requires investigation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a schedule worksheet with the saved expression, its plain-language server-local interpretation and the relevant operator-local interval. Have a second administrator expand every omitted field. For a proposed example using only weekday names, require the reviewer to state the implied time rather than supplying an intended daytime appointment from memory.\nReview dependencies as separate tasks with their own observed completion requirements. Do not schedule a dependent operation around an assumed exact second merely because the first expression includes one. Identify who will investigate a missed or delayed job and what evidence distinguishes the configured schedule from a completed operation.\nInclude the server timezone in change and recovery records, especially when moving the service or changing host settings. If seasonal clock behavior matters, obtain the applicable current guidance and rehearse the intended boundary in a safe test arrangement. Leave the outcome unresolved until observed rather than extending the calendar page into an unsupported clock-transition guarantee.\nUse two proposed calendar cards in the review: one containing only the listed weekdays and one with an explicit daytime value. Ask the operator to expand both without looking at an appointment calendar. Resolve the difference before saving the production task expression.\nVerification and evidence\nProposed verification: choose a harmless supported test task and an approved schedule. Record the saved expression and server time reference, then observe actual start and completion events across several eligible checks. Compare those observations with the plain-language interpretation without treating one launch instant as a future timing promise.\nInclude a proposed omitted-time example in a nonproduction review and have another operator identify its expected calendar points. Preserve timestamps with their time reference, task identifier, observed duration and any missed runs. Assess maintenance-window acceptance separately from mere expression validity. Recheck the worksheet after a server-timezone, task or scheduling implementation change.\nOfficial references\n\nProxmox Backup Server — Calendar Events — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Write the maintenance expectation in the Proxmox Backup server’s time reference before entering a calendar expression. Keep the intended schedule, the operator’s local time and the actual observed job start as separate entries.\n\n## Source fact: what the authority says\n\nThe [Proxmox Backup calendar reference](https://pbs.proxmox.com/docs/calendarevents.html) says schedules use the server timezone and do not support a timezone field in the expression. For most tasks, proxmox-backup-proxy checks the job schedules every minute, even when an expression contains seconds. When the time part is omitted, the reference assigns midnight; omitted weekday or date parts include all corresponding days. Its example mon,wed,fri therefore describes those weekdays at midnight.\n\n## What the source does not establish\n\nThese syntax and evaluation rules do not promise an exact launch second, successful completion or a particular daylight-saving transition outcome. DSE does not transfer a schedule from another product merely because its format looks similar. Confirm the actual task and installed release before adopting the example.\n\n## Applicability questions\n\n- What timezone is configured on the actual backup server?\n\n- What full expression is saved for the intended task, including omitted fields?\n\n- What local staffing or workload interval must the maintenance fit?\n\n- Which observed start, completion or missed-run condition requires investigation?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends a schedule worksheet with the saved expression, its plain-language server-local interpretation and the relevant operator-local interval. Have a second administrator expand every omitted field. For a proposed example using only weekday names, require the reviewer to state the implied time rather than supplying an intended daytime appointment from memory.\n\nReview dependencies as separate tasks with their own observed completion requirements. Do not schedule a dependent operation around an assumed exact second merely because the first expression includes one. Identify who will investigate a missed or delayed job and what evidence distinguishes the configured schedule from a completed operation.\n\nInclude the server timezone in change and recovery records, especially when moving the service or changing host settings. If seasonal clock behavior matters, obtain the applicable current guidance and rehearse the intended boundary in a safe test arrangement. Leave the outcome unresolved until observed rather than extending the calendar page into an unsupported clock-transition guarantee.\n\nUse two proposed calendar cards in the review: one containing only the listed weekdays and one with an explicit daytime value. Ask the operator to expand both without looking at an appointment calendar. Resolve the difference before saving the production task expression.\n\n## Verification and evidence\n\nProposed verification: choose a harmless supported test task and an approved schedule. Record the saved expression and server time reference, then observe actual start and completion events across several eligible checks. Compare those observations with the plain-language interpretation without treating one launch instant as a future timing promise.\n\nInclude a proposed omitted-time example in a nonproduction review and have another operator identify its expected calendar points. Preserve timestamps with their time reference, task identifier, observed duration and any missed runs. Assess maintenance-window acceptance separately from mere expression validity. Recheck the worksheet after a server-timezone, task or scheduling implementation change.\n\n## Official references\n\n- [Proxmox Backup Server — Calendar Events](https://pbs.proxmox.com/docs/calendarevents.html) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 28, 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/read-proxmox-backup-calendar-jobs-in-server-time/", "url": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-28" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Read Proxmox Backup calendar jobs in server time", "item": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/#article", "identifier": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/", "url": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/", "headline": "Read Proxmox Backup calendar jobs in server time", "description": "Proxmox Backup calendar expressions use the server timezone and jobs are checked once per minute; do not infer second-precise starts from expression syntax.", "abstract": "Proxmox Backup calendar expressions use the server timezone and jobs are checked once per minute; do not infer second-precise starts from expression syntax.", "articleBody": "Bottom line: Write the maintenance expectation in the Proxmox Backup server’s time reference before entering a calendar expression. Keep the intended schedule, the operator’s local time and the actual observed job start as separate entries.\nSource fact: what the authority says\nThe Proxmox Backup calendar reference says schedules use the server timezone and do not support a timezone field in the expression. For most tasks, proxmox-backup-proxy checks the job schedules every minute, even when an expression contains seconds. When the time part is omitted, the reference assigns midnight; omitted weekday or date parts include all corresponding days. Its example mon,wed,fri therefore describes those weekdays at midnight.\nWhat the source does not establish\nThese syntax and evaluation rules do not promise an exact launch second, successful completion or a particular daylight-saving transition outcome. DSE does not transfer a schedule from another product merely because its format looks similar. Confirm the actual task and installed release before adopting the example.\nApplicability questions\n\nWhat timezone is configured on the actual backup server?\nWhat full expression is saved for the intended task, including omitted fields?\nWhat local staffing or workload interval must the maintenance fit?\nWhich observed start, completion or missed-run condition requires investigation?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a schedule worksheet with the saved expression, its plain-language server-local interpretation and the relevant operator-local interval. Have a second administrator expand every omitted field. For a proposed example using only weekday names, require the reviewer to state the implied time rather than supplying an intended daytime appointment from memory.\nReview dependencies as separate tasks with their own observed completion requirements. Do not schedule a dependent operation around an assumed exact second merely because the first expression includes one. Identify who will investigate a missed or delayed job and what evidence distinguishes the configured schedule from a completed operation.\nInclude the server timezone in change and recovery records, especially when moving the service or changing host settings. If seasonal clock behavior matters, obtain the applicable current guidance and rehearse the intended boundary in a safe test arrangement. Leave the outcome unresolved until observed rather than extending the calendar page into an unsupported clock-transition guarantee.\nUse two proposed calendar cards in the review: one containing only the listed weekdays and one with an explicit daytime value. Ask the operator to expand both without looking at an appointment calendar. Resolve the difference before saving the production task expression.\nVerification and evidence\nProposed verification: choose a harmless supported test task and an approved schedule. Record the saved expression and server time reference, then observe actual start and completion events across several eligible checks. Compare those observations with the plain-language interpretation without treating one launch instant as a future timing promise.\nInclude a proposed omitted-time example in a nonproduction review and have another operator identify its expected calendar points. Preserve timestamps with their time reference, task identifier, observed duration and any missed runs. Assess maintenance-window acceptance separately from mere expression validity. Recheck the worksheet after a server-timezone, task or scheduling implementation change.\nOfficial references\n\nProxmox Backup Server — Calendar Events — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-29T00:09:58+00:00", "dateModified": "2026-10-29T00:10:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/read-proxmox-backup-calendar-jobs-in-server-time/" }, "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/read-proxmox-backup-calendar-jobs-in-server-time/#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": "Read Proxmox Backup calendar jobs in server time" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Advisory 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": 550, "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": "Proxmox Backup Server — Calendar Events", "url": "https://pbs.proxmox.com/docs/calendarevents.html" } } ] } }