You cannot use direct backup to object storage to keep backups created with Veeam Plug-ins for Enterprise Applications.
we CAN use direct backup to OS with Enterprise Application since v13
8 Matching Annotations
- Last 7 days
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
If you disable encryption, during the next job session Veeam Backup & Replication will automatically create a full backup file.
For backup copy simple mode (Enterprise plugins) we cannot disable/enable encryption while job is running currently. To enable/disable encryption we have to disable the job, change state and enable again
-
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
If you enable or disable encryption for an existing backup created with Veeam Plug-In, during the next job session Veeam Backup & Replication will command Veeam Plug-In to create a full backup file.
If we enable/disable encryption for already created application backup job backup became encrypted after next incremental or full backup (new storage is created) We do not force Full backup here
-
If you change a password for data encryption for an existing backup policy targeted at a Veeam backup repository without changing other backup policy settings, the process of applying the backup policy to a protected computer completes with a notification informing that the backup policy was not modified. This happens because data encryption settings for backup policies targeted at a Veeam backup repository are saved to the Veeam Backup & Replication database and are not passed to a machine with Veeam Plug-In.
If password changed for policy it's applied right after next time VACM is generated (let's say new storage is created) , no UI messages here afaik
-
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
If you change a password for data encryption for an existing backup policy targeted at a Veeam backup repository without changing other backup policy settings, the process of applying the backup policy to a protected computer completes with a notification informing that the backup policy was not modified. This happens because data encryption settings for backup policies targeted at a Veeam backup repository are saved to the Veeam Backup & Replication database and are not passed to a m
If password changed for policy it's applied right after next time VACM is generated (let's say new storage is created) , no UI messages here afaik
-
If you enable or disable encryption for an existing backup created with Veeam Plug-In, during the next job session Veeam Backup & Replication will command Veeam Plug-In to create a full backup file.
If we enable/disable encryption for already created application backup job backup became encrypted after next incremental or full backup (new storage is created) We do not force Full backup here
-
-
tw-preview.dev.amust.local tw-preview.dev.amust.local
-
If you change a password for data encryption for an existing backup policy targeted at a Veeam backup repository without changing other backup policy settings, the process of applying the backup policy to a protected computer completes with a notification informing that the backup policy was not modified. This happens because data encryption settings for backup policies targeted at a Veeam backup repository are saved to the Veeam Backup & Replication database and are not passed to a machine with Veeam Plug-In.
If password changed for policy it's applied right after next time VACM is generated (let's say new storage is created) , no UI messages here afaik
-
If you enable or disable encryption for an existing backup created with Veeam Plug-In, during the next job session Veeam Backup & Replication will command Veeam Plug-In to create a full backup file.
If we enable/disable encryption for already created application backup job backup became encrypted after next incremental or full backup (new storage is created) We do not force Full backup here
-