Abotts Partners with singapore based tech giant to help migrate their public sector customer from Sybase to SQL server.
Abotts partners with NYPL to integrate with their partner libraries.
Upworks Inc partners with ABOTTS to build their Oracle Cloud Infrastructure (OCI) and migrate their custom applications to OCI.
Abotts Inc Partners with Gnorth consulting to deploy exadata and ODA for a large public sector customer.
Purpose:
This document describes the migration procedure to move an existing LAS Progress OpenEdge environment (Application Server and Database Server) to a new Production environment using an existing LAS backup.
1. Scope & Pre-requisites
Scope
- Migration of LAS Application and Database from old environment to new Production servers
- Covers App Server and DB Server setup
- Does not include functional or user acceptance testing
Pre-requisites
- Existing LAS environment (Old Prod / Dev)
- New Production App Server & DB Server provisioned
- Progress OpenEdge 12.2 installed
- lasadmin and progress users available
- Network connectivity between App and DB servers
- Sufficient disk space for /las
2. Take Backup from Old Environment
2.1 App Server Backup
- Source: Old Prod / Dev App Server
- Directory: /las
tar -cvf las_app_backup.tar /las
2.2 DB Server Backup
- Source: Old Prod / Dev DB Server
- Directory: /las
tar -cvf las_db_backup.tar /las
3. Transfer Backup to New Production Servers
3.1 Copy to New Prod App Server
scp -r /las/ deekshithpoojary@<NEW_PROD_APP_IP>:/home/deekshithpoojary/
3.2 Copy to New Prod DB Server
scp -r /las/ deekshithpoojary@<NEW_PROD_DB_IP>:/home/deekshithpoojary/
4. Restore LAS Folder on New Production Servers
On both App and DB servers:
cd /
tar -xvf las_app_backup.tar # on App Server
tar -xvf las_db_backup.tar # on DB Server
5. Application Server Migration Steps
5.1 Create DLC Soft Link
Create soft link inside progress folder
ln -s /path/progress/versions/dlc dlc
5.2 Permissions & Ownership
usermod -aG lasadmin progress
chmod -R 775 /las
chown -R lasadmin:lasadmin /las
5.3 Disable Replication & AI
proutil dbname -C disablesitereplication source
rfutil dbname -C aimage end
5.4 Truncate BI Files
proutil dbname -C truncate bi
5.5 Update DB Connectivity
- Update DB IP in site.cfg
- Ensure DB ports are present in /etc/services
- Can be copied from source system
6. Database Server Migration Steps
6.1 Create DLC Soft Link
Create soft link inside progress folder
ln -s /path/progress/versions/dlc dlc
6.2 Permissions & Ownership
usermod -aG lasadmin progress
chmod -R 775 /las
chown -R lasadmin:lasadmin /las
6.3 Remove Lock Files
cd /las/prod/db/db
rm -rf acc.lk annex.lk gfa.lk
6.4 Disable Replication & AI
proutil dbname -C disablesitereplication source
rfutil dbname -C aimage end
6.5 Truncate BI Files
proutil dbname -C truncate bi
6.6 Update DB IP & Services
- Update DB IP in site.cfg
- Verify /etc/services entries
7. Start LAS Services (Post-Migration)
Start Order
- Start Database services first
- Start Application services next
cd /las/prod/scripts
./startall
8. Post-Migration Validation
8.1 Application Access Validation
- Launch LAS client
- Login using lasuser
- Verify menus load correctly
- Confirm DB connectivity
9. Post-Migration Checks
- Ensure no .lk files exist after startup
- Verify databases are in multi-user mode
- Confirm replication remains disabled
- Validate batch jobs and background daemons