Centralized Client Management
Overview
Centralized Client Management (CCM) lets an administator create/edit backup schedules and change client settings in the backup server which can be then be pushed into the client machines. It allows the administrator to manage multiple client machines and their backup schedules centrally from the web console of the backup server.
How does the Centralized Client Management (CCM) feature work?
In the backup server web console, client settings and backup schedule details can be added or edited against the particular client machine. These changes are then picked up by the client machine and the client updates itself with these changes.
What client settings and backup schedule details can be managed using Centralized Client Management?
Using "Centralized Client Management" feature, the backup administrator can do the following in the client machine from the web console of the backup server:
- Adding new backup schedules (not available for plugin based backups like backup of Exchange Server, SQL Server etc.)
- Editing an existing backup schedule - can edit the schedule time, files to be backed up, additional full backup options etc.
- Running a backup
- Suspending a backup
- Resuming a suspended backup
- Deleting a backup
- Changing Client's Backup Window settings
- Changing Client's Bandwidth Throttling settings
- Changing Client's Automatic Software Update settings
Making Client Settings changes from backup server through Centralized Client Management
In the backup server, clients' settings can be changed through the Centralized Client Management in the following pages in the web console.
- List of backup clients under a customer: In this page, the client machines's common settings such as Client's backup window, Client's bandwidth throttling and Client's automatic software update settings can be changed by clicking on the "Change Client Side Settings" action icon against the respective client.
- List of backup schedules from client client: In this page, client's backup schedule settings such as Add a new backup schedule, Edit an existing backup schedule, Start/Resume/Suspend a backup etc., can be configured by clicking on the "Change Client Side Backup Configurations" action.
- Disk Space & Client Management: In this page, you can configure client as well as backup schedule settings by clicking on the "Change Client Side Settings" and "Change Client Side Backup Configurations" actions for the corresponding client and backup item.
- Search result page: In this page, Centralized Client Management action icon will be shown with the client or backup list as per the serch term. By clicking on that action icon, client or backup schedules settings can be configured.
FAQs
Will a client running an older version can access its setting changes in the backup server by Centralized Client Management feature?
No. CCM is only supported in clients running v3.5 SP3 or higher versions.
How frequestly does the client connect to the backup server for fetching its setting changes through CCM?
The client tries every 5 minutes. Therefore, once the setting changes are specified in the backup server, it could take up to 5 minutes for those changes to appear in the client.
Can I configure multiple settings for a client/backup schedule at a time?
Yes, multiple settings can be configured for a client/backup schedule at a time in the backup server. However, though all the setting changes are fetched by the client when it connects, they will be applied one by one - the ones specified first in the backup server will be applied first in the client. Note: For backup setting changes, if the particular backup is in progress, then though the client will fetch its setting changes from the backup server, it will not apply them for the backup until the backup is complete. Also, if multiple backup schedule setting changes are specified in the backup server for a backup, all those settings will be fetched and applied in the client, over-writing the previous changes. Hence in effect, only the last edit backup will be applied in the client side. To avoid this, configure only one edit backup schedule at a time for a backup schedule.
Is there any limitation for maximum number of settings can be configured for a client or backup schedule using Centralized Client Management (CCM) feature?
No, there is no limitation on the maximum number of settings that can be configured for a client or backup schedule through CCM.
When will the client/backup settings will be applied in the client system?
The client/backup settings will be applied immediately after they are fetched from the server. However, if the backup is in progress, then it's settings will be applied only after the current backup is completed.
If the admin adds a backup for a client through CCM, wont the admin be aware of the backup password? Isn't that a security issue?
Actually the admin doesn't specific a encryption password while adding a backup through CCM. The user of the client machine can set up a 'Default Password' in the client. Any backup added through CCM will take this default password as the encryption password - a password which only the user is aware of and not the admin. Therefore, before adding a new backup schedule through CCM, the client should enable default backup password in the client web console. This default password setting will then be used when the newly added backup is fetched from backup server and applied in the client through CCM.
How do I enable the Centralized Client Management feature
Centralized Client Management feature is enabled by default. The client automatically connects to the backup server to which backup schedules are configured or to the backup server that is specified in the CCM configuration page in the client web console.
Limitations
The client and backup settings configured by Centralized Client Management feature are currently not replicated to the replication server. Hence, those details won't retrieved by Server Disaster Recovery feature. When specifying the settings for a backup of files from a mapped drive, the client will check for availability of the mapped drive. If the disk drive is not available, then it will be considered as application mapped drive and then stored. This way, the backup may fail if it was configured for backing up files from OS mapped drive and OS drive was not accessible for the application when applying the retrieved client setting. To workaround this issue, configure the application mapped drive for the same OS mapped drive location with the same drive letter.
|
Home 
Print