Backup Central

From what I've gathered from previous posts, checkpointing can be
achieved in v9 by setting up an Intermediate Cache, and using
transaction logging.

I've defined an Intermediate Cache Directory on each of our MediaAgents
which share (via network) our Index Cache. I've made sure that the "Use
shared profile if present with transaction logging" is selected in the
job Schedule policy. Yet when I look at the UpdateIndex.log for the
job, I see that Checkpointing is not enabled:

1302450 UPDATEINDEX: Effective failover flags are:
UseCatalogServer=TRUE, UseTransactionLogs=TRUE, Checkpointing=FALSE

What am I missing?

__._,_.___
Reply to sender ([email]georgeh < at > msu.edu?subject=Re%3A%20Job%20checkpointing%20in%20v9[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20Job%20checkpointing%20in%20v9[/email]) | Reply via web post | Start a New Topic
Messages in this topic (1)
Recent Activity:

• New Members 2

Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE

[url=http://global.ard.yahoo.com/SIG=15oero5o7/M=493064.14543979.14562481.13298430/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1320772232/L=cdaa675e-0a1b-11e1-89ac-33734f002aca/B=jzELItBDRqw-/J=1320765032818978/K=tZ1uJAbrrcR7U9vOb5wTYg/A=6060255/R=0/SIG=1194m4keh/*http://us.toolbar.yahoo.com/?.cpdl=grpj]Stay on top of your group activity without leaving the page you're on - Get the Yahoo! Toolbar now.[/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['jzELItBDRqw-']='&U=13cb8ej2p%2fN%3djzELItBDRqw-%2fC%3d493064.14543979.14562481.13298430%2fD%3dMKP1%2fB%3d6060255%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=cdaa675e-0a1b-11e1-89ac-33734f002aca&T=1chncppu4%2fX%3d1320765032%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d2857154115%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9ImNkYWE2NzVlLTBhMWItMTFlMS04OWFjLTMzNzM0ZjAwMmFjYSIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMyMDc2NTAzMjg3MjA3NSIg%2fQ%3d-1%2fS%3d1%2fJ%3d9E238962&U=13cb8ej2p%2fN%3djzELItBDRqw-%2fC%3d493064.14543979.14562481.13298430%2fD%3dMKP1%2fB%3d6060255%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=5361/stime=1320765032/nc1=5758220/nc2=4025291/nc3=4507179[/img]
__,_._,___

Hey George,
Looks correct given it says TRUE for the transaction logs option.
Granted it's not a feature I use myself, but quickly looking at BOL seems to show that the previous method ("Index Checkpointing") has been replaced with the new Catalog Server/Index Cache Server transaction log method, so seeing "Checkpointing=FALSE" would also appear to be correct.
(From v9 BOL < at > documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/prod_info/features.htm?var1=http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/features/index/index_cache.htm#Index_Check_Pointing)
Index Check Pointing
Index Check Pointing option, which provided job restartability in failover scenarios, is a deprecated feature in this release. On upgraded clients, if you have been using the index check pointing feature in the previous release, then you might continue to see the option in the Advanced Backup Options - Data tab. We strongly recommend that you disable this option and use Catalog Server with transaction logging feature instead. For more information on using this feature, see Using Index Cache Server for Job Restarts in Failover Scenarios
Cheers,
Luke On Nov 9, 2011 2:10 AM, "George Haddad" <georgeh < at > msu.edu ([email]georgeh < at > msu.edu[/email])> wrote:

__._,_.___
Reply to sender ([email]kaneda.san.sec < at > gmail.com?subject=Re%3A%5Bcommvault%5D%20Job%20checkpointing%20in%20v9[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%5Bcommvault%5D%20Job%20checkpointing%20in%20v9[/email]) | Reply via web post | Start a New Topic
Messages in this topic (2)
Recent Activity:

• New Members 2

Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE

[url=http://global.ard.yahoo.com/SIG=15op6d0b1/M=493064.14543979.14562481.13298430/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1320773344/L=64010f9e-0a1e-11e1-a77e-b74a5c2c086a/B=Q5DcIdBDRv4-/J=1320766144121249/K=.Xu75K08nQBLqEwnFjzWXA/A=6060255/R=0/SIG=1194m4keh/*http://us.toolbar.yahoo.com/?.cpdl=grpj]Stay on top of your group activity without leaving the page you're on - Get the Yahoo! Toolbar now.[/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['Q5DcIdBDRv4-']='&U=13c1kc518%2fN%3dQ5DcIdBDRv4-%2fC%3d493064.14543979.14562481.13298430%2fD%3dMKP1%2fB%3d6060255%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=64010f9e-0a1e-11e1-a77e-b74a5c2c086a&T=1ch1p6f4r%2fX%3d1320766144%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d2168096296%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9IjY0MDEwZjllLTBhMWUtMTFlMS1hNzdlLWI3NGE1YzJjMDg2YSIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMyMDc2NjE0NDA5MTY4MiIg%2fQ%3d-1%2fS%3d1%2fJ%3d9E238962&U=13c1kc518%2fN%3dQ5DcIdBDRv4-%2fC%3d493064.14543979.14562481.13298430%2fD%3dMKP1%2fB%3d6060255%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=5362/stime=1320766143/nc1=5741391/nc2=4507179/nc3=4025373[/img]
__,_._,___

I'm thinking that is the case Luke, since the CVD logs on the MAs show entries like this:

1324 ee0 11/08 08:48:45 1302451 6783590-7643810 [DSBACKUP ] Updating the Job Manager that the chunk has been committed
1324 ee0 11/08 08:48:45 1302451 6783590-7643810 [DSBACKUP ] The RESTART STRING Sent to Indexing: [ -o 3|141336296] for Offset: 544646495455
1324 ee0 11/08 08:48:45 1302451 IDXCONNECT: afile (2,10,2789993) is valid through offset 544646495455
1324 ee0 11/08 08:48:46 1302451 6783590-7643810 [DSBACKUP ] The RESTART STRING IS [ -o 3|141336296]
1324 ee0 11/08 08:48:46 1302451 6783590-7643810 [DSBACKUP ] Sending Indexing Restart Point XML to JM. XML = [<?xml version="1.0" encoding="UTF-8" standalone="no" ?><Indexing_IndexingBackupRestartInformation cntOpensForWrite="2" status="0"/>]


On 11/8/2011 10:29 AM, Luke wrote:
Hey George,
Looks correct given it says TRUE for the transaction logs option.
Granted it's not a feature I use myself, but quickly looking at BOL seems to show that the previous method ("Index Checkpointing") has been replaced with the new Catalog Server/Index Cache Server transaction log method, so seeing "Checkpointing=FALSE" would also appear to be correct.
(From v9 BOL < at > documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/prod_info/features.htm?var1=http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/features/index/index_cache.htm#Index_Check_Pointing)
Index Check Pointing
Index Check Pointing option, which provided job restartability in failover scenarios, is a deprecated feature in this release. On upgraded clients, if you have been using the index check pointing feature in the previous release, then you might continue to see the option in the Advanced Backup Options - Data tab. We strongly recommend that you disable this option and use Catalog Server with transaction logging feature instead. For more information on using this feature, see Using Index Cache Server for Job Restarts in Failover Scenarios
Cheers,
Luke On Nov 9, 2011 2:10 AM, "George Haddad" <georgeh < at > msu.edu ([email]georgeh < at > msu.edu[/email])> wrote:





__._,_.___
Reply to sender ([email]georgeh < at > msu.edu?subject=Re%3A%20%5Bcommvault%5D%20Job%20checkpointing%20in%20v9[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20%5Bcommvault%5D%20Job%20checkpointing%20in%20v9[/email]) | Reply via web post | Start a New Topic
Messages in this topic (3)
Recent Activity:

• New Members 2

Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE

[url=http://global.ard.yahoo.com/SIG=15ohmnv93/M=493064.14543979.14562481.13298430/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1320776249/L=277e398c-0a25-11e1-982c-7f94a15d18f5/B=aiH7INj8fXs-/J=1320769049115115/K=sK30rV.7UJIIFwvUEfFYyQ/A=6060255/R=0/SIG=1194m4keh/*http://us.toolbar.yahoo.com/?.cpdl=grpj]Stay on top of your group activity without leaving the page you're on - Get the Yahoo! Toolbar now.[/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['aiH7INj8fXs-']='&U=13cdc08j5%2fN%3daiH7INj8fXs-%2fC%3d493064.14543979.14562481.13298430%2fD%3dMKP1%2fB%3d6060255%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=277e398c-0a25-11e1-982c-7f94a15d18f5&T=1ch0kfleb%2fX%3d1320769049%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d2996408298%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9IjI3N2UzOThjLTBhMjUtMTFlMS05ODJjLTdmOTRhMTVkMThmNSIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMyMDc2OTA0OTA0ODAyMyIg%2fQ%3d-1%2fS%3d1%2fJ%3d29228962&U=13cdc08j5%2fN%3daiH7INj8fXs-%2fC%3d493064.14543979.14562481.13298430%2fD%3dMKP1%2fB%3d6060255%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=5363/stime=1320769048/nc1=5191953/nc2=4507179/nc3=4025373[/img]
__,_._,___

I use the checkpointing feature by turning it on in the Registry. I did have a question in relation to this problem though. I've been having a hell of a tough time seeding my global deduplication database, and while troubleshooting it with support, I seem to remember that it was a good thing that I'm just using Shared Index instead of a Catalog.

That said, I have dozens of index cache problems every day (I run over 600 jobs per night over 5 MA's with a shared index cache on our EMC NAS). Intermediate IndexCache didn't really help things there. The problems just changed.

George Haddad <georgeh < at > msu.edu> 11/8/2011 8:17 AM >>>

I'm thinking that is the case Luke, since the CVD logs on the MAs show entries like this:

1324 ee0 11/08 08:48:45 1302451 6783590-7643810 [DSBACKUP ] Updating the Job Manager that the chunk has been committed
1324 ee0 11/08 08:48:45 1302451 6783590-7643810 [DSBACKUP ] The RESTART STRING Sent to Indexing: [ -o 3|141336296] for Offset: 544646495455
1324 ee0 11/08 08:48:45 1302451 IDXCONNECT: afile (2,10,2789993) is valid through offset 544646495455
1324 ee0 11/08 08:48:46 1302451 6783590-7643810 [DSBACKUP ] The RESTART STRING IS [ -o 3|141336296]
1324 ee0 11/08 08:48:46 1302451 6783590-7643810 [DSBACKUP ] Sending Indexing Restart Point XML to JM. XML = [<?xml version="1.0" encoding="UTF-8" standalone="no" ?><Indexing_IndexingBackupRestartInformation cntOpensForWrite="2" status="0"/>]


On 11/8/2011 10:29 AM, Luke wrote:
Hey George,
Looks correct given it says TRUE for the transaction logs option.
Granted it's not a feature I use myself, but quickly looking at BOL seems to show that the previous method ("Index Checkpointing") has been replaced with the new Catalog Server/Index Cache Server transaction log method, so seeing "Checkpointing=FALSE" would also appear to be correct.
(From v9 BOL < at > documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/prod_info/features.htm?var1=http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/features/index/index_cache.htm#Index_Check_Pointing)
Index Check Pointing
Index Check Pointing option, which provided job restartability in failover scenarios, is a deprecated feature in this release. On upgraded clients, if you have been using the index check pointing feature in the previous release, then you might continue to see the option in the Advanced Backup Options - Data tab. We strongly recommend that you disable this option and use Catalog Server with transaction logging feature instead. For more information on using this feature, see Using Index Cache Server for Job Restarts in Failover Scenarios
Cheers,
Luke On Nov 9, 2011 2:10 AM, "George Haddad" <georgeh < at > msu.edu ([email]georgeh < at > msu.edu[/email])> wrote: