Backup into file system

Question

Hi
Setting backup-storage with the follwoing configuration is not generating backup files under said location - we are pumping huge volume of data and data(few GB) is not getting backuped up into file system - can you let me know if what is that I missing here?
Thanks
sunder
<distributed-scheme>
     <scheme-name>distributed-Customer</scheme-name>
     <service-name>DistributedCache</service-name>
     <!-- <thread-count>5</thread-count> -->
     <backup-count>1</backup-count>
     <backup-storage>
     <type>file-mapped</type>
     <directory>/data/xx/backupstorage</directory>
     <initial-size>1KB</initial-size>
     <maximum-size>1KB</maximum-size>
     </backup-storage>
     <backing-map-scheme>
          <read-write-backing-map-scheme>
               <scheme-name>DBCacheLoaderScheme</scheme-name>
               <internal-cache-scheme>
               <local-scheme>
                    <scheme-ref>blaze-binary-backing-map</scheme-ref>
               </local-scheme>
               </internal-cache-scheme>
               <cachestore-scheme>
                    <class-scheme>
                         <class-name>com.xxloader.DataBeanInitialLoadImpl
                         </class-name>
                         <init-params>
                              <init-param>
                                   <param-type>java.lang.String</param-type>
                                   <param-value>{cache-name}</param-value>
                              </init-param>
                              <init-param>
                                   <param-type>java.lang.String</param-type>
                                   <param-value>com.xx.CustomerProduct
                                   </param-value>
                              </init-param>
                              <init-param>
                                   <param-type>java.lang.String</param-type>
                                   <param-value>CUSTOMER</param-value>
                              </init-param>
                         </init-params>
                    </class-scheme>
               </cachestore-scheme>
               <read-only>true</read-only>
          </read-write-backing-map-scheme>
     </backing-map-scheme>
     <autostart>true</autostart>
</distributed-scheme>
<local-scheme>
<scheme-name>blaze-binary-backing-map</scheme-name>
<high-units>{back-size-limit 1}</high-units>
<unit-calculator>BINARY</unit-calculator>
<expiry-delay>{back-expiry 0}</expiry-delay>
<cachestore-scheme></cachestore-scheme>
</local-scheme>

Answer 1

Hi
We did try out with the following configuration
<near-scheme>
     <scheme-name>blaze-near-HeaderData</scheme-name>
<front-scheme>
<local-scheme>
<eviction-policy>HYBRID</eviction-policy>
<high-units>{front-size-limit 0}</high-units>
<unit-calculator>FIXED</unit-calculator>
<expiry-delay>{back-expiry 1h}</expiry-delay>
<flush-delay>1m</flush-delay>
</local-scheme>
</front-scheme>
<back-scheme>
<distributed-scheme>
<scheme-ref>blaze-distributed-HeaderData</scheme-ref>
</distributed-scheme>
</back-scheme>
<invalidation-strategy>present</invalidation-strategy>
<autostart>true</autostart>
</near-scheme>
<distributed-scheme>
<scheme-name>blaze-distributed-HeaderData</scheme-name>
<service-name>DistributedCache</service-name>
<partition-count>200</partition-count>
<backing-map-scheme>
<partitioned>true</partitioned>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<external-scheme>
<high-units>20</high-units>
<unit-calculator>BINARY</unit-calculator>
<unit-factor>1073741824</unit-factor>
<nio-memory-manager>
<initial-size>1MB</initial-size>
<maximum-size>50MB</maximum-size>
</nio-memory-manager>
</external-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>
com.xx.loader.DataBeanInitialLoadImpl
</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>{cache-name}</param-value>
</init-param>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>com.xx.bean.HeaderData</param-value>
</init-param>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>SDR.TABLE_NAME_XYZ</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
</read-write-backing-map-scheme>
</backing-map-scheme>
<backup-count>1</backup-count>
<backup-storage>
<type>off-heap</type>
<initial-size>1MB</initial-size>
<maximum-size>50MB</maximum-size>
</backup-storage>
<autostart>true</autostart>
</distributed-scheme>
With configuration the amount of residual main memory consumption is like 15 G.
When we changed this configuration to
<near-scheme>
     <scheme-name>blaze-near-HeaderData</scheme-name>
<front-scheme>
<local-scheme>
<eviction-policy>HYBRID</eviction-policy>
<high-units>{front-size-limit 0}</high-units>
<unit-calculator>FIXED</unit-calculator>
<expiry-delay>{back-expiry 1h}</expiry-delay>
<flush-delay>1m</flush-delay>
</local-scheme>
</front-scheme>
<back-scheme>
<distributed-scheme>
<scheme-ref>blaze-distributed-HeaderData</scheme-ref>
</distributed-scheme>
</back-scheme>
<invalidation-strategy>present</invalidation-strategy>
<autostart>true</autostart>
</near-scheme>
<distributed-scheme>
<scheme-name>blaze-distributed-HeaderData</scheme-name>
<service-name>DistributedCache</service-name>
<partition-count>200</partition-count>
<backing-map-scheme>
<partitioned>true</partitioned>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<external-scheme>
<high-units>20</high-units>
<unit-calculator>BINARY</unit-calculator>
<unit-factor>1073741824</unit-factor>
<nio-memory-manager>
<initial-size>1MB</initial-size>
<maximum-size>50MB</maximum-size>
</nio-memory-manager>
</external-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>
com.xx.loader.DataBeanInitialLoadImpl
</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>{cache-name}</param-value>
</init-param>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>com.xx.bean.HeaderData</param-value>
</init-param>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>SDR.TABLE_NAME_XYZ</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
</read-write-backing-map-scheme>
</backing-map-scheme>
<backup-count>1</backup-count>
<backup-storage>
<type>file-mapped</type>
<initial-size>1MB</initial-size>
<maximum-size>100MB</maximum-size>
<directory>/data/xxcache/blazeload/backupstorage</directory>
<file-name>{cache-name}.store</file-name>
</backup-storage>
<autostart>true</autostart>
</distributed-scheme>
Note backup storage is file-mapped
<backup-storage>
<type>file-mapped</type>
<initial-size>1MB</initial-size>
<maximum-size>100MB</maximum-size>
<directory>/data/xxcache/blazeload/backupstorage</directory>
<file-name>{cache-name}.store</file-name>
</backup-storage>
We still see that process residual main memory consumption is 15 G and we also see that /data/xxcache/blazeload/backupstorage folder is empty.
Wanted to check where does backup storage maintains the information - we would like offload this to flat file.
Appreciate any pointers in this regard.
Thanks
sunder