Digital Computing System
Information Technology (it)Implement a new InfiniBand Server Cluster? We have a non-blade, rack-mount solution. Migrate from NAS to a SAN network for mass storage? Change from Fibre Channel to iSCSI? We have a copper based CAT6 and Fiber Optics solution. Upgrade to Gigabit network with Cat6 cable? We have special RJ45 plugs, so that the larger wires can be pulled through the plug. Contact us for the solutions. Email us C/Assembly(TMS320 DSP,68000,80x86,8051,MPC832, 68HC12) Programming and Circuit Design Migrate Exchange 5.5 to Exchange 2003 Server:
An affordable and necessary disaster recovery plan (andrp): Backup plan: · Two identical servers are deployed. One is in production (EXDCS2), the other one is also on-line, but renamed to EXDCS1, IP: 192.168.23.6, All Exchange services stopped. · A rescue server is taken off-site. · DCS2 (Exchange server): Use the built-in Backup function to backup System State and Storage Store to K: (300GB) unattended. This backup is done 5AM every workday. File names are created automatically, such as “Small Business Server Backup (1).bkf”. Disk 0 and Disk1 of this server are configured as RAID 1, i.e. mirrored. · DCS1 (Recovery Server) has Exchange fully configured and tested. Its services have been stopped. A free download program “idem” is running. Idem would back up server DCS3 Shared folder at every 1 hours interval (1 hour, the value=400). It also backup DCS2 Exchange Storage store at the same interval. · DCS3 Backup: Unattended daily backup to D:. Shadow copy is created every 6 hours, starting 6AM every day. If files are modified, a shadow copy will be created. User can see the copied from local computer, right click the file name, select Properties, and click “previous version” tab. The files must be from server sys folder, not from local My Document folder to have the Shadow Copies. · Manual offline Backup is done once a month: need to stop mail service first, and then run Backup program. · Backup to DVD Restore Data:
· File Server Restore. Three options are available: from Shadow Copies (6 hours old), or from DCS1 (1 hour old), or from D (1 day old): · Main Email Server local restore: Run start/programs/Accessories/system tools/backup. Check restore, and specified restoring from K:/Backup/. · Network restore: copy all folders from Recovery server D:/Exchsrvr/ · Recovery Email Server: Turn off main server, and remove disk 2 (300GB). Install Disk 2 to DCS1. Change IP of EXDCS1 to 192.168.23.2, and rename computer to EXDCS2. Under Services, select Automatic, and start all Exchange services.
Disaster Recovery plan: · Scenario 1 : Boot disk failed, or file corrupted · Resolution 1: Break disk mirroring. Stop unattended backup program, and stop “idem” which is running on the recovery server. Switch cable for disk0 and disk1, and remove the bad disk. Insert the bootable SD module. Change BIOS to boot from E:. Downtime is about 4 hours. · Scenario 2: A file is corrupted. Windows or Exchanger services can not start. · Resolution 2: Stop all backup programs on both servers. On the main server, boot to recovery mode, if necessary, and copy the file from the backup server, or CD. Minimum loss of data. Downtime is about 1 hour. · Scenario 3: Server hardware, CPU, or main-board failure. · Resolution 3: Move disk 2 (K:) from main server to the recovery server. Activate Recovery server (see instruction on Restore section). Restore Storage Store from K: Connect Recover server online to receive mails. Estimated downtime: 4 hours. · Scenario 4: both servers are damaged beyond repair. · Resolution 4: Bring the rescue NT server from off-site location. Update user accounts and use in production immediately. Build new server and restore data folders from the DVD-ROM. Estimated downtime 4-24 hours.
Move MS Exchange 5.5 Server to a new computer Exchange Backup. Migrate MS Access, SQL, or Oracle database to Internet using
ASP/JSP, ADO, CDO, XML ·
Thin-client applications ·
Keep the existing database and save prior IT investments.
Simply sharing data with Internet users. ·
Add e-catalog, and
e-shopping to the database and make most of the existing resources. ·
A true low cost and effective e-commerce solution. ·
Require a public IP, and a web publishing server. ·
No more dedicated lease lines for remote users; no
additional client access license; ·
See a few Samples: Computer Doctor -> Help
Desk Database On-Line Shopping ->Inventory
Database and On-line Order |