If you’re talking about backing virtual machine, then please be aware that VB&R put into use special VMware feature called CBT, which allows us tracking/backing ip only those blocks that have been changed since the last backup run.

Moreover, even if CBT doesn't work, VB&R leverages its proprietary mechanism that works this way: VB&R scans through the whole VM image and a checksum (hash) is calculated for every data block, then it verifies what blocks have been changed on your VM compared to the VM image stored in the backup file.

So, in case of virtual machine backup/replication, it's practically always about an incremental not a full run.

If you’re talking about Copy Job, then you need to know it just transfers files as a whole knowing nothing about changes that have happened previously. So, it can be utilized in incremental way.

v.Eremin wrote:If you’re talking about backing virtual machine, then please be aware that VB&R put into use special VMware feature called CBT, which allows us tracking/backing ip only those blocks that have been changed since the last backup run.

Moreover, even if CBT doesn't work, VB&R leverages its proprietary mechanism that works this way: VB&R scans through the whole VM image and a checksum (hash) is calculated for every data block, then it verifies what blocks have been changed on your VM compared to the VM image stored in the backup file.

So, in case of virtual machine backup/replication, it's practically always about an incremental not a full run.

If you’re talking about Copy Job, then you need to know it just transfers files as a whole knowing nothing about changes that have happened previously. So, it can be utilized in incremental way.

Hope this helps.
Thanks.

thank you for your answer,
yes i am talking about the files, as i have like 1,5 TB and it will take long to back it up every night,
so i want to run Full backup onces during the night, and schedule a job to back up the data ( i want this job to check just for the files that been changed to back them up, not the whole 1.5 TB, over and over every night,

Julien, this cannot be done with this kind of job. File copy job performs a full run every time.

If you need incremental backups, you can use ordinary backup jobs against the VM to copy just those blocks that have been changed in the VM guest OS since the job's previous run. Veeam B&R is a block-level solution and tracks changed blocks, not files.

If your files dont change , then the underlying blocks are not going to change either - so the CBT incremental will be pretty small. I have a customer who backs up a 2TB fileserver every hour; it takes 5 minutes and produced pretty small incrementals.

chrisdearden wrote:If your files dont change , then the underlying blocks are not going to change either - so the CBT incremental will be pretty small. I have a customer who backs up a 2TB fileserver every hour; it takes 5 minutes and produced pretty small incrementals.

i dont mind having it every hr backing up,
but the issue it create a new folder,and double the files and folder,
so i want it to back up just to one folder,

Not sure why you want to back up to a partition on the same server? Sure you can add the partition(Disk) as a repository but what if you lose the server and need to recover? this will add further steps to you process, ie mounting the disk to another server re adding the repository to veeam.

v.Eremin wrote:If you’re talking about Copy Job, then you need to know it just transfers files as a whole knowing nothing about changes that have happened previously. So, it can be utilized in incremental way.

jamerson wrote:yes i am talking about the files, as i have like 1,5 TB and it will take long to back it up every night

I believe the question is not about Copy Jobs, but rather about Veeam backup jobs according to the later post below:

jamerson wrote:my story is the next,
i have FS, DC, EX,
DC is 40GB
EX= 140GB
FS=1,5TB

kjc3303 wrote:Not sure why you want to back up to a partition on the same server? Sure you can add the partition(Disk) as a repository but what if you lose the server and need to recover? this will add further steps to you process, ie mounting the disk to another server re adding the repository to veeam.

i backup on the partition in case need to recovery for a quick revocer,
also i backup on external disk

kjc3303 wrote:Hi Yes they will give support on evaluation licenses, they're good like that

i''ve seen alot of people suffering with this error, about files back up that the name is too long,
so we''ll stuck with our back up software untill Veeam is stable,
Windows Server back up does great Job on backing up files,

Hi Julien, you should be requesting updates from your support engineer, as the team behind this forum is not involved with support. However, please note that only Premium Support is provided 24/7. Standard Support is provided during business hours only, while yesterday and today is weekend. Additionally, response times also depend on the issue severity, and whether or not you are a paying customer... you can review our support policy for more information. Thanks!

Gostev wrote:Hi Julien, you should be requesting updates from your support engineer, as the team behind this forum is not involved with support. However, please note that only Premium Support is provided 24/7. Standard Support is provided during business hours only, while yesterday and today is weekend. Additionally, response times also depend on the issue severity, and whether or not you are a paying customer... you can review our support policy for more information. Thanks!

hey Gostev,
i have already opend the ticket, and the support team request the log file which i provided them, but they are still telling me this windows limitation name however Symantec back up doesn''t have this issue,
Windows limitation is not really the issue,i beleive this a bug in the software,

Symantec requires in-guest agent and file index created during backup to enable file recovery, which is a completely different technology which cannot be compared directly with Veeam B&R. We perform agent-free image-level backup (one of many reasons why customers prefer Veeam to Symantec), and thus we have to be more creative at restore time.

However, as somebody from my team already explained you in another thread you posted this issue in, this is scheduled to be addressed in v7. Support is correct that the current limitation sits is outside Veeam code, but we should be able to work around it by redesigning some part of file level recovery engine.

The issue happens in pretty exceptional cases (very long file paths) and did not plague too many customers, which is why it was not fixed in earlier releases.