The discussion on migrating from 6 to 7 often suggests to export the configuration, use netinstall, and then import the configuration.
Trying to prepare for this, I made a full export configuration with "/export file=anyname". It created a text file "anyname.src" which did not contain some configuration items, for example /users.
How do I know that this is the full configuration? It may be missing some additional items. Am I doing something wrong?

Hardware: RB922UAGS-5HPacD
RouterOS: 6.49.1

I forgot to mention that I tried "/export verbose file=anyname" without any luck.
The post you are referring to concerns sensitive information (like passwords). I am not even getting user names. And my question was more general. If /users is missing, how do I know if something else is not also missing?

Passwords are certainly missing, even not exported in encrypted form. Everywhere , even with verbose or terse.
Verbose includes the default values, and that's a long list. Some of those things can only be set through CLI.
Some modules are missing or have their own export method (user, port, certificate, ..... ?), and react also on verbose

/user export
/port export
/certificates export
/certificates export-certificate (???)

Extra packages like dude have their own config and database export.

This list may be far from complete.

And sometimes there are bugs .... like 6.47.10 not exporting the wireless frequencies.

The discussion on migrating from 6 to 7 often suggests to export the configuration, use netinstall, and then import the configuration.
Trying to prepare for this, I made a full export configuration with "/export file=anyname". It created a text file "anyname.src" which did not contain some configuration items, for example /users.
How do I know that this is the full configuration? It may be missing some additional items. Am I doing something wrong?

Hardware: RB922UAGS-5HPacD
RouterOS: 6.49.1

I'd recommend doing a backup before upgrade (Files>Backup) & making sure to download the backup file from device to desktop/mobile since the flash may get wiped on the device during the upgrade process. Still create and download the "export verbose file=x" config, but more as reference to compare with V7 config (in case something got converted wrong in your config from V6 -> V7). As long as you downgrade to the same version you made the backup file, that will restore all things includes users and certificates (and other things like logs).

Now if V7 doesn't work for you... Most of the time you downgrade by copying the 6.46.1 RouterOS file (.npk) from www.mikrotik.com/downloads to the root of your Mikrotik Files, and the System>Reboot. Netinstall is a more complete re-install (e.g. it re-formats a partition and copies all files again), but it generally not needed. Regardless how you got back 6.49.1, at the same version you'd upgraded from (6.49.1), you can restore the backup file (copy from desktop/mobile to Mikrotik device, the Files>Restore). The only issue with backup files is the do have all settings (so may not be ideal to one clone a Mikrotik to another, since it keeps the name, log files, etc. from the orginal). Also, when restoring a backup file, the the version running should match the version used to make the backup file.

See https://help.mikrotik.com/docs/display/ROS/Backup for more information. I did forget that in recent version there is "Cloud Backup" – that can skip the download to desktop/mobile step – but it may be easier not to try that out for the first time here.

The help also has an overview of both Backup/Restore and export/import here: https://help.mikrotik.com/docs/display/ ... up/Restore

Thank you all. The backup goes without saying, but somebody mentioned in the forums that restore does not always work going from 6 to 7. That's why they suggest the export/import method.
Well, it will be some time before I upgrade to buggy 7, so I will have a lot of time to prepare.

Yeah this stuff is little tricky. But with both backup file and config export, any upgrade problem is pretty easily fixed - either by fixing V7 config or going back to V6. As a best practice also copies of the RouterOS NPK files for platform/version used for the backup, in case Mikrotik website goes down – that's also happen recently.

The backup goes without saying, but somebody mentioned in the forums that restore does not always work going from 6 to 7. That's why they suggest the export/import method.

You likely do NOT want restore a backup from V6 over V7. If V7 didn't import your config right, and just work after upgrade... That might be a good sign to just rollback to V6. And it the rollback where you'd want that backup file to get you back to where you started on V6. The config file is useful to make sure the config matched, but unless your using esoteric feature or BGP/advanced routing, in most case the upgrade itself goes okay. But...

Well, it will be some time before I upgrade to buggy 7, so I will have a lot of time to prepare.

Good idea.

I doubt you'll need Netinstall (mainly for a bricked device), but a plan+backup+config to rollback is very wise on your part. But the KEY thing about netinstall is DO NOT want to use a "export" file as the "script file" in netinstall to get your config back! So if you somehow needed netinstall... You want to use it to get a CLEAN RouterOS, then restore your backup file AFTER netinstall got the SAME version installed used when the backup was taken.

Basically you should restore on same ROS version, as was used by the backup file. Even if it means upgrading/downgrading (or using netinstall) so the backup & OS versions matched. It may work to restore a backup on different version, but it's not a good idea. And if you wanted a different version, upgrade/downgrade AFTER the backup was restored on the version of RouterOS used for backup.

Thank you for everything Amm0. Very valuable information. I guess a major upgrade (like 6 to 7) is a good chance to clean my configuration anyway. The reason I am so careful is because this pair of RB922's is my Internet connection. So, if something goes wrong, no help forums, no access to NPK files, nothing. I must have everything at hand when I do it.