RMS (or any POS) and data management

[jcasetnl]

Hello All,

I work for a company with about 10 retail locations and we are using Microsoft RMS as our point of sale app. Each store typically has one or two POS terminals. The SQL DB is currently stored on the POS machine and we do a nightly full backup to our main office over a biz DSL VPN link.

The backup fails far too often and my guess is that a hiccup over the VPN link is enough to cause the operation to crap out. I considered instead of backing up the db to a remote server to instead backup locally to the POS, zip, rename and then robocopy the data. However, I then have a bunch of scheduled task scripts floating around with very little error reporting ability. I also have to babysit the process far too much.

I'm wondering how others handle data management with or without RMS and their remote locations. Is it the kind of thing that simply requires an exceptionally high amount of attention or is their a solution to this problem?

Thanks in advance.

 

[markphsd]

Hey,

I know this is POS related, but this is also SQL server related.

You might want to research the SQL Server Administration group to see what is recommended. There should be a way to get over the hiccups and reconnect. Don't look at it as a POS process but a SQL Server / VPN process.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[DTSMAN]

With the sql databases being to big for disk we partition all our hard drives on terminals and servers. The server will backup to one of its unused partitions. Then a batch file zips it and copies it to an empty partition on one of the terminals. So now I have a backup copy of the server on the server and a copy on a terminal. The reason we use partitions is so that we can hold 7 days of backups before they start overwritting, because sometimes corruption can take a few days to show its ugly head.

Bo

Kentucky phone support-
"Mash the Kentrol key and hit scape."