If JetBackup fails to restore account(s) with the error “Invalid file type” - the first step would be to reindex JetBackup to sync data between source and destination servers and check that this resolves the issue. You can do this by running the following command:JetBackup 4: /usr/bin/jetcli backup -vfR reindex
JetBackup 5: jetbackup5api -F reindexDestination -D "_id={DESTINATIONID}"
This error can also be caused when the backup was generated with a different JOB ID. If the Job ID is not registered on the server, the backup was likely generated on another server/destination/job.
NOTE: Jetbackup 4.0 and JetBackup 5.1 do not allow moving backups from one server to another by simply copying the backups only.
The JOB ID that generated the backup is hard-coded inside the backup, therefore it is identified as the path of the backup. When you run reindex, you are telling JetBackup that you have a backup job ID (example: 5c7c57d4e5eaff58ce16e052) and it generated those backups and would be the source of the problem.
Then, when the cleanup/restore process runs it will search for the backups at the "jetbackup_1_1_5c7c57d4e5eaff58ce16e052" directory, which doesn’t exist, therefore it will only do part of the task and will not be able to find the hard files.
To properly import backups from another destination/server/backup-job, you must copy the entire job folder (jetbackup_1_1_5c7c57d4e5eaff58ce16e052) to the Backup Directory of the destination. Then reindex the destination again. This way you are importing backups to the system and JetBackup will properly recognize them.
