As we’ve released a number of versions of inFlow On-Premise, there can be a number of things preventing a successful restore of your data.
Error: “media family on device is incorrectly formed. sql server cannot process this media family.”
If you’re getting the above error message, it’s because you’ve restored a backup from a computer that has a newer version of SQL Server (this is the backend database used to store your data through inFlow). Please see the full instructions here for how to fix this.
Error: “This backup file could not be restored, since it was made using a newer version of inFlow.”
This error message means the installed inFlow program is an older version (e.g v3.0.8) but you’re trying to restore a backup that was made in a newer version (e.g v3.3). The only way to fix this is to update the program to match the version of the backup file. If you’re not sure what version, the backup file usually contains the version number, or you can go to the computer you created the backup from and check inFlow’s Main Menu > Options > About inFlow .
Other things to try
Here are some other things to try if you’re still failing to restore/backup:
Check the file type you are trying to restore
In previous versions, inFlow’s backup file format is .ifi . As of v3.3. (latest version), the backup file is now .ifz , as it contains some extra settings unique to v3.3 (integration settings with online stores). However, you will not be able to restore .ifz files to inFlow versions v3.2 or earlier. Check the file extension of your backup file and make sure you have the correct version of inFlow installed. To get the latest update, please go here.
Check that you have enough space to backup your data
If you try to backup your data to a specific folder/directory, you must ensure you have enough space to create the backup file. For example, if your database is 1GB and you’re trying to save it into your C:, your C: must have space to accommodate that 1GB file. TO check the space, right-click on the folder/directory and click Properties. You can see the “Used space” and “Free Space” here.
Try doing the backup/restore from the server computer
If you are in multi-user mode, please try it doing the backup or restore from the server computer. Sometimes, particularly for large databases, the backup will fail when going across a network. If you’re not sure which one is your server computer, check by going to the Main Menu > Options > Connection Settings. It will show the name of the computer you are connected to (which would be the server).
Try manually unzipping your backup file
Sometimes inFlow has trouble unzipping the backup file. Try these steps to manually unzip the file and extract the backup:
1. Make a copy of your backup file
2. On the backup file, rename the extension to .zip instead of .ifz. (e.g: “inFlowBackup.ifz” becomes “inFlowBackup.zip”
3. Click “Yes” to the warning
4. Right-click on the zip file and click “Extract all”
5. Wherever you extract it to, there should be an inFlow.ifi file that you can try restoring to .
MANUAL PROCEDURES (If you’re still unable to backup)
If none of the above steps worked, then please email us the contents of the log file in the Start Menu -> inFlow Inventory -> “Program Log” so we can look into the problem. In the meantime, you can also manually do a backup as follows:
Manual Backup Procedure
1. Click Start, type in “inFlow Utilities” without the quotes.
2. Click “Perform a database query.”
3. Copy the following lines:
BACKUP DATABASE inFlow TO DISK = N'C:\inFlow_backup.ifi' WITH FORMAT
and paste it into the database query box. Click “Execute”.
4. Check your C:\ to see that the backup is there.
If you do not see the “inFlow Utilities” option or the “Perform a Database Query” option, you may be on an older version of inFlow, or you may not be on the server computer. You can check your version number by going to Main Menu > Options > About inFlow , in the inFlow program. Please get in touch with support at email@example.com and your issue so we can send you alternate steps for the manual backup procedure, or update to v3.3 today.