Question: I have a master slave setup using MySQL 5.0. 
I have very frequent writes to the master and slave is used only for backup purpose (no explicit writes).

In my current configuration, the slave database is synced with the master by MySQL automatically via VPN. But if the system (win 7) consisting of Master goes down for some reason, after reboot the synchronization doesn't continue from the last synced record. Instead I have to stop the services at both the ends, delete and recreate the config files, move the sql of the backup from master to slave and restart the sync. All this has to be done every time my system goes down for any reason. 

Is it possible to avoid this so that whenever master system goes down, the syncing starts again as usual ?

Answer: 
I assume you've restored entire partitions, but the partition drive letters are now wrong.

If SQL is looking for I: then you have three choices

a) Fix the drive letter of the partition that's now got the data. You said this is not an option. Is that because I: is already taken, or because something else is now looking for this data based on its new drive letter (E:)

b) Add an additional drive letter for the partition - nothing stops you referring to the same partition by more than one drive letter. This isn't an option if I: is already taken and you can't move that data from I:

c) Create a symbolic link on your new I: drive to point things back to what's now on E:. Start an elevated command prompt. Then type

```
I:
cd "\Program Files\"
mklink /d "Microsoft SQL Server" "E:\Program Files\Microsoft SQL Server"

```

If you already have a `Microsoft SQL Server` folder on your new I: then change the mklink command to make the `MSSQL.1` folder as the symlink rather than the `Microsoft SQL Server` folder.
At the very least, you need to change your drive letter back as in the original configuration. But if *reinstalled* (not *repaired*) Windows then you basically have a new machine and you must re-install SQL and everything else on it.