--
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: http://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The first choice is wich lan:
Windows Server 20??
a linux server
But require new server with many upgrade ram & cpu
is possible also buy a cloud service like in italy www.cloud.it
Linux server+SAMBA
Hi Swapan,
if you simple whish something new, what to say against ...
... but let tell you that a P-III must not be the end for a classic NW Server.
I set up a 4.11 SFT ~ 4 years ago on 3GHz single core Intel Xeon machines, it
works well since 2 decades, but since them a bit faster. My payment was more
than hardware costs, so it should be ;)
A single NW4/5-server can take up to 4 GB Ram for dirty buffers, gigabit LAN
with (priceless cheap old) INTEL! server NICs, should make not any problem, drivers are there.
Needed NNClient i see [not tested myself] up to newest Windows versions.
Not for production use because there a server should be only a server, but in
my development environment i run such a stone age 4.11 NW Server with VMware
Player V4 'by the way' in a virtual machine. Sure, this is a somehow
difficult, tricky and not a trivial task to get it best in there, but IMHO
sure possible for NW5.
I layed the disk images for it on a SSD, so it full boot up in 30 seconds.
After long long tryouts i was even able to install a teamed pair of virtual
Intel Gigabit NIC - a wonder !
This should run on every modern machine, even independent of underlaying OS.
Generally imho NW will need brutal CPU rate, does not really benefit from
modern cpu technics, so you would have to look mostly for cpu
core speed (and highest performance disk!) - further maybe that the CPU supports like VMplayer this Intel-VTx technic.
The only thing which speaks against to stay a bit longer at NW: Linux clients.
They have a fundamental problem with record locking over IPX protocol. But
if a read careful, you only have windows clients.
And the other thing: you will hardly find remaining experts, who remember and
can help you in case of problems - even i myself never set up NW5. You will have to try it yourself, but the web is full of hints ...
Regards
Rolf
--
I've been running a linux/samba server for years with no problems. Clients are now XP/7 (were also 95/98 in the past).
The only problem is that .dbf files are accessible to users but since 1987 we had no problems... anyway, we may move to netio to get some more speed and hide files from users.
If your software needs massive data moves over the lan you may need to experiment with alternate lan cards since some on-board cards are not good enough.
I've no idea about linux/samba as of now. Branko has also suggested linux/samba as server. There must be linux/samba tools to create valid users and rights at server?!
you perhaps know what a directory on a local Windows machine is, given free for access by other Windows machines in network ?
Nothing else is Samba, only based on a most reliable Linux OS, free of all annoying registration procedures ...
I assume Linux with samba can be installed on pcs with latest config.
Somehow in our Novell setup the setup is same, mapped novell drive to access the data & index folders! Yes dbfs are accessible to users (thanks God that users do not enter into the accessible novell server's network drive, and happy with clicking the apps. icons on their desktops!
Apart from <R>ead and <W>rite, Netware know an additional <A>dd trustee for directories, which is also responsible for deleting files.
And a <C>hange attribute responsible for renaming.
And a <S>earch attribute: user (app) must know the exact filename to get file access, a DIR command/ explorer will not list the files.
It can be granulary adjusted, who belonging to which group is allowed where he can do what - f.e. not all are allowed of indexing databases (delete old/ create new [index] files).
So fine it can't be tuned with Samba, or i overlooked something.
They think its as easy as buying a new pc, without giving a thought to the compatibility issue
Nearly as easy it _could_ be.
Make a one-to-one! copy of the old disk to a new disk.
As convinced Linuxer i would do that with 'dd' or better 'dd_rescue' command, but there exists tools for windows. Be careful don't to copy the new blank over the old one ;).
This would be an overall good thing you can do to your old server, as old HDs' are ever the most critcal point.
Put this into the new machine. IDE drives will work, SATA i suppose to make trouble cause of missing drivers, classic SCSI from Adaptec should work, special RAID controllers is a topic for itself.
WHAT TYPE has the old server ?
I never need to try such a move to a multicore CPUs based machine, but experienced this working on the fastest single core Xeons (available up to 3600/ 3800 MHz).
An easy and good pre-test before any further test maybe a try to start DOS :-) from the hopefully available floppy drive.
Network driver may need to be adjusted, if the NIC card can't move with you (or much better: get for 5$ a new old stock/ used one as duplicate)
Strategy behind: don't disassemble the old server, even not when a new one runs. Save it as is as 'fallback'.
Network cards: i spoke of the prooven Intel Pro 1000 Server! series - available also for PCI express, excellent driver support ...
###
Francesco, any other important points at Samba to take care of ? - as only full disable opportunistic locking to ensure data integrity ?
Regards
Rolf
###
Francesco, any other important points at Samba to take care of ? - as only full disable opportunistic locking to ensure data integrity ?
Francesco, any other important points at Samba to take care of ? - as only full disable opportunistic locking to ensure data integrity ?
Not that I'm aware of.
Francesco, that's good to hear !
Anyway, I'd not use dd to copy drives since the original data is on a netware filesystem and I'm sure it is not good to have it in linux.
He can move files from a client machine, just drag&drop from old to new, or recursive xcopy.
I wrote about how to full replicate a Netware server (including SYS volume) to 'newer' hardware
- sure not about to copy Netware _data_ with dd to a Samba server, that makes no sense as AFAIR Linux can't access/ use directly a Netware partition.
I know that recent Netware is linux based but don't know his version.
You are right, same my thoughts that in a way this Netware is an Unix derivate (Linus wasn't old enough ;)
I mean to see this at typical named directories (ETC, SYSTEM ..) and some commands ...
Addendum to Swapan:
after DOS can errorfree boot from f.e. of a floppy on a new machine, it must see/ able to access HD drive C:
This is a quick and very base test to eventually go further with trying to build into the cloned HD.
Hi again, Swapan
Can members please guide me how we can manage/setup our Clipper/Harbour multi-user apps over the network (LAN) in the current hardware & software scenario?
Sexta-feira, 5 de Abril de 2013 13:43:08 UTC+1, SD escreveu:Can members please guide me how we can manage/setup our Clipper/Harbour multi-user apps over the network (LAN) in the current hardware & software scenario?
Hi SD,
May I share some experience:
A factory:
file server: a simple dual core machine 4Gb ram, running Linux CentOS 6 & Samba
BTW, does your server (at factory) and office computers accessing the server's dbfs are in the same premises (factory compound only).
Hi Swapan,
Go to www.opensuse.org and download the DVD ISO. Create a DVD.
Boot the PC with the DVD and follow installation - it is easy except if the disks already contain a recent MS s.o.
When you are asked for packages please check that samba is selected. If not asked don t worry go a head.
Setup the LAN card. When complete login and start yast2 (like contro label) program and update the system (like windows update).
I think there are hundreds of tutorials on the web.
--
Harbour Applications run on similar setup, just replacing Novell Server with a new PC with Windows Server
Dear Swapan,
I have Harbour/xHarbour applications installed on Win 2008 R2 64 bit server and client machines being 32 bit XP, 64 bit Win 8 etc… The entire setup has been working for the last 6 months without any hitch.
FYI All programs are compiled in 32 bit. The users and I have not noticed any drop in speed or any other issues in the above environment.
Go ahead and do it.
Warm regards,
Jayadev
--
Hi Swapan,
Of course there are issues :-).
But they are really the same old issues as in the last fifteen years,
with the oplocks, CachedOpenLimit and the other registry settings. And
the SMB2 issue was added along the way too. So for file sharing database
systems to work properly (Microsoft calls them "old database systems" in
their KB articles) the registry hacks to streamline the server for that
kind of use must be applied. They have been discussed several times in
this newsgroup, and they are described in many places on the web.
That said, I have no direct experience with WinServer 8 specifically. I
moved several years ago to NAS disks running some NIX variety with Samba
on top. I have had no problems with that. And they are cheap.
This thread seems to circle back to Samba like clockwork :-)
Regards,
Klas
Windows 8 server, linux with samba or whatever operating system you want to test/use I strongly suggest that you must have an administrator fluent with that S.O. to setup backups and handle all the initial configuration - and came from time to time to have a look and finally solve problems when they (will) happen.
DBFs have pros and cons. One con is that they must be accessible in a shared disk - it happened once in the far past the a user dragged the data directory inside another dir... everything stopped working...
This problem may be solved using netio or porting to other databases but you will lose some language power...
A pro is when users of my programs in the past copied the program + data on a notebook to go abroad, several times in a year, so that they could have a copy of the data, use the program, create statistics and new documents - they had to input in the main system when back to office but it worked.... Update was just a batch that copied a couple of directories. Porting to a sql database was deemed difficult...
Since 2 years they go abroad with the notebook but use a VPN (also via a satellite connection) to login to a virtual machine inside the main office lan and then they work on live data - reports and documents are sent to them or directly to clients via mail. No need to have a local copy of data on the notebook, no risk of having it taken by competitors if notebook stolen... now a porting to sql is more easy (or at least netio with some rpc calls to speed up long queries)...
Dear Swapan,
I have Harbour/xHarbour applications installed on Win 2008 R2 64 bit server and client machines being 32 bit XP, 64 bit Win 8 etc… The entire setup has been working for the last 6 months without any hitch.
FYI All programs are compiled in 32 bit. The users and I have not noticed any drop in speed or any other issues in the above environment.
Go ahead and do it.