Recent content by BkpAdmin

yes i have - it takes some time to find out what the rate of change is going to be on your disk during the time you run your backup. If you are performing the backup while users are accessing the filesystem - you must have a cache large enough to hold all the changes. Image level first backups...

Image level agest contains a system level driver with the potential to bluescreen your machine. Similiar to the level that AntiVirus software accesses your disk subsystem. CV may want to hit you with services due to that aspect. I happened to have them out here for another reason and they...

Frbutler - I had contacted my account rep and opened a case for this issue as well. When speaking with CV today they reported that this patch will be released loosely before sp4.

if you are doing a job based restore you will not notice any or very little latency from seeking because all the data from the backup is tossed back on the disk. That being said - if you select files from the browse in all different file locations you will definitely see the effect on recovery...

I think birky is correct - as long as it creates a new full index which i believe a synthetic does you should be good to go.

Multiplexing adds signifigant restore time.

You have to log in to the Commvault MA site to grab the patch. My understanding is that the downloader only grabs critical updates and service pack releases. Does anyone know why CV doesnt add all the updates within the downloader?

there seems to be atleast 10+ patches for SQL that I counted that are post sp2. Like dall said - get sp3 on ASAP.

have you upgraded your mag space or presented a mount point under your mag vol folder? You may also want to cycle both the Commcell and Media Agent services to see if that corrects this problem

yes it is a post sp3 patch.

Are you viewing the Commcell GUI from the Commcell itself or your desktop? There are GUI patches that need to be applied to workstations that have the GUI installed also - maybe this is causing the problem?

patch 658 fixes this problem. You have to apply the patch then run a full backup.

You have summed this entire thread up in this sentence "So what we are both saying is backup vendors suck, none of them have a decent product or QA." And I agree with you 100% :-)

let me quote it for you since you missed it "One major issue Veritas users cited with NetBackup 6.0 is that when a backup job indicates it's complete, it often has only backed up 1K files, so there's no data to restore" what this translates too is - Veritas reporting your 1TB job as complete...

Kluken - Your arguement is running out of steam as you seem shocked to find out there are bugs with software and your tout of switching to Veritas has been sullied by dataloss bugs on a grand scale which were known and not fixed for over a year. I have copied the article from Computer World...