I'm making a database design for Fuel Stations. i need insights from the experts.
There are some scenarios to implement :
using One SQL Server in one head office, and client pc(s) in every fuel stations to record fuel transaction...and every fuel station is connected by leased-line(dedicated line) to the head office. i can not recommend TCP/IP internet since the connection is lousy in indonesia. so every pc will insert, update, and delete directly to SQL Server in head office. quite heavy.
backup and disaster recovery methods :
1.1. using replication to another server in a location behind head office, just in case something happens in head office or natural disaster like tsunami and earthquake strikes. since it's heavily transaction based, i think of transactional replication.
1.2. beside replication i intend to use backup and restore, i think of complete backup every 2 weeks. and differential backup everyday...actually i'm interested in transaction log backup, but i'm not clear what transaction log backup is and the difference with differential backup ...
using 1 SQL Server in head office, and client pc(s) in every fuel stations to record fuel transaction...every fuel station has its own SQL Server to speed up transactions and is connected by leased-line(dedicated line) to the SQL Server in head office. so every pc in that fuel station will insert, update, and delete to SQL Server in that fuel station also.
then every midnight we'll do replication like no. 1.1. and backup like no. 1.2.
so dear friends all over the world, pls give advices based on your experience and smart brains...to form a best design...
3. BACKUP MEDIA.
Currently what is widely used backup media ? i need reliable, and cheap one since the data is huge.