The appropriate way to restore backed-up Files data is to restore versions of file system data and database data that match. You can check integrity between database data (metadata) and file system data (binary) by running the FilesDataIntegrityService.checkFiles command.
Before you begin
To use administrative commands, you must use the wsadmin client. See Starting the wsadmin client
About this task
The FilesDataIntegrityService.checkFiles command outputs messages to the SystemOut.log
file. Any files found on the file system but not in the database are moved to a file path location you specify in the command. You might want to delete these extra files, or back them up if you think you might need them for a future Files backup.
The command also logs files that are in the database but missing from the file system. The log includes the location where the file should be, its type (such as media
), and its file_id. Users cannot download files if they are missing from the database. You can use the log information to find the missing files if possible, or restore an older backup on which the command will run successfully. Alternately, you can delete the rows that own the file ids from the database, but be aware that this data is then irretrievable. You can also leave the mismatch and have it fail when users attempt to download.
- Start the wsadmin client.
- Start the Files Jython script interpreter using the following command:
- Check the integrity of data in the database and file system directory with the following command:
Parent topic: Backing up Files data
Starting the wsadmin client
Files administrative commands