public:users
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:users [2019/08/12 11:04] ronnie.chan |
public:users [2023/09/08 15:34] (current) anam.gumba |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Add new backup user ===== | ===== Add new backup user ===== | ||
| - | A new backup user can be created. Following properties can be configured for a backup user | + | A new backup user can be created. Following properties can be configured for a backup user: |
| * Login name | * Login name | ||
| Line 23: | Line 23: | ||
| * Manage Contact Information | * Manage Contact Information | ||
| - | ===== Add new backup user ===== | + | ===== Delete backup user ===== |
| - | A new backup user can be created. Following properties can be configured for a backup user | + | Remove selected backup users from AhsayCBS. |
| + | ===== Auto update client software ===== | ||
| + | Trigger update of client's AhsayOBM / AhsayACB software from AhsayCBS. | ||
| - | ==== Move / Import / Export Users ==== | + | ===== Broadcast ===== |
| - | This function handles export users to a file, import users from a file, and export user’s home directory to another user home. | + | Send email message to the contact email addresses of select users. You can choose to send plain text or HTML broadcasting content and include attachment if needed. |
| - | You may use this function to migrate a user from an AhsayCBS to another AhsayCBS, migrate a user from the user home to another user home on the same machine. This function is limited to system user with admin role. | + | |
| - | * Move user home to – Export user from a user home to another user home. | + | |
| - | * (v7 users) Import users to – Import a previous exported user zip file into the user home. | + | |
| - | * (v6 users) Import users from previous versions – Import a v6 user profile from user home. (Move v6 user folder into v7 user home then enter the page, do not required restart services, will skip empty named user / existing users in CBS for selection) | + | |
| - | * Export users to file – Export user profile and backup files to a zip file format. | + | |
| - | **Note** : Please schedule a time with your users when you need to migrate their user home to another user home/AhsayCBS. It is better to suspend the user, stop any running backup, and close the client interface before you perform the user export. | + | ===== Initiate Backup Job ===== |
| + | Start backup jobs remotely without the need to access the client machine. | ||
| - | {{ :importv6user.png?nolink |}} | ||
| - | Since the move of a user from a user home to another user home would export the whole user profile and the backup data from a user to another user home. When moving a user account with large backup sets, it is expected to wait for a long period of time. So, it is suggested to perform 1 user export at a time, and during the export, please do not restart service or server. In case of power failure or server shutdown, the move user’s process would become fail. | + | ===== Run Restore Drill ===== |
| + | Manually run a restore drill whenever needed to check for data healthiness. | ||
| - | ---- | ||
| - | ==== Export Users' Usage Statistics to CSV ==== | + | ===== Export users' usage statistic to CSV ===== |
| + | Export usage statistic of selected users to a CSV file which you can import/concert to other tools such as Excel or database for further purpose. | ||
| - | To export user' usage statistic to a CSV (Comma Separated Values) file. Which you can import/concert to other tools such as Excel or database for further purpose. | + | ===== Move / Import / Export Users ===== |
| + | Export selected users to a file, import selected users from a file, and export user’s home directory to another user home. | ||
| - | In exported CSV file:\\ | + | You may use this function to migrate a user from an AhsayCBS to another AhsayCBS, migrate a user from the user home to another user home on the same machine. This function is limited to system user with admin role. |
| - | Name: User name\\ | + | * Move user home to – Export user from a user home to another user home. |
| - | Alias: Alias of user\\ | + | * (v7 users) Import users to – Import a previous exported user zip file into the user home. |
| - | Owner: Owner of user\\ | + | * (v6 users) Import users from previous versions – Import a v6 user profile from user home. (Move v6 user folder into v7 user home then enter the page, do not required restart services, will skip empty named user / existing users in CBS for selection) |
| - | Usage (Bytes): To convert back to K/M/G/TB, divided by 1024\\ | + | * Export users to file – Export user profile and backup files to a zip file format. |
| - | Quota (Bytes): To convert back to K/M/G/TB, divided by 1024. Limitation: Standard quota before migrating to >=v7.15.6.38 is shown in this field, which may be out sync with the current quota settings in CBS >= v7.15.6.38\\ | + | |
| - | (Refer to [[tms>21064]] [KB ER] Able to show the quota of destinations for exporting CSV) | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ==== Broadcast Message ==== | + | |
| - | + | ||
| - | Send broadcast message to contact email address of backup user(s) in text / html format (with / without attachment) | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ==== Save Button ==== | + | |
| - | + | ||
| - | After clicked the save buttons, the backup users (users.xml), user groups (userGroup.xml) and policy groups (policyList.xml) are updated. | + | |
| - | * Avoid concurrent modification to autoUpdate.bdb, the page is blocked when clicked the save / cancel button. | + | |
| - | + | ||
| - | ----- | + | |
| - | ==== Cancel Button ==== | + | |
| - | + | ||
| - | After clicked the cancel button, the add user list and delete user list is cleared | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ===== Manage Windows Active Directory Integration ===== | + | |
| - | When this feature is enabled and AhsayCBS fails to authenticate a user logon using its own records, a user authentication will be dispatched to Windows Active Directory automatically. This means that if an AD is presented in the network, it is only required to create a user account once in the Windows Active Directory. The same user account can also be used on the AhsayCBS server. This is because AhsayCBS will create this user account automatically after authenticating this logon using AD. The user account created will be of the type Paid and of backup client AhsayACB (unless the user logon using AhsayOBM). | + | |
| - | + | ||
| - | * Note that the whole page will wait for this tab to be loaded before displaying the page for non-re-seller system users. | + | |
| - | + | ||
| - | ===== Expected Behaviors ===== | + | |
| - | + | ||
| - | - Backup User List | + | |
| - | - Filter | + | |
| - | - Client Type: Filter the backup users by the client type (OBM / ACB) and customized client type should be shown (%OBM_SHORT_NAME%, %ACB_SHORT_NAME%) | + | |
| - | - Export user's usage statistics to CSV | + | |
| - | - Exports the used online quota (i.e. exclude local destination) and remaining online quota of the user in .CSV format. | + | |
| - | - Backup User | + | |
| - | - Trigger the backup job running in OBC after selected the destination(s) where the destination ID(s) are saved in users.xml as follows. Make sure the scheduler service in client machine is started. | + | |
| + | <WRAP prewrap> | ||
| <code> | <code> | ||
| - | <Key name="com.ahsay.obx.cxp.cloud.RunBackupSettings" content=""> | + | **Note** : |
| - | <Value data="Y" name="enable" type="boolean" /> | + | Please schedule a time with your users when you need to migrate their user home to another user home/AhsayCBS. It is better to suspend the user, stop any running backup, and close the client interface before you perform the user export. |
| - | <Value data="" name="backup-type" type="string" /> | + | |
| - | <Value data="2017-05-21-22-02-45" name="backup-job-id" type="string" /> | + | |
| - | <Value data="-1495245989958" name="destination-id-1" type="string" /> | + | |
| - | <Value data="-1495246372172" name="destination-id-2" type="string" /> | + | |
| - | <Value data="-1495375276154" name="destination-id-3" type="string" /> | + | |
| - | </Key> | + | |
| </code> | </code> | ||
| + | </WRAP> | ||
| - | ---- | + | {{ :importv6user.png?nolink |}} |
| - | ===== Troubleshooting Guide ===== | + | Since the move of a user from a user home to another user home would export the whole user profile and the backup data from a user to another user home. When moving a user account with large backup sets, it is expected to wait for a long period of time. So, it is suggested to perform 1 user export at a time, and during the export, please do not restart service or server. In case of power failure or server shutdown, the move user’s process would fail. |
| - | **User owned by sub-admin disappear when save button is clicked in [User, Groups & Policies]** | + | ===== Rebuild storage statistics ===== |
| + | Rebuild the storage statistics of selected users, applicable only for v6 Backup Sets. This function is not applicable for v7+ Backup Sets and will do nothing if used. | ||
| - | When v6 users in OBS owned by sub-admin are migrated to newly installed CBS by moving the user folders {username}#{sub-admin ID}, and a new sub-admin is created in CBS instead of migrated from the OBS, ID of the sub-admin will not be align and upon clicking the save button in [User, Groups & Policies], checking will be done to remove the mismatched users. User setting changes and encryption key may be loss together. | + | ===== Rescan all user home directories ===== |
| + | The feature ensures the status of all user home is updated so that the backup sets under available user home should be shown in the selecting list for Admin user account to exclude while the backup sets under unavailable user home should not be listed during backup data migration. And also if the user home is offline, the backup and restore job cannot be run properly, so the feature helps confirm the status of the user home before starting a backup and restore job. | ||
| - | **Solution** | + | ===== Enable / Disable Two-Factor Authentication ===== |
| + | Enable or disable the two-factor authentication of backup users. | ||
| - | 1. Stop CBS services | ||
| - | |||
| - | 2. Change the system user ID in cbs.json("ID"=XXXXX) and /branding to align with the #ID in user home | ||
| - | |||
| - | 3. Start CBS services | ||
| - | |||
| - | ==== Move User Home (Replication) ==== | ||
| - | |||
| - | If a partner has replication enabled and moved their user homes on CBS, the user home folder will be automatically replicated to the new user home on the replication server. However, they will have a duplicated user home folder in the old user home of the replication server. If there are any snapshots that have not been copied over, try the following: | ||
| - | |||
| - | 1. Check that the new user home does not have the same retention snapshot folder. | ||
| - | |||
| - | 2. If it does not have the same retention snapshot folder, copy it from the old user home. | ||
| - | |||
| - | 3. If it does have the same retention snapshot folder, do not try to merge the two together as this could lead to data corruption. | ||
| - | |||
| - | ---- | ||
| - | |||
| - | |||
| - | Below are the FAQs / Issues related to AhsayCBS Users Management feature. | ||
| ===== Issues ===== | ===== Issues ===== | ||
| * [[public:5184_issue:cannot_configure_timezone_setting_with_gmt_-xx:30_or_gmt_13:00_using_the_adduser.do_api|Cannot configure timezone setting with GMT+/-xx:30 or GMT+13:00 using the AddUser.do API]] | * [[public:5184_issue:cannot_configure_timezone_setting_with_gmt_-xx:30_or_gmt_13:00_using_the_adduser.do_api|Cannot configure timezone setting with GMT+/-xx:30 or GMT+13:00 using the AddUser.do API]] | ||
| + | |||
public/users.1565579071.txt.gz · Last modified: 2019/08/12 11:04 by ronnie.chan