Uninstalling clients hosted on NEOSYS Server: Difference between revisions
No edit summary |
|||
| Line 25: | Line 25: | ||
Capitalising the folder name instead of moving the folder will prevent the backups from doubling up while still allowing us to identify which clients are live and which ones are terminated. | Capitalising the folder name instead of moving the folder will prevent the backups from doubling up while still allowing us to identify which clients are live and which ones are terminated. | ||
5. | 5. Place 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 | ||
7. Strike-through the terminated client's link on support home page (support.htm). | |||
==== Stage 2. Permanent Deletion ==== | ==== Stage 2. Permanent Deletion ==== | ||
Revision as of 10:22, 8 June 2017
This must be done in the following circumstances:
- Reinstallation on other servers
- Reinstallation on clients own server
- Termination of contract
- Any other reason
NEOSYS needs to:
- Ensure that the installations can no longer be used 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
Stage 1. Disabling
1. Ensure that the NEOSYS processes, for the installation that is being moved, have been shutdown. This includes checking that no ntvdm process is running for the installation being moved, in procexp.exe (Find, Handle, D:)
2. Stop the associated web in IIS
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
4. Capitalise the client folder name. In Windows, capitalisation has no effect other than visual. This makes it possible to differentiate between active and terminated clients.
The old procedure of MOVING this folder to the "OLD" folder leads to backups doubling up on capacity. i.e. on the backup server, the terminated Client's folder will be present both in the old location (where all active client folders are) and the new location ("OLD" folder).
Capitalising the folder name instead of moving the folder will prevent the backups from doubling up while still allowing us to identify which clients are live and which ones are terminated.
5. Place a copy of the latest backup.zip file as mentioned in Handling backup for historical clients
6. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it
7. Strike-through the terminated client's link on support home page (support.htm).
Stage 2. Permanent Deletion
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:
1. Delete the associated web in IIS
2. Delete the associated folders in hosts\OLD folder
3. Remove the terminated client's link from support home page (support.htm).
