Recent content by JG5

Hot Add mode will utilize the IO stack of the physical ESX server, so that may not be the most efficient method depending on the number of virtual machines. VCB works, but the snapshot has to be copied from the datastore and staged on the proxy server prior to backup. This may increase your...

You can try increasing the number of streams configured on the storage policy that writes to disk. Also make sure the writers to streams ratio is correct.

CDR is similar to other replication software in that it replicates at the byte level. Remote backup will accomplish roughly the same objective, but you would have to perform a restoration of the data from the Commvault side. CDR will allow you to have replicated data in it's native format...

Just tested the method you mentioned and it works fine. Guess I was wrong about the individual key method - been years since I tried that. Thanks for the help.

One of my developers asked me if the registry gets backed up every night to which I replied yes. I've always known this was included as part of the system state restore, and when I was on 5.9, I could have sworn that I was able to recover individual keys if needed. As a test, I restored the...

I got the info from a combination of all you mentioned. I agree, the books online leaves a lot to be desired. Most of the time I just use the search function rather than drilling down through the whole thing. I also use the online knowledge base. It can sometimes be useful.

Don't get rid of them. I presume these are larger than normal because you are doing brick level exchange backups? If so, this will definitely generate more log files compared to a database level backup. These files are needed to keep track of the job history. You can relocate them to a...

Data aging will only age jobs that have completed the copy process - it will not age partially copied jobs, or the partial data. If you kill an aux copy, it will pick up where it left off. In fact, if you kill it, you can look at your jobs in storage policy copies and it will show as...

Hi there. I've been using Gridstor for quite some time now with good results. I'll try to address some of your concerns. I have 6 media agents, all of which have SAN attached libraries - not shared among each other. My commserve is also a media agent with an LTO library attached - this is...

You can only change the job results folder in the properties - it will still leave behind the base, cvupdates, log files and updates directory - which take up the most space. To move all of these, he would need to uninstall and reinstall the agent to a different drive.

You can simply uninstall the agent via add/remove programs (assuming it's a windows box) and then run the installation for the agent and specify a different drive when it asks you for the location.

I actually ran a few tests and validated just what you said, but forgot to post back until I got the notification. Thanks for the reply.

All of my magnetic primary storage policies have a synchronous aux copy to secondary disk. The primary copy is set for 1 week retention, and the secondary for 28 days. If I manually prune the only full copy from a primary storage policy, the next backup will be forced full - makes sense. My...

If you have version 7.0, just use Disc 1 and run the setup.exe. I can't remember exactly what it was in 5.9 and 6.1, but I think there was a separate disc for the agents with both of those versions - in any event, each disc should have its contents printed on it. Hope this helps. Thanks.

Good point and I will keep that in mind. All of my secondary disk copies and subsequent tape copies are made from the Commserve, which is also a media agent. I treat the primary magnetic media as a spool copy more or less, although I don't have it configured that way. So, worst case scenario...