Skip to content

Update incident reporting process in Veeam restore doc #404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
VickieKarasic merged 1 commit into from
Nov 18, 2025
Merged

Update incident reporting process in Veeam restore doc #404

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion services/veeam_restore.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Virtual machines that have special tags in vSphere (they look like `LIB_<datacen
We used to keep a spreadsheet of [VMs on the Veeam backup list](https://princetonu.sharepoint.com/:x:/r/sites/library/systems/Shared%20Documents/Server%20Documentation/Backup/Library%20Veeam%20Backup%20Schedules.xlsx?d=wc6e6edba4e224c6bbb8f0a1067b98801&csf=1&web=1&e=0gJi8U) in Sharepoint. Now we have a template in Ansible Tower called View VEEAM Backup List that shows which VMs have which tags. The intention is to balance the load of backups across days of the week and between data centers.


* Open a new SN@P Incident
* Open a new Generic Request
* Assign to storage
* Give as much detail as possible as to where the files were located and when they were deleted

Expand Down