Couple things here...
first, there is no Unity 2.5... I assume you mean 3.1(5)?
Second, there's no way to do a "hot failback" onto an old Unity server should a migration go awry for some reason. All the users in the directory are associated with a phsical Unity server using the System ID of the local primary location object on that Unity server - these are unique for each server install - it's not done by server name.
Once you make the leap to 3.1 you've made the leap. Getting back to 2.4 basically involves manually reinstalling it again which is more work than just fixing the 3.x install.
That said, we haven't had too many "holy cow it's in flames and in the ditch" migrations from 2.x to 3.x that would mandate such a drastic "jump back" mechanism. If you follow the instructions for migrating you should be fine...