on 04-23-2015 1:15 AM
I’m posting this on behalf of a one of our clients. He is concerned there is a bug in Advantage Database Server that could lead to loss of data.
They have about 18 software packages all running and accessing Advantage on the cloud.
The Terminal Server is 2012 R2
The Data Server is 2008 R2
The Advantage Database Server is 11.10.0.22
On Sunday the 12th, the administrator made a change to the network share Advantage was using to access the tables. He unshared the old drive ( 😧 ) and path then he shared the new drive ( G: ) and path both the new and the old share where the same name. Advantage was still running at the time the network share was changed.
After the network share change, Advantage was still opening and writing data to the old network share on ( 😧 ) and not the new network share on ( G: ). Advantage seemed to be unaware the share path had changed.
They ran for a week like this then on Saturday the 18th the data server was restarted to another issue our tech support was having. On Monday the 20th, it was determined that the data was reverted back to Thursday the 16th, thereby missing Friday’s work. One of the software’s data was reverted back to Monday the 13th.
It appears that the act of “downing” the server on Saturday the 19th caused the data loss discovered on the 20th as Advantage was now looking at a different place since the share names were changed on the 12th.
The client is thinking that the tables were being cached in the Advantage memory and didn’t have an opportunity to write the data to disk when the data server was downed.
Any help would be appreciated.
How was the old and the new drive mapped, did you map to the UNC path or IP address?
Was the old and the new share used via Server-Side-Aliases? Are you able to reproduce this issue again and use now the ARC to verify, where the files will be open? If yes, please open a support incident, make some screenshots and provide more information about your environment and settings, so we can work on this issue directly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
In the first view, it looks for me an issue with the Discovery Process.
Are you using an ADS.ini with Lan_IP/Port? If not, I would recommend to use this, to avoid Netbios issues. You can also use the Server-Side-Aliases to point the Server the right place of the files. This will also help to avoid such like behavior of the Discovery Process.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.