You'll have to reassign or seize the RID master role on a functioning domain controller. Microsoft says:
Do not seize the RID master role if you can transfer it instead.
Seizing the RID master is a drastic step that should be considered
only if the current operations master will never be available again.
For more information about transferring operations master roles, see
Related Topics.
So it sounds like you'll have to seize, but I'm going to include reassigning anyway because of the above text. (I've copied and pasted in case of link rot.)
To reassign:
- Open Active Directory Users and Computers.
- In the console tree, right-click Active Directory Users and Computers, and then click Connect to Domain Controller.
- In Enter the name of another domain controller, type the name of the domain controller you want to hold the RID master role.
- Or, click the domain controller in the list of available domain controllers.
- In the console tree, right-click Active Directory Users and Computers, point to All Tasks, and then click Operations Masters.
- Click the RID tab, and then click Change.
To seize:
- Open Command Prompt.
- Type:
ntdsutil
- At the ntdsutil command prompt, type:
roles
- At the fsmo maintenance command prompt, type:
connections
- At the server connections command prompt, type:
connect to serverDomainController
- At the server connections prompt, type:
quit
- At the fsmo maintenance command prompt, type:
seize RID master
Aside: You probably already realize this, so I apologize for rubbing it in, but it sounds like you need better backups. Please consider implementing something as soon as you resolve the current crisis. Windows Server Backup is free with your version of Windows.