-
- Influencer
- Posts: 19
- Liked: 5 times
- Joined: Mar 10, 2014 5:37 pm
- Contact:
backup copy not recognizing new restore points in linked backup job
Hello,
we noticed a strange behavior in veeam B&R 9.5 with one of our backup copy jobs.
We have a backup job running once a week and a backup copy referencing to that backup job.
The backup job run normally and copied about 177 GB of new data.
But the backup copy is not copying any data. It only states waiting for new restore points.
The backup copy has no data so any restore point should be considered as a new one shouldn't it?
Even a newly created backup copy job linked to the backup job is not copying any data and just states it is waiting for new restore points.
Normally when we create a new backup copy job and link it to a backup job it recognizes a new restore point and starts an initial copy run.
This is a behavior that we deemed logical, as a backup copy job that never ran should consider any restore point linked to it as a new restore point.
If we link any other backup job to the backup copy job it instantly recognizes new restore points and start copying.
There are definitely restore points in the backup job we are trying to copy. There are vbk and vrb file on the repository and the restore points are shown in veeam and we can restore data from any restore point. We just can't get a backup copy job to work on this backup job.
we noticed a strange behavior in veeam B&R 9.5 with one of our backup copy jobs.
We have a backup job running once a week and a backup copy referencing to that backup job.
The backup job run normally and copied about 177 GB of new data.
But the backup copy is not copying any data. It only states waiting for new restore points.
The backup copy has no data so any restore point should be considered as a new one shouldn't it?
Even a newly created backup copy job linked to the backup job is not copying any data and just states it is waiting for new restore points.
Normally when we create a new backup copy job and link it to a backup job it recognizes a new restore point and starts an initial copy run.
This is a behavior that we deemed logical, as a backup copy job that never ran should consider any restore point linked to it as a new restore point.
If we link any other backup job to the backup copy job it instantly recognizes new restore points and start copying.
There are definitely restore points in the backup job we are trying to copy. There are vbk and vrb file on the repository and the restore points are shown in veeam and we can restore data from any restore point. We just can't get a backup copy job to work on this backup job.
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
Hello,
Yes, it should recognize any restore point as a new one.
Can you share all the settings of the backup copy job (interval, retention, GFS scheme, target, etc.).
Thanks!
Yes, it should recognize any restore point as a new one.
Can you share all the settings of the backup copy job (interval, retention, GFS scheme, target, etc.).
Thanks!
-
- Influencer
- Posts: 19
- Liked: 5 times
- Joined: Mar 10, 2014 5:37 pm
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
Hello DGrinev,
When we compiled all the settings, we noticed that the copy data store we selected was the same as the backup data store.
Changing the copy data store to another data store in another location made the Backup Copy job work.
Since it doesn't make sense to copy Backup Copy data to exactly the same data store as the backup data, the behavior of the backup copy job to actually copy nothing is logical, but the error message (or its lack) and the message "Waiting for new restore points" are not.
Since we are all human, errors can happen again and again, so here is a suggestion:
The system should either check whether the data stores for backup and backup copy are the same and refuse to accept such settings, or at least change the message from "Waiting for new restore points" to something clearer like " mismatch of data stores" or "Target datastore equals source datastore. Data won't be copied" or anything like that.
Thank you and best regards
When we compiled all the settings, we noticed that the copy data store we selected was the same as the backup data store.
Changing the copy data store to another data store in another location made the Backup Copy job work.
Since it doesn't make sense to copy Backup Copy data to exactly the same data store as the backup data, the behavior of the backup copy job to actually copy nothing is logical, but the error message (or its lack) and the message "Waiting for new restore points" are not.
Since we are all human, errors can happen again and again, so here is a suggestion:
The system should either check whether the data stores for backup and backup copy are the same and refuse to accept such settings, or at least change the message from "Waiting for new restore points" to something clearer like " mismatch of data stores" or "Target datastore equals source datastore. Data won't be copied" or anything like that.
Thank you and best regards
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
Can you share what's the version of VBR 9.5 you are at?
We do have a protection implemented, that should prevent you from choosing the same target for the copy job as for the source job. Thanks!
We do have a protection implemented, that should prevent you from choosing the same target for the copy job as for the source job. Thanks!
-
- Influencer
- Posts: 19
- Liked: 5 times
- Joined: Mar 10, 2014 5:37 pm
- Contact:
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
That's shouldn't be an issue then.
Can you clarify what exactly do you mean by the same data store, is it just the same repository or different repositories on the same hardware device? Thanks!
Can you clarify what exactly do you mean by the same data store, is it just the same repository or different repositories on the same hardware device? Thanks!
-
- Influencer
- Posts: 19
- Liked: 5 times
- Joined: Mar 10, 2014 5:37 pm
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
Same repository on same hardware device (actually not real hardware. Repositories are virtualmaschines, so: same vm, same drive in vm)
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
I've discussed the issue with the Dev Team.
You cannot select the repository as a target, if it's selected as the source for the backup copy job.
In case where the backup job is the source, you can do that.
However, you can find the message in the job session log that the restore point is located in the Backup Copy target repository and cannot be used as a source.
It's by design, since the backup copy job can consist of several backup jobs as a source. Thanks!
You cannot select the repository as a target, if it's selected as the source for the backup copy job.
In case where the backup job is the source, you can do that.
However, you can find the message in the job session log that the restore point is located in the Backup Copy target repository and cannot be used as a source.
It's by design, since the backup copy job can consist of several backup jobs as a source. Thanks!
-
- Influencer
- Posts: 19
- Liked: 5 times
- Joined: Mar 10, 2014 5:37 pm
- Contact:
Re: backup copy not recognizing new restore points in linked backup job
Thanks for the answer.
Who is online
Users browsing this forum: karsten123 and 100 guests