Not with the system, but with the backup session. In case the data change rate is very high you might get a snapshot overflow, which means that there is not enough space to keep all changes for the period the session runs. That will casue backup job to fail. In such case VAL will increase snapshot size automatically and attempt a three retries.Can there be a problem with the running system?
No, it can't, unless you change the default settings to extreme values without consulting our support team first.can Veeam damage the system or database?
No, it's not. VAL uses Copy-on-Write snapshot to ensure filesystem consistency.Is Veeam doing file locking or simular things?
Full and volume backups are the same thing, blocks are copied to the target storage from source device. During file-level backup VAL copies files as a whole + their attributes.Is there a difference how Veeam reads the data from the disk when doing a full, volume or file based backup?
No, it is not possible. Kernel module keeps CBT data in memory (if you reboot the host VAL will perform full rescan) and it takes negligibly small amount of space to keep that data. Every time something is written to a block, kernel module saves current index value to the corresponding array cell. During next incremental run VAL compares the values with the values that are kept in a backup file, and copies only those blocks that have different (higher) value.How does the Changed-Block-Tracking (CBT) works an where does it save its data? Is it possible that this function is filling the file system on the backup source?
Feb 16 23:15:00 hostname kernel: ERR veeamsnap:snapshotdata.c:__snapshotdata_write_dio_request_to Cannot store data to snapshot. Not enough space.
Feb 16 23:15:00 hostname kernel: ERR veeamsnap:snapshotdata.c:snapshotdata_SetCorrupted Now snapshot corrupted.
Not sure what you mean, please provide an example of the differences.Is it normal that settings in veeam.ini is different between linux server when we do standard install ?
That info is not for public usage, will reply in PM.Someone could explain me the settings in veeam.ini plz ? There is no documentation on veeamsnap settings…
This part means that 'common' snapshot algorithm was triggered instead of 'stretch'. That happens only if the filesystem is not ext4 or XFS, is that the case for you system? Could you please share both files and PM me the link so I can download them? Also please tell me which one of them has been modifed manually by either you or our support team.usedPercent= 10
Users browsing this forum: No registered users and 2 guests