The maximum size of the NetScaler MAS database depends on the system database model. It is not the same on all systems. If the size of your database exceeds the threshold, the database becomes inaccessible. If that happens, you can use the following procedures to connect to the file system, delete a few components, and make the database accessible. You can then perform recovery operations.
For a NetScaler MAS standalone deployment:
1. At the command prompt, type the following command:
2. Run the NetScaler MAS recovery script (python /mps/mas_recovery/mas_recovery.py).
The script prompts you to delete filesystem components.
3. Generate some space by deleting file system components, and then restart NetScaler MAS.
4. Wait for about twenty minutes for internal DB operations to complete after NetScaler MAS has started, and then run the script again.
5. You should now be able to connect to NetScaler MAS database. The script helps you delete some data from the database by prompting you to navigate from one component to another.
6. After deleting some data, restart NetScaler MAS.
When NetScaler MAS is up and running, it should work as expected.
For a NetScaler MAS high availability deployment:
1. Run the NetScaler MAS recovery script (python /mps/mas_recovery/mas_recovery.py) individually on node 1 and node 2, and delete only file-system components.
2. Restart both nodes.
3. Once the nodes are up, wait for about 30 minutes for internal database operations to complete.
The database should now be up on both nodes.
4. Reconfigure the high availability deployment as a standalone deployment.
5. Run the recovery script on node 1, respond to the prompts by choosing tables to delete, and restart NetScaler MAS.
6. Run the script on node 2, delete exactly the same tables that you deleted on node 1, and restart NetScaler MAS.
7. Let the two nodes run for at least 45 minutes, and then recreate the HA pair by running the deployment script (deployment_type.py) on each node.