openreplay / openreplay/documentation
Documentation on best practices for running Veeam backups alongside OpenReplay
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 16
- Forks
- 23
- Avg merge
- 39m
- Merged PRs (30d)
- 3
Description
We currently use Veeam to back up our Linux servers on a nightly schedule. In most cases, this does not cause any problems for OpenReplay. However, we have seen a few instances where Veeam and OpenReplay compete for disk resources during the backup window, leading to disk pressure and, in some cases, a server crash.
Are there any OpenReplay side best practices or recommended configurations for running regular system backups with Veeam? We’d like to avoid resource conflicts during backups and eliminate the risk of these crashes occurring again.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing OpenReplay documentation for backup, disk usage, and Linux deployment guidance, then investigate the reported Veeam resource conflict and server crashes. Done means adding documented, OpenReplay-specific recommendations for running scheduled Veeam backups without disk pressure or crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100