Firstly, forgive my poor question title. I couldn't think of the best way to summarise this.
Essentially I'm putting together some scenario based DR documentation, with this specific scenario being a SAN issue where we have lost disks which hold either log or data files.
I'm assuming that MASTER has been affected (ie. the drive where it's files exist isn't accessible) and SQL services won't therefore start.
My specific questions are as follows:
If I run a rebuild of sys databases via command prompt using the install media, am I able to specify an alternative drive for the files? My understanding is on a rebuild, the pre-existing default instance location is used, which in this scenario wouldn't be accessible.
Assuming I can get a copy of the mdf and ldf files (by restoring a backup to another instance, for example) is there a way to start SQL Server by pointing it to a different location for the MASTER database? Like a service parameter?
Now I know that it would be possible to mount a new disk with the same drive letter, but I'm looking for a way where I could safely bring the instance up sooner than that, given in a critical situation such as this, the datacenter may have a list of priorities as long as their arm and it could be several hours or worse before the new volume could be ready.