Uninstalling clients hosted on NEOSYS Server: Difference between revisions

From NEOSYS Technical Support Wiki
Jump to navigationJump to search
m (Comment out the installation from apache24/conf/neosys2.conf)
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 8: Line 8:
NEOSYS needs to:
NEOSYS needs to:


#Ensure that the installations can no longer be used by accident or design.
#Ensure that the databases can no longer be logged in to by accident or design.
#Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.
#Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.


Line 15: Line 15:
====Stage 1. Disabling====
====Stage 1. Disabling====


1. Ensure that the NEOSYS processes, for the installation that is being moved, have been shut down. This includes checking that no ntvdm process is running for the installation being moved, in procexp.exe (Find, Handle, D:)
1. Ensure that the services for the client being uninstalled have been stopped.
./doall <dbname> stop


2. Comment the lines pertaining to the stopped installation in D:/Apache24/conf/neosys2.conf
2. Delete the website
./doall <dbname> delete_site


3. Edit the process startup cmd file, which is scheduled to run daily in the task scheduler and comment out the stopped installation from it.
3. Disable the service, otherwise the services will start up every time ex1 reboots.
./doall <dbname> disable


4. Do not amend the client folder name or location, leave the client folder name as it is.
4. In doall, comment out the line corresponding to the client being uninstalled. Do this in dev as well and push the changes to neosys git.


The old procedure to Capitalise the client folder name or MOVING this folder to the "OLD" folder leads to backups doubling up on capacity on the backup server as the historical snapshots retain the old folders on the backup server. Hence, these procedures must be stopped.  
5. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh)


5. Retain a copy of the latest backup.zip file as mentioned in [[Backup_and_Restore#Historical.2FLapsed_Clients.3F| Handling backup for historical clients]]
6. Strike-through the terminated client's link on support home page (support.htm).


6. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh)
7. Create Thunderbird reminder to permanently delete the client 1 year later.


7. Strike-through the terminated client's link on support home page (support.htm).
====Stage 2. Permanent Deletion====
 
We keep ex client data for up to one year before deleting, but after this period:
 
1. Retain a copy of the client's latest backup sql.gz file in a separate directory (in ex1:/backups/current/deleted as of 3/4/2023)


====Stage 2. Permanent Deletion====
2. Delete the database and service
sudo -u postgres dropdb <dbname>
sudo -u postgres dropdb <dbname_test>
./doall <dbname> delete_service


Any installation found in the hosts\OLD folder which is older than one year may be deleted to free up storage and backup resources as follows:
3. Delete client directory from /root/hosts directory.
rm -r ~/hosts/<dbname>


1. Delete the associated web in IIS (for old clients).
4. Remove the terminated client's link from support home page (support.htm).


2. Delete the associated folders in hosts folder.
5. Delete the associated entry from Zone Edit.


3. Remove the terminated client's link from support home page (support.htm).
6. In doall, delete the line corresponding to the client being uninstalled. Do this in dev as well and push the changes to neosys git.


4. Delete the associated entry from Zone Edit.
7. Delete the lines for the stopped installation in the Nagios config file (edit: genclients.sh).

Latest revision as of 05:54, 1 April 2024

This must be done in the following circumstances:

  1. Reinstallation on other servers
  2. Reinstallation on clients own server
  3. Termination of contract
  4. Any other reason

NEOSYS needs to:

  1. Ensure that the databases can no longer be logged in to by accident or design.
  2. Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.

Include admin@neosys.com when sending emails regarding this subject.

Stage 1. Disabling

1. Ensure that the services for the client being uninstalled have been stopped. 

./doall <dbname> stop

2. Delete the website 

./doall <dbname> delete_site

3. Disable the service, otherwise the services will start up every time ex1 reboots. 

./doall <dbname> disable

4. In doall, comment out the line corresponding to the client being uninstalled. Do this in dev as well and push the changes to neosys git.

5. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh)

6. Strike-through the terminated client's link on support home page (support.htm).

7. Create Thunderbird reminder to permanently delete the client 1 year later.

Stage 2. Permanent Deletion

We keep ex client data for up to one year before deleting, but after this period:

1. Retain a copy of the client's latest backup sql.gz file in a separate directory (in ex1:/backups/current/deleted as of 3/4/2023)

2. Delete the database and service 

sudo -u postgres dropdb <dbname>
sudo -u postgres dropdb <dbname_test>
./doall <dbname> delete_service

3. Delete client directory from /root/hosts directory. 

rm -r ~/hosts/<dbname>

4. Remove the terminated client's link from support home page (support.htm).

5. Delete the associated entry from Zone Edit.

6. In doall, delete the line corresponding to the client being uninstalled. Do this in dev as well and push the changes to neosys git.

7. Delete the lines for the stopped installation in the Nagios config file (edit: genclients.sh).

Retrieved from "https://techwiki.neosys.com/index.php?title=Uninstalling_clients_hosted_on_NEOSYS_Server&oldid=4040"