There are two types of system administrators:
those, who don't backup yet, and those, who do it already.

Old truths must be felt by every person.

There's one very-well known eternal verity - if you want to do something relativly complex, that involves a labor of a team, then you must build a team you can rely on.
It's pretty simple, and everyone agrees with that. It's hardly possible to find a person who would object.
And I wouldn't object either. But understanding - is one thing, and the feeling, that you fail a project because of you inability to gather a good team - is something completely different.

Not so long ago I felt pretty well that if manager doesn't know the team, if she is not sure that she can withstand any 'storm' with the team members, then she has no team.
Manager must not underestimate the risks that follow the cooperation with unknown or not enough known team - that's clear.

And by accepting these risks manager bets her reputation. Because it's obvious that the only person, responsible for the project failure, is the manager. It's impossible for manager to blame anyone else except her.

So, team matters and this risk must be valued along with any other risk, such as new and unknown technology, time shortage, small budget and so on.