If the backup server has updates installed, the console will be updated automatically. Every time you connect to the backup server locally or remotely, the console checks for updates. For example, if one of your backup servers run version 9.5 Update 3, and another backup server runs version 9.5 Update 4, you will need to use 2 separate consoles for connecting to these servers. Note this if you have more than one backup server in your backup environment, and these backup servers run different versions of Veeam Backup & Replication. You cannot use the same console to connect to backup servers with different versions of Veeam Backup & Replication. For convenience, you can save several shortcuts for these connections. If you have multiple backup servers in the infrastructure, you can connect to any of them from the same console. Other users will be prompted to reload the wizard or window to get the most recent information about the changes in the configuration database. If several users are working with Veeam Backup & Replication at the same time, the user who saves the changes first has the priority. Veeam Backup & Replication prevents concurrent modifications on the backup server. You can install as many remote consoles as you need so that multiple users can access Veeam Backup & Replication simultaneously. You can also use it in a standalone mode - install the console on any machine and access Veeam Backup & Replication remotely over the network. The console is installed locally on the backup server by default. If the connection is re-established within this period, you can continue working without re-logging to the console. To make users work as uninterrupted as possible, the remote console maintains the session for 5 minutes if the connection is lost. To access the data, the console connects to the backup server and queries this information periodically during the work session. User credentials and passwords are stored in the configuration database encrypted with Data Protection API (DPAPI) mechanisms. Such data as user credentials, passwords, roles and permissions are stored on the backup server side. The console does not have a direct access to the backup infrastructure components and configuration database. For more information, see Kerberos Authentication. To build a more secure environment, disable NTLM and leave Kerberos the only domain authentication protocol. Using NTLM increases the attack surface of your backup infrastructure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |