Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
cloudappliance:database-troubleshooting [2024_01_12 18:16] stevencloudappliance:database-troubleshooting [2024_02_28 01:03] (current) – external edit 127.0.0.1
Line 3: Line 3:
 ##### last updated on: Feb 7, 2023 ##### last updated on: Feb 7, 2023
  
-This document covers troubleshooting of the MariaDB database server included with the Enterprise File Fabric appliance.+This document covers troubleshooting of the MariaDB database server included with the Access Anywhere appliance.
  
 There are two main deployment options: There are two main deployment options:
  
- * Local database - database running on same virtual machine as the File Fabric Engine. + * Local database - database running on same virtual machine as Access Anywhere Engine. 
- * Remote database - File Fabric Engine connecting to a database over a network.+ * Remote database - Access Anywhere Engine connecting to a database over a network.
  
 A remote database could be: A remote database could be:
  
- * An instance of the Enterprise File Fabric appliance configured to only run the bundled MariaDB database.+ * An instance of the Access Anywhere appliance configured to only run the bundled MariaDB database.
  * An installation of MariaDB or compatible database  * An installation of MariaDB or compatible database
  * An external database-as-a-service compatible with MariaDB  * An external database-as-a-service compatible with MariaDB
Line 25: Line 25:
 ## Version Compatibility ## Version Compatibility
  
-The Enterprise File Fabric appliance includes a MariaDB 10.4 database server. +Access Anywhere appliance includes a MariaDB 10.4 database server. 
  
-Supported databases (as of Enterprise File Fabric 1705.00 through at least 1803.03)+Supported databases (as of Access Anywhere 1705.00 through at least 1803.03)
   * MariaDB 10.4   * MariaDB 10.4
  
Line 53: Line 53:
 ### Database Connection Settings ### Database Connection Settings
  
-To check what database an Enterprise File Fabric Engine is using look at the config.inc.php file.+To check what database an Access Anywhere Engine is using look at the config.inc.php file.
  
     grep '$db' /var/www/smestorage/public_html/config.inc.php     grep '$db' /var/www/smestorage/public_html/config.inc.php
Line 84: Line 84:
  
 ## Connecting across a Network ## Connecting across a Network
-For security the database included with Enterprise File Fabric cannot be connected to over a network. That is, it can only be accessed by processes running on the same machine.+For security the database included with Access Anywhere cannot be connected to over a network. That is, it can only be accessed by processes running on the same machine.
  
 This section covers settings that need to be changed for the database to be connected to from another machine. Please consult your IT or network administrator for other connectivity issues. This section covers settings that need to be changed for the database to be connected to from another machine. Please consult your IT or network administrator for other connectivity issues.
Line 90: Line 90:
 ### Verify Access to Port ### Verify Access to Port
  
-If the database is remote (the Enterprise File Fabric connects to the database over a network) verify network access from the server(s) hosting the Enterprise File Fabric Engine(s):+If the database is remote (Access Anywhere connects to the database over a network) verify network access from the server(s) hosting Access Anywhere Engine(s):
  
     curl hostname:3306     curl hostname:3306
Line 119: Line 119:
 Comment out **bind-address 127.0.0.1** which was telling mysql to only accept local connections. Adding a line with **::** allows incoming IPv4 and IPv6 connections. A setting of **0.0.0.0** can be used instead, which is also the default. It will allow IPv4 but not IPv6 connections: Comment out **bind-address 127.0.0.1** which was telling mysql to only accept local connections. Adding a line with **::** allows incoming IPv4 and IPv6 connections. A setting of **0.0.0.0** can be used instead, which is also the default. It will allow IPv4 but not IPv6 connections:
  
-    # SME managed file, do not edit directly!+    # NAA managed file, do not edit directly!
     [mysqld]     [mysqld]
     #bind-address = 127.0.0.1     #bind-address = 127.0.0.1
Line 160: Line 160:
 We typically recommend tools from the hypervisor or third-parties to backup the appliance and database. In some cases it’s helpful to use native tools. We typically recommend tools from the hypervisor or third-parties to backup the appliance and database. In some cases it’s helpful to use native tools.
  
-The File Fabric database is named **smestorage** and stores data in of InnoDB and MyISAM tables.+The Access Anywhere database is named **smestorage** and stores data in of InnoDB and MyISAM tables.
  
 For more information see https://mariadb.com/kb/en/library/backup-and-restore-overview/ For more information see https://mariadb.com/kb/en/library/backup-and-restore-overview/
Line 263: Line 263:
 ## Increasing Database Size ## Increasing Database Size
  
-Another way to deal with a full database is to allocate more space. The File Fabric database, by default, uses the local filesystem for storage. Allocating more space to the database involves increasing the space available on the filesystem. This is typically done by extending one of the disk partitions of the virtual machine.+Another way to deal with a full database is to allocate more space. The Access Anywhere database, by default, uses the local filesystem for storage. Allocating more space to the database involves increasing the space available on the filesystem. This is typically done by extending one of the disk partitions of the virtual machine.
  
 <WRAP center round important 100%> <WRAP center round important 100%>
Line 337: Line 337:
 ## Convert to GTID for v2006+ ## Convert to GTID for v2006+
  
-File Fabric HA/DR environments set up prior to v2006 did not leverage GTID for database replication. +Access Anywhere HA/DR environments set up prior to v2006 did not leverage GTID for database replication. 
 Starting with v2006 and greater, GTID is the recommended method for data migration.  Starting with v2006 and greater, GTID is the recommended method for data migration. 
  
 <WRAP center round important 100%> <WRAP center round important 100%>
-Warning: This work will bring down the File Fabric. As such you should run this only during a planned maintenance window. +Warning: This work will bring down Access Anywhere. As such you should run this only during a planned maintenance window. 
 </WRAP> </WRAP>
  
-### Enable GTID in the File Fabric appliances:+### Enable GTID in the Access Anywhere appliances:
  
 As the root user run the following on every database node: As the root user run the following on every database node: