Updating suse 9 1 to 9 2
devices=/dev/disk/by-id/ata-VBOX_CD-ROM_VB2-01700376 9 | repo-debug | open SUSE-Leap-42.1-Debug | No | ---- | Yes | 10 | repo-debug-non-oss | open SUSE-Leap-42.1-Debug-Non-Oss | No | ---- | Yes | 11 | repo-debug-update | open SUSE-Leap-42.1-Update-Debug | No | ---- | Yes | 12 | repo-debug-update-non-oss | open SUSE-Leap-42.1-Update-Debug-Non-Oss | No | ---- | Yes | 13 | repo-source | open SUSE-Leap-42.1-Source | No | ---- | Yes | The above output clearly shows, the open SUSE-Leap-42.1-Update repository is available.
uses this fact to perform rapid upgrades by creating new system tables and simply reusing the old user data files.
For deployment testing, create a schema-only copy of the old cluster, insert dummy data, and upgrade that.
If you are upgrading a pre- to point to the old server's socket location.
(This is not relevant on Windows.) If you want to use link mode and you do not want your old cluster to be modified when the new cluster is started, make a copy of the old cluster and upgrade that in link mode.
To make a valid copy of the old cluster, use , as documented in Section 25.3.3.