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 don't know about the other services, but for the main database service you can go into SQL Server Configuration Manager (start - all programs - microsoft sql server 2008 - configuration tools - sql server configuration manager) and change where the master database is located.

Right click SQL Server(MSSQLSERVER)[parens may be different for named instances] - properties. Go to the Advanced tab. In the startup parameters (make sure the service is off first), update it to where your master files are physically located, should look something like this for you:

> 
> -dE:\SQL\Databases\master.mdf;-ee:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG;-lE:\SQL\Databases\mastlog.ldf
> 
> 
> 

Once you've edited it to the correct locations hit apply and restart the service and see if it comes up.
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.