Working over the reasonable hours can lead to productivity losses, as explained eg in Why We Have to Go Back to a 40-Hour Work Week to Keep Our Sanity:
...for most of the 20th century, the broad consensus among American business leaders was that working people more than 40 hours a week was stupid, wasteful, dangerous, and expensive — and the most telling sign of dangerously incompetent management to boot. ...every hour you work over 40 hours a week is making you less effective and productive over both the short and the long haul. And it may sound weird, but it’s true: the single easiest, fastest thing your company can do to boost its output and profits -- starting right now, today -- is to get everybody off the 55-hour-a-week treadmill, and back onto a 40-hour footing...
Above reasoning applies both to team members and to you yourself. Consider studying more information available on that and presenting it to your management, to set their expectations in line with standard business practices.
A prominent example worth referring in the context of software industry is here:
developers think working long hours is a sign of machismo, it really is stupidity.
Best startup I ever worked for had a solid testing framework, zero regressions, high code velocity.
Everyone worked 9-5, weekdays only. My wife was astonished to see me for dinner so regularly. If we ever had to pull long shifts, the company had a fresh team that was nowhere close to burnt out.
Of course it failed...NOT. You might have heard of the company, LinkedIn.
Any time you have worked long hours it is a sign of a broken process. Insist the process gets fixed before working the long hours.
I also "tested" this on myself: limiting self to about 40 hr / week and reasonable vacations indeed increased my productivity, compared to working overtime and skipping vacations.