Are the databases instance specific? Else you could: - have a master server that no customer box calls - copy new tracks to that - scan on this box - sync new tracks to slave servers - sync DB files to new servers in a temp directory - backup the old slave DB files to a temp file - shutdown / restart to insert new DB file per requirements - come back up with the new DB
If this could be made to work you could just have a brief blip in the middle of the night when your slaves re-start. Seems it may work if all of the paths are the same. Seems quite redundant to let all of the box's CPU's churn on the same task. -Chris On 11/12/05, bglad <[EMAIL PROTECTED]> wrote: > > thanks to all for the good thoughts. the one thing i didn't mention is > that the hotel's in a fairly remote location so reliability, simplicity > and remote admin are important. i lean towards dean's idea of a RAIS, > but i'll throw all this at the guys who're doing the networking etc and > see what fits > > one thing concerns me whatever the architecture - rescanning for new > music flogs the server... they'll want a 24/7 music service and to > frequently add the latest cds - is there any way to lessen the load of > rescans? > > thanks again > ben > > > -- > bglad > ------------------------------------------------------------------------ > bglad's Profile: http://forums.slimdevices.com/member.php?userid=1052 > View this thread: http://forums.slimdevices.com/showthread.php?t=18098 > > _______________________________________________ > Discuss mailing list > Discuss@lists.slimdevices.com > http://lists.slimdevices.com/lists/listinfo/discuss > _______________________________________________ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
