The message title says it all. I spent 4+ hours today on the phone with a client in a panic because nobody in their warehouse to could access Sage 100. They were having two ISVs install a minor enhancement. During this process the installation crashed - and hosed the providex data dictionary file in the \MAS90 folder.
For those of you unlucky to have experienced this the result is the Sage 100 splash screen appears then disappears.
And, nope, there was no "quick and dirty backup" made before the process was started.
And, Yes, we did go to IT (MSP) and they restored files from backup - which took 1.25 hours during which the owner was staring at all the warehouse workers sitting idle and not able to ship orders.
In this case the customer's \MAS90\ folder was 50 GB. That's really not convenient to quickly copy/paste to another area on the server. And when I move huge folders like this I'm always afraid that I'm going to cause an "out of disk space issue" either right away or in a day or two should I forget to remove the backup copy once the crisis is over.
Which started me thinking - does anyone have a list of critical files that could be backed up via a batch file that could be placed one level above \MAS90. This wouldn't be a guaranteed fix but having the most critical files copied via backup which might take under 2 minutes is a lot better than no backup.
For example, a batch file could xcopy key files without which you may have problems starting or using Sage 100:
\MAS90
Providex.kdf
Providex.ddf
Providex.dde
Providex.prm
Providex.auc
Providex.dcl
\MAS90\MAS_SYSTEM
*.M4T
\MAS90\SOA
*.SOA
\xx\custom ( the customizations folder - if existing - for each module )
What other files am I overlooking ( aside from the data files themself)?
------------------------------
Wayne Schulz
wayne@s-consult.comSchulz Consulting
(860) 516-8990
Connecticut
------------------------------