Question

GitHub backup with All repositories as content

  • 6 April 2023
  • 6 replies
  • 165 views

Badge +1

Hello,

I would like to backup our GitHub Account where we have a huge amount of repositories.

And few are added very frequently.

But I’m not able to configure once as content “all repositories” in order to have also the new ones added without going back to the configuration.

Someone was able to do it ?

Today I’m forced to add the new ones regularly manually (add content).

Thank you,

Regards,

Michael.

 

 

 


6 replies

Userlevel 7
Badge +23

Hey @Michael EZAOUI,

Just checking you picked all repositories in step 9?

https://documentation.commvault.com/2022e/essential/132592_add_github_app.html

 

With most apps in Commvault, if you add content manually the automatic discovery is disabled for new items.

Badge +1

Hi @Michael EZAOUI ,

I don’t think it’s currently possible. At least not in 11.24; haven’t tested more recent versions yet.

You either choose all repo’s, or specific repo’s, but then then no new repo’s will be added automatically.

A fix was added some time ago where disabled repo’s are automatically skipped (instead of failing the complete job), but to my knowledge there is no such thing as ‘filters’ in Azure Devops / GIT.

Userlevel 4
Badge +10

Hi @Michael EZAOUI 


We provide an option to select “All Repositories”. This option will figure out all the repositories the token has access to, and will backup those.

 

If that’s not happening, kindly escalate with logs.

 

@Ramkumar S for further help.

 

 

 

Thanks,

Sparsh

Userlevel 7
Badge +19

@SparshGupta well this is not really the solution, right? Currently it only allows you to specify all contents which is the option to make sure that it adds new content or you select specific repositories, which means you will have to add newly created repositories manually. So, we basically miss:

  • the option to exclude repositories from protection, preferably using dynamic rules.
  • the option to populate the repository using dynamic rules.

the current implementation, based on FR30, is very static and for customers using instance based licensing also very expensive as each repository consumes a VOI license. 

Badge +1

Yes. Aggree with you Onno.

I have already selected “All Repositories” but new created ones are not automatically added to the content.

The support told me that this will be fixed in SP30. Anyone knows when this SP will be available ?

Thank you,

 

 

Userlevel 7
Badge +19

Ahhh ok. So it's a feature😐Anyhow SP30 is available already. Unfortunately there are many naming patterns used to identify a specific release and in this case I assume they referred to SP30 which is also known as Platform Release 2023, internally it is named FR30. 

Reply