UT2015 wrote:full backup weekly on *no* day (will that work?)
UT2015 wrote:Another strange thing/bug: When editing properties of a media pool and selecting "automatically create new media set daily at" the value "00:00" leads to the time being changed to 12:00 which is definately wrong/buggy.
We have time settings in 12-hour format in the product so 00:00 is 12:00 AM.
Both Full Backup-Jobs are scheduled to do the full backup only on Saturday. But when they started on Tuesday, they tried to do a full backup to tape! Why is that? The log file states "Backup doesn't contain any backupsets. Forcing full pass." - But this does not make sense. Incremental backup is disabled, full backup is scheduled for Saturdays!
UT2015 wrote:This is not true.
UT2015 wrote:And what about that?
I am using B&R 9.5 U1. Mentioned field is editable in 24-hours-format. Field is also displayed in 24-hours-format except when editing 00:00, value 12:00 is displayed after saving. So you are saying in U2 24-hours-format was replaced by 12-hours-format?!We're again talking about different versions. Which version are you at?
Both. To-tape-job should perform synthetic full of Endpoint backups and active full of vCenter environment. Both is scheduled for Saturdays and was performed on Tuesday.By 'they tried to do a full backup to tape' do you mean synthetic full or just copying vbk-file from repository to tape?
On tape was nothing because the job was created and started for the first time. On disk were both vbks and vbis for the Endpoint backups and for the vCenter environment.What files were in repository and on tape at the moment when the tape job started?
[27.05.2017 11:59:50] <21> Info [CTapeSourceBackupJob]Backing up vbk Backup Job DC012017-05-15T211018.vbk:88475858-0409-4ea7-a946-8f91a9c6b445:15.05.2017 21:10:18:15.05.2017 21:10:18 again because it's a first time backup!
Field is also displayed in 24-hours-format except when editing 00:00, value 12:00 is displayed after saving.
Both is scheduled for Saturdays and was performed on Tuesday.
On tape was nothing because the job was created and started for the first time. On disk were both vbks and vbis for the Endpoint backups and for the vCenter environment.
We have another problem
But don't you agree that it is unlogical, if a job is configured to perform full backup once a week on Saturdays and incrementals are disabled for the job, if the job is running on Tuesday and performs the full backup? I cannot see why this is a good behavior. It would be more logical if the job would do nothing on Tuesday and would do the full backup on Saturday.If there's no full backup on tape than a job will first copy full and process increments afterwards.
You are right, the box is not checked. But it is also not checked in our "old" Backup-to-Tape-job. The files on disk did not change so it is strange that the new job seems to behave different to the old one. And I don't understand why this has influence on synthetic full backups. There is always one old full backup on disk and the to-Tape-job actually creates a new synthetic full...To avoid copying previous backup chains which is happened in your case you need to check Process latest full backup chain only check box in job's Advanced settings.
I have those two jobs pointing to one incremental pool. That pool is configured to automatically create new media set daily at 00:01. Those jobs copy only increments, which is very little and which fits on a single tape (for both jobs). Sometimes those jobs are using the same tape, but sometimes each job uses a tape on its own. How can I force those jobs using one tape together?So in your case I suggest to create two jobs: the first one has fulls pointed to full_meida_pool1, incrementals to incremental_meida_pool, the second one to full_media_pool2 and again incremental_media_pool.
Well it does some days and some days not, which is very strange.If not, only the eject shouldn't cause creating new media set
I do not know, which of both jobs is started first, because both are depending on a Backup-To-Disk-Job and start after this job finished. I cannot create a dependency between both tape-jobs, because I created those jobs to be executed in parallel (to use two tape drives and to store the disk backups in a certain order to tape, as described above).but if I were you I would disable eject option in the first job anyway
Users browsing this forum: mfo and 1 guest