For the business:
* It's a real life test of what happens if an employee quits/resigns, with less impact (a team member will probably be able to reach them in an emergency).
* You can test your operational robustness (as mentioned by the parent comment).
* It exposes holes in processes and documentation that have been papered over by a human.
* The vacation may reveal tasks which can be delegated to others or not done at all (timeline depending, of course).
Here are my general thoughts on that: https://letterstoanewdeveloper.com/2021/09/13/always-be-repl...
tl;dr "...you should always be looking at ways to replace yourself. This will free you up to work on new tasks and learn new things."
Over time this made me really angry at the team. It really shut down my brain because I had so many things to juggle. I really wish I could have replaced myself. I wound up just leaving the team, I think they struggled for a while.
When you're on a team with someone who seems to know everything, some people are much less motivated to learn the system. Also, sometimes things just suck. Sometimes you just have a team of jaded short-timers about to leave. Sometimes you have a team of junior employees who can "make things work" but leave a trail of half baked decisions.
-Flavor text from Netrunner CCG (1996)