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 moves files found on the file system, but not in the database, 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.
Users cannot download files if they are missing from the database.
Before running the FilesDataIntegrityService.checkFiles command, create the target path_to_extra_filesDirectory
folder. This folder will be used to save unused files during the integrity check. Create the folder on the device from which you will run the command.
If you are running the command on Linux or AIX, ensure that you have correct write permissions enabled for the folder.
Parent topic: Backing up Files data
Starting the wsadmin client
Files administrative commands
- 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:
On Windows -- FilesDataIntegrityService.checkFiles("C:\path_to_extra_filesDirectory")
On AIX or Linux -- FilesDataIntegrityService.checkFiles("/opt/path_to_extra_filesDirectory")