> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/3.1/guides/maintenance-tasks.md).

# Maintenance tasks

The StifleR Server(s) needs regular maintenance like any other critical infrastructure to function effectively and continuously. In this section you find an operations guide that the sysadmin or operations team can follow to maintain a StifleR Environment. The guide is divided in to daily, weekly, monthly, and quarterly operation tasks.

In general the tasks described in these documents should be implemented into whatever ticketing system that is being used, such as Service Now, Remedy or Zendesk.

## Daily Maintenance Tasks 

1. Verify that the nightly backup was successful 
2. Check free disk space on all volumes on the StifleR Server (s)
3. Review the StifleR Server Event log
4. Review the StifleR Resource Manager log (if implemented)

## Weekly Maintenance Tasks

1. Review all daily tasks
2. Review and disk space usage on the StifleR Server(s), and compare to previous week to see trends etc. 
3. Verify that networks haven’t changed (boundaries etc.) 

## Monthly Maintenance Tasks

To be added, but these are for preparing for upgrades, and to establish long term trends. Usually scheduled meetings with workplace managers and other team members.

## Quarterly to semi-annual Maintenance Tasks 

1. Review the security plan for any needed changes 
2. Change accounts and passwords if necessary according to your security plan 
3. Review the maintenance schedule for upgrades to the StifleR platform
4. Check StifleR performance to ensure changes have not been made that affect operations 
5. Review the disaster recovery plan for any needed changes 
6. Perform a site recovery according to the disaster recovery plan in a test lab 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/3.1/guides/maintenance-tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.