Scratch my previous Comment, at least partially.Found the two reasons why it stopped working for me.CV uses the global http Proxy even if the selected VSA Proxy could directly contact the Kubernetes Cluster. our Proxy currently has issues and that’s why this connection was dropped. Option to specify Web-Proxy on case-to-case base would be better, especially for multi-tenant Envs or segregated Networks. CommServe Database lost the Secret Key; vdiscovery.log stated “Credentials incomplete for x”. and Attribute “K8s Secret Key” in App_InstanceProp Table was empty all the sudden. Sidenote: the key is saved in plain-text in this field, shouldn’t that be at least encoded or encrypted like all other passwords?
Looks a lot like the guide I found on Oracles KB, even the tickmarks are placed identical :-)Ended up using belows Variant for use in Powershell, using Namespace default did not work for me, so settled for kube-system.kubectl -n kube-system create serviceaccount backup-service-accountkubectl create clusterrolebinding backup-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:backup-service-account$TOKENNAME=kubectl -n kube-system get serviceaccount/backup-service-account -o jsonpath='{.secrets[0].name}'$TOKEN = kubectl -n kube-system get secret $TOKENNAME -o jsonpath='{.data.token}'$DECODEDTOKEN=[Text.Encoding]::Utf8.GetString([Convert]::FromBase64String($TOKEN))kubectl config set-credentials backup-service-account --token=$DECODEDTOKENkubectl config set-context --current --user=backup-service-accountThat worked out fine for a Day, after that the Token apparently expired. So there must be some Value I missed to tweak. Could redo the procedure above and re-add the Tok
you should never defrag SAN-LUNs, that only causes massive load on the Storage without doing anything for performance. Storage Boxes manage the logical blocks themselves and use their own logic to keep access fast.
Hi Monty. What kind of Storage do you use? If you are on a external SAN-Storage or a local RAID-Array I would caution against using Defragmentation Tools, same with SSD/Flash Storage.On local standalone Disks defragmentation can help. In my Envs we decided to skip that step for now and rely on Commvaults use of Sparsefiles and defragmenting those files if they get too sparse. If you use that external defrag can be contraproductive.
Default Limit for a single MediaAgent is 100, but depending on your Hardware-Sizing and other tasks the Server runs in addition, like VSA Processing, IndexServer, etc, this might already be too much. Or your servers are bored-out and you can set it up to 200, suggest to increase Memory usage in ctsrvr.cfg if you go that route, defaults there are rather conservative.
Hi MikeThat's where “Completed with Warnings” would come into play for me.Everything backed up fine: CompletedSome minor or non critical files not backed up: Completed with WarningsSome major or critical files not backed up: Completed with ErrorMajor parts of Backup or System Writers failed: FailedCVDB knows the StatusName but havn’t seen it used in action yet, nor is it available as Option in Error Threshold Roles.
Experienced incomplete and outdated Data before in CommandCenter, main reason why I only use it if not other option is available. Didn’t know the Ctrl+F5 Trick, thanks for sharing!
Same question here. Best guess would be someone didn’t like to see so many Failed or CWE Jobs so they requested this “solution” to hide the minor issues.Even considers Job ok if CommServe Services failed to be backed up, or most other parts of SystemWriters.Though that bug should finally be fixed in next HPK.Personal Solution/Workaround: Alert that goes of on specific SystemWriter Events and triggers Workflow to fix Issues , create Ticket with Server-Owner, or just send an Info-Mail to us for further checking.
We finally got an accurate progress bar for restores for VM machines in SP5/SP6 of V11 (that is an eternity ago now), before then we’d get a lot of support cases of customers assuming something was broken as the progress bar would go from 5% to 85% and nothing inbetween. Lots of those little things have been sorted out, but still room for improvement, obviously. Unfortunately that Progress bar is broken again with VSA Index v2, especially on File Restores. There it is even worse, the Restore may do nothing for hours until the Persistent Recovery is done counting files to restore. So far this takes the crown for confusing customers in my book
Thanks for the Info Mike!Didn’t see that in the Changes in FeatureRelease 21 Documentation. Shouldn’t that be noted there as well for everybody to be aware?Was that a change already known when FR21 was released half a year ago?Will there be any kind of Warning or Error Event thrown to inform Admins about this deprecated Config, allowing them to act?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.