Comprehensive data protection for all workloads
Post Reply
kbossak
Novice
Posts: 6
Liked: never
Joined: Mar 06, 2017 10:48 pm
Full Name: Kerry Bossak
Contact:

Accidentally made a second Cloud Repository from same Service Provider

Post by kbossak »

I kept getting 'unable to connect to datastore' errors on our cloud service provider backup jobs after upgrading to the latest version.

I reconnected the service provider and for some reason it made a second Cloud Repository.

https://drive.google.com/file/d/1SkHEJY ... sp=sharing

If I scan the first one that shows it has 604 GB of used space, it just fails.

https://drive.google.com/file/d/1oL4HPO ... sp=sharing

The second one scans fine, but it keeps showing no space used. My question is, if I remove the first one and back up something to the new one, will it know I have cloud backups there?
Gostev
Chief Product Officer
Posts: 31806
Liked: 7300 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Accidentally made a second Cloud Repository from same Service Provider

Post by Gostev »

Hohestly, it would be less risky to have support review the situation and make sure to delete the "correct" repository. This could potentially be the situation when configuration database edits may potentially be required, due to conflicting records already present there. Thanks!
Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Bing [Bot], Google [Bot], tyler.jurgens and 224 guests