Regify provider appliance update guide - Revision history

Regify: /* Important notes about update scenarios and roll-backs */

2020-12-07T07:29:29Z

Important notes about update scenarios and roll-backs

Regify: /* Simple update */

2020-11-04T13:38:17Z

Simple update

Regify: /* How to safely revert to a previously done VM snapshot */

2020-06-16T08:38:03Z

How to safely revert to a previously done VM snapshot

Regify: /* Simple update */

2020-06-16T08:36:42Z

Simple update

Regify: /* Simple update */

2020-06-16T08:33:06Z

Simple update

Regify: /* How to safely revert to a previously done VM snapshot */

2018-02-02T11:20:36Z

How to safely revert to a previously done VM snapshot

Regify: /* How to revert to a previously done VM snapshot */

2018-02-02T11:19:39Z

How to revert to a previously done VM snapshot

Regify: /* Notes */

2017-04-12T13:14:00Z

Notes

Regify: /* Important notes about update scenarios */

2016-07-07T10:50:07Z

Important notes about update scenarios

Regify: /* Update with fallback option */

2016-07-07T10:49:17Z

Update with fallback option

@@ Line 41: / Line 41: @@
 # Contact support@regify.com and tell about your experience.
-== Important notes about update scenarios and roll-backs ==
+== Important notes about restoring VM snapshots and backups ==
-In order to understand the complexity of roll-backs, you need to consider the following:
+In order to understand the complexity of VM roll-backs, you need to consider the following:
 * If someone registers at your regify provider, his email address is registered in the regify clearing service (anonymized as fingerprint).
 * During registration, every regify provider first checks the clearing if the e-mail address is not already registered at any regify provider. If it is, the registration is denied!
-* Thus, if you register a new user at a regify provider and reset the database later (eg revert to VM snapshot), the e-mail address is still registered in the clearing. As it is no longer in your provider database you can not even delete this registration. The user is blocked to register forever.
+* Thus, if you register a new user at a regify provider and reset the database later (eg revert to VM snapshot or a VM backup), the e-mail address is still registered in the clearing. As it is no longer in your provider database you can not even delete this registration. The user is blocked to register forever.
 * If you register transactions, they are registered in the clearing and in the users regify provider. If you revert the provider database later (eg revert to VM snapshot), the transaction entries in your provider are missing. The transactions still can get opened (clearing delivers the key) but your provider is no longer able to assign the notifications to an existing entry in his database. Therefore, the sender will not get a receipt notification at all. The transaction is no longer listed in users history. The provider might trigger an error in his logs because of an unknown transaction ID.

@@ Line 6: / Line 6: @@
 # Login to your regify provider appliance using SSH (PuTTY is the recommended tool).
-## If you login as ''root'', you ned to type "providerConfig" to open the appliance menu.
+## If you login as ''root'', you need to type "providerConfig" to open the appliance menu.
 ## If you login as ''regify'', the appliance menu opens up automatically.
 # Select the "Check for updates" option.
-# Verify the updates found. Select OK to do the update.
+# Verify the updates found. Select OK or YES to do the update.
 # Select the "Check for updates" option and repeat as long as no more updates are found.

@@ Line 33: / Line 33: @@
 # Enter provider administration (https://yourUrl/ADMINISTRATION/)
-# Delete all users that have been created during test period and respect the following:
+# Delete all users that have been created since the last snapshot and respect the following:
 #* If there are unknown users since the update, please note their name and e-mail address!
 #* This allows you to contact them and let them re-register after going back.

@@ Line 6: / Line 6: @@
 # Login to your regify provider appliance using SSH (PuTTY is the recommended tool).
 # Select the "Check for updates" option.
 # Verify the updates found. Select OK to do the update.

@@ Line 1: / Line 1: @@
 == Simple update ==
-'''We strongly recommend to make a backup or snapshot as a fall-back option. See next major topic below!'''
+'''We recommend to make a backup or snapshot as a fall-back option. See next major topic below!'''
 In order to update your regify provider appliance, please follow these steps:

@@ Line 36: / Line 36: @@
 #* Please note that transaction history during this period is not able to get restored.
 # Revert your VM to your previous snapshot.
 # Contact support@regify.com and tell about your experience.

@@ Line 28: / Line 28: @@
 # Note the notes for "Simple update" in first chapter here.
-=== How to revert to a previously done VM snapshot ===
+=== How to safely revert to a previously done VM snapshot ===
 # Enter provider administration (https://yourUrl/ADMINISTRATION/)

@@ Line 13: / Line 13: @@
 * The provider will be unreachable for a few minutes during update.
 * After updating, always login to your provider administration (https://yourUrl/ADMINISTRATION/) and check if there is something to do.
-* It is possible that the error log gets some entries during update. In most cases you can ignore them.<br>If you are unsure about them, please send them to support@regify.com and ask for verification.
+* It is possible that the error log gets some entries during update. In most cases you can ignore them.<br>If you are unsure about them, please send them to support (at) regify.com and ask for verification.
 == Update with fall-back option ==

@@ Line 15: / Line 15: @@
 * It is possible that the error log gets some entries during update. In most cases you can ignore them.<br>If you are unsure about them, please send them to support@regify.com and ask for verification.
-== Update with fallback option ==
+== Update with fall-back option ==
 If you do not trust in our update mechanisms, you should follow this scenario: