SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Galaxy Data Classifiation Error
Author Message
Post Galaxy Data Classifiation Error 
Hi All:

I realize this is pretty obscure. We no longer have paid
support for CommVault Galaxy. I put in for it and it didn't get
approved last time around. Figured I'd ask the question here.

I got email from one of our support engineers in Japan. He was
on a customer visit recently and discovered that CommVault Data
Archiver was refusing to archive files on the J: Array. Because of
the way we have to do archiving, we have to use Data Classification.
DC was the real culprit. Here's the error from the GXHSMIfind.log.

"2124 11e4 08/05 00:12:20 4166 Error: DC Not Running; Db Path :
[J:J_db.db]; Error : [ReadWriteMutex::lockRead(124): -Warn--: Failed
to wait for Mutex-Read with WAIT_TIMEOUT; timeout=14400000; with
ErrNo=183; ReadCount=0]; FUNC : [run_sql_query] ID : [1382];"

What the engineer did was delete the existing J_db.db file so Galaxy
would be forced to do a scan and create a new copy. As far as I know
this solved the problem. What the engineer wanted to know is,
was there a chance the system could have righted itself if the
WAIT_TIMEOUT were increased? I searched the windows registry and
didn't see a WAIT_TIMEOUT key to modify. I think it's possible the
J_db.db database had become corrupt and nothing would have prevented
the need for a site visit. But, I'm speculating.

We're running Windows 2003 Server Standard R2 32-bit SP2 and Galaxy
7.0(Build76).

Thanks,

Dennis Herrick
Dennis_Herrick < at > hotmail.com ([email]Dennis_Herrick%40hotmail.com[/email])




__._,_.___
Reply to sender ([email]dherrick < at > ade.com?subject=Re%3A%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply via web post | Start a New Topic
Messages in this topic (1)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE
[url=http://global.ard.yahoo.com/SIG=15om3lsr4/M=791726.14818010.14570270.10835568/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1313545273/L=39f2b4e0-c861-11e0-8e10-0bbcc165e768/B=RyqOMtBDRmM-/J=1313538073093637/K=VekT4GASkpwQ5RYWjbe.sA/A=6449880/R=0/SIG=12u01en1m/*http://www.freecreditscore.com/dni/default.aspx?SiteVersionID=997&sc=671020&bcd=YGROUPS_Know]Know your score. Know what your credit strengths are. freecreditscore.com .[/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['RyqOMtBDRmM-']='&U=13cg178dj%2fN%3dRyqOMtBDRmM-%2fC%3d791726.14818010.14570270.10835568%2fD%3dMKP1%2fB%3d6449880%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=39f2b4e0-c861-11e0-8e10-0bbcc165e768&T=1ch9ch7rq%2fX%3d1313538073%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d3244036691%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9IjM5ZjJiNGUwLWM4NjEtMTFlMC04ZTEwLTBiYmNjMTY1ZTc2OCIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMxMzUzODA3MzA3MDg3OSIg%2fQ%3d-1%2fS%3d1%2fJ%3d25228962&U=13cg178dj%2fN%3dRyqOMtBDRmM-%2fC%3d791726.14818010.14570270.10835568%2fD%3dMKP1%2fB%3d6449880%2fV%3d1[/img]


Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=5260/stime=1313538072/nc1=5522130/nc2=4507179/nc3=5191952[/img]
__,_._,___

Post Galaxy Data Classifiation Error 
Whats special about the way you are doing archiving that requires you to use DC.

From: commvault < at > yahoogroups.com [mailto:commvault < at > yahoogroups.com] On Behalf Of dennisherrick
Sent: Tuesday, August 16, 2011 4:28 PM
To: commvault < at > yahoogroups.com
Subject: [commvault] Galaxy Data Classifiation Error





Hi All:

I realize this is pretty obscure. We no longer have paid
support for CommVault Galaxy. I put in for it and it didn't get
approved last time around. Figured I'd ask the question here.

I got email from one of our support engineers in Japan. He was
on a customer visit recently and discovered that CommVault Data
Archiver was refusing to archive files on the J: Array. Because of
the way we have to do archiving, we have to use Data Classification.
DC was the real culprit. Here's the error from the GXHSMIfind.log.

"2124 11e4 08/05 00:12:20 4166 Error: DC Not Running; Db Path :
[J:J_db.db]; Error : [ReadWriteMutex::lockRead(124): -Warn--: Failed
to wait for Mutex-Read with WAIT_TIMEOUT; timeout=14400000; with
ErrNo=183; ReadCount=0]; FUNC : [run_sql_query] ID : [1382];"

What the engineer did was delete the existing J_db.db file so Galaxy
would be forced to do a scan and create a new copy. As far as I know
this solved the problem. What the engineer wanted to know is,
was there a chance the system could have righted itself if the
WAIT_TIMEOUT were increased? I searched the windows registry and
didn't see a WAIT_TIMEOUT key to modify. I think it's possible the
J_db.db database had become corrupt and nothing would have prevented
the need for a site visit. But, I'm speculating.

We're running Windows 2003 Server Standard R2 32-bit SP2 and Galaxy
7.0(Build76).

Thanks,

Dennis Herrick
Dennis_Herrick < at > hotmail.com ([email]Dennis_Herrick%40hotmail.com[/email])






***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message in error,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************



__._,_.___
Reply to sender ([email]sukumara < at > commvault.com?subject=RE%3A%20%5Bcommvault%5D%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=RE%3A%20%5Bcommvault%5D%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply via web post | Start a New Topic
Messages in this topic (2)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=5261/stime=1313588823[/img]
__,_._,___

Post Galaxy Data Classifiation Error 
Hi Rajiv:

Our company's application collects data from measurement tools
and stores it in a SQL Server database. I tried to get our Engineers
to use the CommVault DATA Archive product in a standard way, such as
archive all the files that have collected in an array once a day.
While we have terabytes and terabytes of disk space for storage,
occasionally the engineers like to "selectively" prune data by
sending some of it over to a separate archive server to be rolled
to tape. The size and age of the files have no meaning in our
environment, so I can't make use of those rules. We don't stub
either, they consider this extra clutter. SQL keeps track of whether
the files are on the main server or on the archive server getting
ready to be archived. If the files aren't in either location, then
they're assumed to be on tape. Our engineers could even send a
portion of the files from a directory to be archived one night and
the remaining files a year later. It's completely unpredictable.
Everything is controlled by directories named according to year,
month, day and hour such as 2011-JAN-09-23. Right now I'm running
jobs according to year and month. Since I can't predict when the
engineers will archive a file, I have to run all the jobs ever
created every night, just to catch any old stragglers the engineers
may have sent over. Right now it's about 3 years worth or 36 jobs.

We sell the product and our customers insisted on this strategy.
They keep track of their production by year-month-day and hour.
They know what lots were processed on what day and if they need to
restore data from a certain lot, they run find. Files are in small
organized chunks on very few tapes and the recoveries take very
little time, around 20 minutes total. This is about 200% better
than what one customer was seeing for restore times and they're
thrilled and so are their customers.

I think the reason we use DataClassification is because we need to
use regular expressions and wild cards in our filters and I believe
Standard Archiving doesn't support this. Our local CommVault Field
Engineer suggested we try DC.

We don't like DC here much it seem kind of fragile.

Thanks,

Dennis

--- In commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]), Rajiv Kottomtharayil <sukumara < at > ...> wrote:

Whats special about the way you are doing archiving that requires you to use DC.

From: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])] On Behalf Of dennisherrick
Sent: Tuesday, August 16, 2011 4:28 PM
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Subject: [commvault] Galaxy Data Classifiation Error



Hi All:

I realize this is pretty obscure. We no longer have paid
support for CommVault Galaxy. I put in for it and it didn't get
approved last time around. Figured I'd ask the question here.

I got email from one of our support engineers in Japan. He was
on a customer visit recently and discovered that CommVault Data
Archiver was refusing to archive files on the J: Array. Because of
the way we have to do archiving, we have to use Data Classification.
DC was the real culprit. Here's the error from the GXHSMIfind.log.

"2124 11e4 08/05 00:12:20 4166 Error: DC Not Running; Db Path :
[J:J_db.db]; Error : [ReadWriteMutex::lockRead(124): -Warn--: Failed
to wait for Mutex-Read with WAIT_TIMEOUT; timeout=14400000; with
ErrNo=183; ReadCount=0]; FUNC : [run_sql_query] ID : [1382];"

What the engineer did was delete the existing J_db.db file so Galaxy
would be forced to do a scan and create a new copy. As far as I know
this solved the problem. What the engineer wanted to know is,
was there a chance the system could have righted itself if the
WAIT_TIMEOUT were increased? I searched the windows registry and
didn't see a WAIT_TIMEOUT key to modify. I think it's possible the
J_db.db database had become corrupt and nothing would have prevented
the need for a site visit. But, I'm speculating.

We're running Windows 2003 Server Standard R2 32-bit SP2 and Galaxy
7.0(Build76).

Thanks,

Dennis Herrick
Dennis_Herrick < at > ...<mailto:Dennis_Herrick%40hotmail.com>





******************Legal Disclaimer***************************
"This communication may contain confidential and privileged
material for the sole use of the intended recipient. Any
unauthorized review, use or distribution by others is strictly
prohibited. If you have received the message in error, please
advise the sender by reply email and delete the message. Thank
you."
*********************************************************



__._,_.___
Reply to sender ([email]dherrick < at > ade.com?subject=Re%3A%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply via web post | Start a New Topic
Messages in this topic (3)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=5263/stime=1313726794[/img]
__,_._,___

Post Galaxy Data Classifiation Error 
Hi Rahul:

Without paid support we don't have access to Galaxy version 9.0. I do have 8.0 here. I'm going to try to get support turned on again.
Unfortunately my Manager is on vacation, so I'll have to wait 2 weeks for approval. Anyway, here are a few sample filter rules. See below:

Find files where lowFreeVolume < 100
AND highFreeVolume < 100
AND (fileSize > 0 AND lastAccessedDays > 0 AND modifiedDays > 0 )
AND ( fullPath LIKE 'J:EncoFVStorage2008?_07?_%%' ESCAPE '?' )
AND ( fullPath NOT LIKE '%.bat'
AND fullPath NOT LIKE '%.cur'
AND fullPath NOT LIKE '%.dll'
AND fullPath NOT LIKE '%.exe'
AND fullPath NOT LIKE '%.ico'
AND fullPath NOT LIKE '%.lnk' ) AND (not attrs & 1 and not attrs &
2 and not attrs & 4 and not attrs & 16384 and not attrs & 4096) AND
Exfilter in ("GALAXY_DIR","WINDOWS_DIR","DC_DIR","SYSTEM_DIR")

This one is used to collect files from Jul 2008 for archive. I have no control over the directory structure naming. Our software engineers selected it in conjunction with our customers before we bought Data Archiver

And another:

Find files where lowFreeVolume < 100
AND highFreeVolume < 100
AND (fileSize > 0 AND lastAccessedDays > 0 AND modifiedDays > 0 )
AND ( fullPath LIKE 'J:EncoFVStorage2008?_06?_%%' ESCAPE '?' )
AND ( fullPath NOT LIKE '%.bat'
AND fullPath NOT LIKE '%.cur'
AND fullPath NOT LIKE '%.dll'
AND fullPath NOT LIKE '%.exe'
AND fullPath NOT LIKE '%.ico'
AND fullPath NOT LIKE '%.lnk' ) AND (not attrs & 1 and not attrs & 2 and not attrs & 4 and not attrs & 16384 and not attrs & 4096) AND Exfilter in ("GALAXY_DIR","WINDOWS_DIR","DC_DIR","SYSTEM_DIR")

This one is used to collect files from Jun 2008 for archive. Again, I have no control over the directory structure naming. Our software engineers selected it in conjunction with our customers before we bought Data Archiver

Thanks,

Dennis Herrick
Dennis_Herrick < at > hotmail.com ([email]Dennis_Herrick%40hotmail.com[/email])

----------------------------------------------------------

Hi Dennis,

Could you please send samples of some of the regex you use for content or the DC query you are using currently.

Please confirm if you would have access to version 9 of the product.

Regards

Rahul

--- In commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]), Rajiv Kottomtharayil <sukumara < at > ...> wrote:

Whats special about the way you are doing archiving that requires you to use DC.

From: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])] On Behalf Of dennisherrick
Sent: Tuesday, August 16, 2011 4:28 PM
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Subject: [commvault] Galaxy Data Classifiation Error



Hi All:

I realize this is pretty obscure. We no longer have paid
support for CommVault Galaxy. I put in for it and it didn't get
approved last time around. Figured I'd ask the question here.

I got email from one of our support engineers in Japan. He was
on a customer visit recently and discovered that CommVault Data
Archiver was refusing to archive files on the J: Array. Because of
the way we have to do archiving, we have to use Data Classification.
DC was the real culprit. Here's the error from the GXHSMIfind.log.

"2124 11e4 08/05 00:12:20 4166 Error: DC Not Running; Db Path :
[J:J_db.db]; Error : [ReadWriteMutex::lockRead(124): -Warn--: Failed
to wait for Mutex-Read with WAIT_TIMEOUT; timeout=14400000; with
ErrNo=183; ReadCount=0]; FUNC : [run_sql_query] ID : [1382];"

What the engineer did was delete the existing J_db.db file so Galaxy
would be forced to do a scan and create a new copy. As far as I know
this solved the problem. What the engineer wanted to know is,
was there a chance the system could have righted itself if the
WAIT_TIMEOUT were increased? I searched the windows registry and
didn't see a WAIT_TIMEOUT key to modify. I think it's possible the
J_db.db database had become corrupt and nothing would have prevented
the need for a site visit. But, I'm speculating.

We're running Windows 2003 Server Standard R2 32-bit SP2 and Galaxy
7.0(Build76).

Thanks,

Dennis Herrick
Dennis_Herrick < at > ...<mailto:Dennis_Herrick%40hotmail.com>





******************Legal Disclaimer***************************
"This communication may contain confidential and privileged
material for the sole use of the intended recipient. Any
unauthorized review, use or distribution by others is strictly
prohibited. If you have received the message in error, please
advise the sender by reply email and delete the message. Thank
you."
*********************************************************



__._,_.___
Reply to sender ([email]dherrick < at > ade.com?subject=Re%3A%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20Galaxy%20Data%20Classifiation%20Error[/email]) | Reply via web post | Start a New Topic
Messages in this topic (4)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE
[url=http://global.ard.yahoo.com/SIG=15o02m5tm/M=791726.14818010.14570270.10835568/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1313827369/L=089982be-caf2-11e0-8078-b372e2e5ee90/B=lM52NdBDRuk-/J=1313820169605563/K=2c3esfNW4Q2wpQLFit0cKQ/A=6449876/R=0/SIG=130kfcsn4/*http://www.freecreditscore.com/dni/default.aspx?SiteVersionID=997&sc=671020&bcd=YGROUPS_Bad598]A bad score is 598. A bad idea is not checking yours, at freecreditscore.com.[/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['lM52NdBDRuk-']='&U=13cl37iil%2fN%3dlM52NdBDRuk-%2fC%3d791726.14818010.14570270.10835568%2fD%3dMKP1%2fB%3d6449876%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=089982be-caf2-11e0-8078-b372e2e5ee90&T=1chumg32o%2fX%3d1313820169%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d1809131972%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9IjA4OTk4MmJlLWNhZjItMTFlMC04MDc4LWIzNzJlMmU1ZWU5MCIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMxMzgyMDE2OTYyOTI4OCIg%2fQ%3d-1%2fS%3d1%2fJ%3d28228962&U=13cl37iil%2fN%3dlM52NdBDRuk-%2fC%3d791726.14818010.14570270.10835568%2fD%3dMKP1%2fB%3d6449876%2fV%3d1[/img]


Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=5264/stime=1313820169/nc1=5191954/nc2=4025321/nc3=4507179[/img]
__,_._,___

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB