Hi Everybody,
i need help i'm newby. I have configured an incremental Backup on Tape
for backup of 80 VMware VMs. I have configured the jobs to start each
day at 12:00. On Sunday I configured a Full Backup always starting from
12:00.
The conservation is 20 days and I have created 2 different Pools, one for
full backups and one for incremental backup.
On Sunday the Full Backup Job started successfully at 12:00 and ended at
21:00, I just don't understand why I made even a very small Backup
Incremental of only 3 VMs consecutively, using a second Tape ????
You know how to give me an explanation
Thx
Simone
ID: INC0177810
-
- Novice
- Posts: 5
- Liked: never
- Joined: Mar 14, 2022 10:37 am
- Contact:
-
- Product Manager
- Posts: 14837
- Liked: 3084 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Veeam Tape Schedule
Hello,
and welcome to the forums.
I'm not 100% sure about understanding the situation / question, but I try to answer... backups are created based on a schedule. So my guess is, that new backups appeared that matched a tape schedule.
What kind of tape job are you using? Backup-to-tape or file-to-tape?
Best regards,
Hannes
and welcome to the forums.
I'm not 100% sure about understanding the situation / question, but I try to answer... backups are created based on a schedule. So my guess is, that new backups appeared that matched a tape schedule.
What kind of tape job are you using? Backup-to-tape or file-to-tape?
what kind of number is this? Veeam support case numbers today look like 05..... today.ID: INC0177810
Best regards,
Hannes
-
- Novice
- Posts: 5
- Liked: never
- Joined: Mar 14, 2022 10:37 am
- Contact:
Re: Veeam Tape Schedule
Thank you very much for the welcome and for the reply,
I found that the problem was due to 3 3 Vm jobs ending too late and crossing with tape backup jobs
I am backing up to disks and I have split the VMs on two different physical servers, I have created 1 job for each VM. Then as Disaster Recovery I created 1 single job which includes all vm and writes on 6 incremental tape and on Sunday a Syntethic Full
sorry but I'm newbie and maybe that's not the answer you wanted.
It's the number I used to write to support, it probably wasn't the exact code.
Thank you very much
I found that the problem was due to 3 3 Vm jobs ending too late and crossing with tape backup jobs
I am backing up to disks and I have split the VMs on two different physical servers, I have created 1 job for each VM. Then as Disaster Recovery I created 1 single job which includes all vm and writes on 6 incremental tape and on Sunday a Syntethic Full
sorry but I'm newbie and maybe that's not the answer you wanted.
It's the number I used to write to support, it probably wasn't the exact code.
Thank you very much
Who is online
Users browsing this forum: No registered users and 21 guests