Again, it really
isn??™t intended to be a failover mechanism, but more of a data-protection technique. When
it comes to redirecting clients, you have a number of techniques at your disposal. I??™m only
going to discuss the ones most commonly used.
Change DSNs on Client Machines
One technique for redirecting clients to the new primary server is to change the Data
Source Names (DSNs) on all your client machines to point to what used to be the secondary
server. However, if you have Windows-based applications that use a local DSN, this is
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 166
not the technique to use. Changing local DSNs would require visiting every client
machine and updating that machine??™s DSN entry to point to the secondary server??”not
an efficient approach.
You could always deploy a registry update to make the change via Active Directory,
which would definitely increase the efficiency of the process. However, the users would
have to log off and back in in order for the Group Policy Object (GPO) to process the registry
update. Again, the approach isn??™t all that efficient.
Pages:
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325