Unacceptable startuptime software with databases on SS4000 as shared drive
I bought an SS4000 to prevent that i lose all my databases when the harddrive goes down, so far so good ... BUT Our software runs on a couple of computers (local) and each makes connection to another computer with a shared drive to get connected to the databases. If we don't use the SS4000 it takes 10 seconds to start our software If i put my databases on the SS4000 it takes 4.5 muinutes before my software runs ... unacceptable !!!
The databases we use Paradox 7.0 databases, Win XP SP2, latest firmware on the SS4000
Re: Unacceptable startuptime software with databases on...
@echo PLEASE WAIT, THIS MAY TAKE A MINUTE. @ECHO PREPARING ROUTE FOR USING INTEL ATTACHED STORAGE @ECHO MAY HAVE TO DO A MANUAL CLOSE AND DISCONNECT OF THE Z: DRIVE. devcon enable "PCI\VEN_14E4&DEV_167A" <== modify for you route delete 0.0.0.0 192.168.0.101 net use z: \\192.168.0.101\public storage /user:admin /persistent:yes
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
All laptops & desktops will support databases by different software groups, of which, Excel can be a database of its own, it just does not have the fancy fields as most others would. Sharing the database with other computers becomes tricky part.
SQL database Recovery Software remove errors from corrupted SQL server database and allow to recover your all database of SQL Server Recovery tool support with all the MS SQL server version and MS windows.
NOTE: It may be possible to remove the drive(s) and put them in another system and from that system using those drives as data only drives (not boot) to copy any files which are needed to be backed up.
I have done this a number of times (please note that I am talking about single desktop systems here), every time it has work like a charm. If the drives are IDE, you need to set one drive at a time (if more than one IDE) as the slave drive. Once the drives are correctly set, then proceed to start the system and copy your data to the media you want. If the drives are scsi, set them accordingly on another system and number them as slaves or non-boot in the scsi controller bios. Then copy from your slave or non-boot drive(s) to the media you want to put your data. If you are using a system with some configuration other than single drives...such as some kind of RAID. then you need other help.
I am not familiar with the specific model, but my guess is you can setup another separate logical vlume by using a RAID1 for the new disks. You will not be able to add the disks to the existing volume.
If there is no data, and the array supports it you can delete the existing volume and setup a RAID 5 instead, which will use all 4 disks, as long as they have the same capacity.
If you check their website, you will find: Upgrading from a previous version of the firmware (to version 1.4) is a “data destructive” process. it is strongly recommended that you first
backup your existing data to another system in your environment. It is
also recommended that you understand your current configuration of
users, groups and shares to be able to recreate this under the 1.4