File to Tape ( VBK & VIB)

[OMW72]

Hi there,
we want to have for each day (mo-fr) the current backup chain on tape. The VBK and VIB being created with a copy job.
The settings for the copy jobs are 7 restore days and GFS keep weekly full back up for 1 week and creates a full on Friday
We want to have Friday the VBK file on tape.
Monday: VBK and VIB
Tuesday: VBK, VIB and VIB
.....
Thursday >: VBK, 4 times VIB

Friday the current VBK and so on.....
For the first week it should be not an issue at all to get the necessary files on tape.
Not sure with the second week. Due the fact that the restore days are set to seven i assume that the first backup chain will be deleted as soon as the second chain is completed as well. correct?
For our scenario it would be better that the first chain will deteled as soon as the second weekly full back via GFS is created.

Regards,
Oliver

[david.domask]

Hi OMW72,

Currently the only way to achieve this would be multiple file to tape jobs. You can use the answer to the last question on our Tape FAQ to design this, but effectively each day would get its own job, media pool, and tape. Ensure the file to tape job starts after the source job(s) have run and applied their retention.

[OMW72]

Hi David,
sorry that I came back to you you with topic.

We already created for each day (monday to friday) a media pool and a tape job and it works perfekt. (Backup to Tape)

The Tape Jobs starts every day at the same time and we activated the option "process the latest backup chain only" so prevent to store more files on tape because the retention is set to 14 days.

With the second data center which we have already put into operation we have one step more in terms of our backup solution.

Backjob stores the files in a repository that is located in the data Center 2. A copy ob brings the files back to the data center1 (repository) where the tape Storage ML3 is located . The repositories are in both cases pure storages.

How we have to create the config for the back copy job if we want to have only the latest backup chain on tape. Without a GFS we have a forever inkremental until the retention is reached. Then we have for each a day a VBK file, correct?

How likes like with the GFS? For example we create each monday a new full back so that we get the following chain:

Monday: VBK
Tuesday: VBK, VIB
.....
Friday : VBK, 4 times VIB

This should be the content for each daily separate tape job as well,

What is happening on the second Monday? The goal with the activtes option "process the latest backup chain only" to get only the new created VBK on tape. If the retention is set to 7 days ,does it mean the oldest created backup chain within the backup copy job will be deleted if the current backup chain is completed ? So we have 14 files in the repository and after the latest VIB has been created on friday the oldest chain will be deleted? The maximum of files is 14 ?

is it right that a backup copy job can not be used within the scheduler of a tapjob?

Regards,
Oliver

[david.domask]

Hi Oliver,

How we have to create the config for the back copy job if we want to have only the latest backup chain on tape. Without a GFS we have a forever inkremental until the retention is reached. Then we have for each a day a VBK file, correct?

Just to get it correctly, both sites are managed by a single backup server? Or does Data Center 2 have its own backup server doing a backup copy to data center 1, and data center 1 has its own backup server that can reach the files?

This is important as if it's two backup servers, there won't be a way to get Backup to Tape to work with the backup copies from another server, you will need to use File to Tape.

is it right that a backup copy job can not be used within the scheduler of a tapjob?

I'm sorry I don't understand the question here. The question is can you schedule tape job with the "run after job" feature with Backup Copy jobs?

Without a GFS we have a forever inkremental until the retention is reached. Then we have for each a day a VBK file, correct?

Backup Copy simple retention is always Forever Forward Incremental, correct. I'm not sure I understand your second question but since the goal is to get these backups to tape I'm not sure it's fully relevant -- Tape jobs always work with the simple retention, tape jobs do not concern themselves about the source job's GFS configuration.

Maybe it will be better if you tell your desired tape-out scheme for the backup copies and please clarify the infrastructure above, as unfortunately not able to fully understand the configuration currently. Maybe you can create a quick diagram and share it along with the desired tape-out scheme and then we can better advise. Thanks!

[OMW72]

Hi David,
Demand one :
There is only one VBR managment server for both datacenter.

Demand two:
Yes im looking for option run after job (BackupCopyJob) for the tape job.

I will provide you a diagram for BackupCopy GFS /Tape Job topic asap.

Regards
Oliver