BACKUP Errors for MariaDB Xpand

Overview

MariaDB Xpand supports a BACKUP statement. The statement can raise errors in certain circumstances.

When using the Xpand Storage Engine topology, the errors described here only apply when you connect to the Xpand nodes.

BACKUP Errors

  • Errors indicating that something is wrong with the BACKUP statement:

    • Bad Parameter.:"Backup..." is invalid

    • Bad parameter.: *.* is repeated in the list

    • Bad parameter.: DB "..." is included multiple times

    • Bad parameter.: "..." is included multiple times

    • Bad parameter.: nothing to back up!

    • Unrecognized backup url scheme: ...

    • syntax error: ...

  • Errors indicating you are trying to backup something that cannot be backed-up, or doesn't exist:

    • Generic Error: no user DB found

    • Bad parameter.: Hidden database '...' cannot be backed up

    • No such database: '...'

    • Not found: Object "..." does not exist

    • Not found: There are more than one "..."

    • Backup only supported for TABLES right now: ...

  • Errors indicating you are trying to backup something currently unavailable:

    • Representation is unavailable: ...

    • Generic Backup Error: Couldn't find baserep for ...

    • Generic Backup Error: Couldn't find columns for ...

  • Errors indicating that Xpand is unable to parse URL or connect to FTP server:

    • Bad backup URL: ...

  • Errors indicating that there is already a backup at that location:

    • Backup already exists in create: ...

  • Errors indicating file written to backup was shorter than it should have been

    • Upload of slice was truncated on remote host: ...

  • Errors indicating that the statement would not backup any data:

    • EXCLUDING *.* is invalid

  • Errors indicating an object is excluded more than once:

    • "..." is repeated in the EXCLUDING clause

Zlib Errors

  • Errors indicating internal buffering error:

    • Internal Error: Unexpected buffering stop

    • Internal Error: Unexpected stop

FTP Errors

  • Errors indicating bad internal usage of our FTP interface:

    • File not found

    • FTP Socket Closed

    • Invalid argument to API

    • Socket timeout while waiting for server response

    • Unexpected error response from server

    • Unexpected response to PASS command

    • Unexpected response to USER command

    • Unexpected temporary error response from server

SFTP Errors

  • Errors indicating that there is no process reading from the other end of a pipe:

    • A file that isn't a directory was specified when a directory is required

    • An attempt was made to modify something on a read-only file system

    • Bad file descriptor

    • Broken pipe

  • Error typically indicating that you are trying to delete a directory:

    • Directory not empty, where an empty directory was expected

  • Error indicating that an existing file was specified in a context where it only makes sense to specify a new file:

    • File exists

  • Error indicating that the write operation on a file failed because the disk is full:

    • No space left on device

  • Errors indicating that the system tried to use the device represented by the file you specified, and it couldn't find the device:

    • No such device or address

    • No such file or directory

    • Permission denied

    • SSH authentication failed

  • Error indicating that the SSH server closed the connection due to a timeout:

    • SSH timeout

  • Error indicating that you tried to transmit data over a socket, without first specifying a destination for the data:

    • The socket is not connected to anything

  • Error indicating a cycle of symbolic links:

    • Too many levels of symbolic links were encountered in looking up a file name

  • Error indicating something unexpected happened in the SSH protocol:

    • Unexpected SSH error