Differences

This shows you the differences between two versions of the page.

--- public:documents_and_guides:feasibility:backup_set_data_migration [2021/05/21 15:48]
yuk.cheng
+++ public:documents_and_guides:feasibility:backup_set_data_migration [2021/10/12 14:09] (current)
anam.gumba
@@ Line 8: / Line 8: @@
 ==== Introduction ====
-For partners who are planning to upgrade existing AhsayOBS v6 servers to AhsayCBS v8 or who have already upgraded from AhsayOBS v6 to AhsayCBS v8 and have not yet started or completed v6 to v8 backup set data migration, the conversion of v6 backup set data format to v8, 16 MB or 32 MB blocks format.  For more details on v8 data format and structure, please refer to the following article, [[http://wiki.ahsay.com/doku.php?id=public:8020_faq:faq_about_ahsay_cloud_backup_suite_8&s%5b%5d=block&s%5b%5d=format#Backup%20data%20are%20stored%20in%20new%20structure,%20can%20you%20explain%20on%20the%20new%20changes|FAQ: Frequently Asked Questions about Ahsay Cloud Backup Suite 8]].
+This feature will be of interest to partners who are planning to upgrade existing AhsayOBS v6 servers to AhsayCBS v8 or who have already upgraded from AhsayOBS v6 to AhsayCBS v8 and have not yet started or completed v6 to v8 backup set data migration, the conversion of v6 backup set data format to v8, 16 MB or 32 MB blocks format.  For more details on v8 data format and structure, please refer to the following article, [[http://wiki.ahsay.com/doku.php?id=public:8020_faq:faq_about_ahsay_cloud_backup_suite_8&s%5b%5d=block&s%5b%5d=format#Backup%20data%20are%20stored%20in%20new%20structure,%20can%20you%20explain%20on%20the%20new%20changes|FAQ: Frequently Asked Questions about Ahsay Cloud Backup Suite 8]].
 With the release of AhsayCBS v8.5.2.0 and above, the v6 to v8 backup set data migration has been enhanced to run in a separate process, it was originally included in the AhsayCBS Java process. This means the data migration job will not utilize the Java memory resources of AhsayCBS Java process, as the data migration thread will run in its own independent Java process with its own dedicated Java memory setting. The backup set data migration job will not affect the performance or stability of the AhsayCBS service, even if the data migration job crashes. In the event the data migration job where to hang or become unresponsive the system administrator can terminate the process from the operating system.
-As it is now a separate process, it is easier to allocate resources and to monitor the status of the data migration job. By default, the memory for the data migration is set to 1024 Java memory. However, the Java memory allocation can be customized by the system administrator.
+As it is now a separate process, it is easier to allocate resources and to monitor the status of the data migration job. By default, the memory for the data migration is set to 1024 MB Java memory. However, the Java memory allocation can be customized by the system administrator.
 The status of the data migration process can only be monitored from the operating system on the AhsayCBS server.
@@ Line 26: / Line 26: @@
-^ <color #670CFB>minimum Java heap size</color> | This is the minimum Java heap size setting of the data migration process.  The default value is 1024. |
+^ <color #670CFB>minimum Java heap size</color> | This is the minimum Java heap size setting of the data migration process.  The default value is 128 MB.  |
-^ <color #ff7f27>maximum Java heap size</color> | This is the maximum Java heap size setting of the data migration process.  The default value is 1024. |
+^ <color #ff7f27>maximum Java heap size</color> | This is the maximum Java heap size setting of the data migration process.  The default value is 1024 MB. |
 ^ <color #5E5D5A>Data Migration Process</color> | This identifies the process as the data migration process. |
 ^ <color #CFA408>Backup Set ID</color> | The backup set ID of the backup set currently undergoing data migration. |
@@ Line 47: / Line 47: @@
 == Linux ==
-In AhsayCBS for Linux you can use the <color #ed1c24>ps -ef|grep java</color> command to list all the processes using java to run.  This also starts with the username then the process ID to identify the running processes.  In the example below, username **root** with process ID **10370** is the Data Migration process.
+In AhsayCBS for Linux you can use the <color #ed1c24>ps -ef|grep java</color> command to list all the processes using java to run.  This also starts with the username then the process ID to identify the running processes.  In the example below, username **root** with process ID **10370** is the Data Migration process.  This is indicated by the min/max java heap size **-Xms128m -Xmx1024m**.
 | #root@centos-7-1810-temp ~]# <color #ed1c24>ps -ef|grep java</color>\\   \\  root      4905     1  0 17:12 ?        00:00:59 /usr/local/obm/jvm/bin/bschJW -Xms128m -Xmx768m -Dsun.nio.PageAlignDirectMemory=true -Djava.library.path=. -cp .:./cbs.jar cbs /usr/local/obm     \\   \\  root      9796     1 18 20:40 pts/0    00:01:41 /usr/local/cbs/java/bin/java -Djava.util.logging.config.file=/usr/local/cbs/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.library.path=/usr/local/cbs/lib/LinX64 -DCATALINA_PID=/var/run/obsr.pid -Xrs -Xms512m -Xmx2048m -Xss384k -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m -XX:MaxDirectMemorySize=512m -XX:NewRatio=3 -XX:SurvivorRatio=32 -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=80 -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseConcMarkSweepGC -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=85 -XX:+ScavengeBeforeFullGC -XX:+CMSScavengeBeforeRemark -Dsun.net.inetaddr.ttl=3600 -Dnetworkaddress.cache.ttl=3600 -Dsun.net.inetaddr.negative.ttl=300 -Dnetworkaddress.cache.negative.ttl=300 -Dsun.nio.PageAlignDirectMemory=true -Djava.net.preferIPv4Stack=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=conf/logging.properties -Dtc.work.path=work -Dtc.log.path=logs -Djavax.servlet.context.tempdir=work -Djdk.nio.maxCachedBufferSize=262144 -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.endorsed.dirs= -classpath /usr/local/cbs/tomcat/bin/bootstrap.jar:/usr/local/cbs/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/usr/local/cbs -Dcatalina.home=/usr/local/cbs/tomcat -Djava.io.tmpdir=/usr/local/cbs/temp org.apache.catalina.startup.Bootstrap start\\  \\  **root     10370**  9796 99 20:49 pts/0    00:00:04 /usr/local/cbs/java-linux-x64/bin/java -Xms128m -Xmx1024m -XX:MaxDirectMemorySize=1024m -Dsun.nio.PageAlignDirectMemory=true -Xrs -Djava.library.path=/usr/local/cbs/lib/LinX64 -cp /usr/local/cbs/lib/cbs.jar:/usr/local/cbs/lib/*:/usr/local/cbs/lib:/usr/local/cbs/tomcat/lib/* -Dcatalina.base=/usr/local/cbs RunDataMigration /usr/local/cbs **1620111338046** QgsSo/AkSjvTlOOVjcF/W9dcqxQKiFnVqI/A9Le/N0uvzIAFFlBJq1ZNFwlLKxfO3B8uWZiGl35vDj0DjScn8Q== QgsSo/AkSjvTlOOVjcF/W9dcqxQKiFnVqI/A9Le/N0te9GJsuIFiLYAh8wprdjBs QgsSo/AkSjvTlOOVjcF/W9dcqxQKiFnVqI/A9Le/N0sJtzhqrGM6IaxlRIL6+zjurGlJSNuslsqxg9vhbOvlNcM3Z9EaCwb7vMjHdMjKzVHxl/9zRmKcsCfovDWxFj8wa+yruhL0RYuOKuDdEqxcAw== QgsSo/AkSjvTlOOVjcF/W9dcqxQKiFnVqI/A9Le/N0vC/gEJqRt1LFZr1Iz3nkhpvKKt6o7TuA+cseUlimZXV4L4YYYN3w+0qYiyBDCM32Q= OBM 127.0.0.1 8081\\     \\    root     10397  9112  0 20:49 pts/0    00:00:00 grep --color=auto java|
@@ Line 57: / Line 57: @@
 In AhsayCBS for FreeBSD, there are two steps to check the Data Migration process.
-. First find the process ID using the <color #ed1c24>**ps –aux|grep java**</color> command.  To identify each process that is running, it also starts with the username then the process ID.  In the example below, username **root** with process ID **2706** is the Data Migration process.
+. First find the process ID using the <color #ed1c24>**ps –aux|grep java**</color> command.  To identify each process that is running, it also starts with the username then the process ID.  In the example below, username **root** with process ID **2706** is the Data Migration process.  This is indicated by the min/max java heap size **-Xms128m -Xmx1024m**.
 | #root@FREEBSD120X86:~ # <color #ed1c24>ps -aux|grep java</color>\\   \\  root       2163   3.0 21.2 2635284 660996  0  I    22:21    3:25.68 /usr/local/cbs/java/bin/java -Djava.util.logging.config.file=/usr/local/cbs/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -D     \\   \\  **root       2706**   0.0  0.9 1389572  27880  0  S    22:38    0:00.36 /usr/local/cbs/jvm/jre/bin/java -Xms128m -Xmx1024m -XX:MaxDirectMemorySize=1024m -Dsun.nio.PageAlignDirectMemory=true -Xrs -Djava.library.path=/usr/local/cbs/lib/FbdX86\\  \\   root       2708   0.0  0.1    4728   2228  0  S+   22:38    0:00.00 grep java|
@@ Line 70: / Line 70: @@
 In AhsayUBS, there are two steps to check the Data Migration process.
-. First find the process ID using the <color #ed1c24>**ps –aux|grep java**</color> command.  To identify each process that is running, it also starts with the username then the process ID.  In the example below, username **root** with process ID **77431** is the Data Migration process.
+. First find the process ID using the <color #ed1c24>**ps –aux|grep java**</color> command.  To identify each process that is running, it also starts with the username then the process ID.  In the example below, username **root** with process ID **77431** is the Data Migration process.  This is indicated by the min/max java heap size **-Xms128m -Xmx1024m**.
 | ahsayubs:~ # <color #ed1c24>ps -aux|grep java</color>\\   \\  **root 77431** 58.3 3.6 2703736 291176 - S 03:39 0:16.85 /ubs/mnt/esfmfw/obsr/system/obsr/java-freebsd-x64/bin/java -Xms128m -Xmx1024m -XX:MaxDirectMemorySize=1024m -Dsun.nio.PageAlignDirectMemory=true -Xrs -Djava.library.path     \\   \\  root 45832 0.2 11.3 4044324 924100 - I 09:07 22:43.51 /ubs/module/obsr/system/obsr/java-freebsd-x64/bin/java -Djava.util.logging.config.file=/ubs/module/obsr/system/obsr/conf/logging.properties -Djava.util.logging.manager=o \\  \\  root 77434 0.0 0.0 6740 2624 0 S+ 03:39 0:00.00 grep java |
@@ Line 84: / Line 84: @@
 ==== Setup and Configuration ====
-By default, the memory is set to 1024. This can be changed by appending the options “**<color #ed1c24>com.ahsay.obs.core.job.MigrateV6Data.Xmx=xxxx</color>**” for the maximum Java heap size and “**<color #ed1c24>com.ahsay.obs.core.job.MigrateV6Data.Xms=xxxx</color>**” for the minimum Java heap size in the cbs.opt file.
+By default, the memory is set to 1024 MB. This can be changed by appending the options “**<color #ed1c24>com.ahsay.obs.core.job.MigrateV6Data.Xmx=xxxx</color>**” for the maximum Java heap size and “**<color #ed1c24>com.ahsay.obs.core.job.MigrateV6Data.Xms=xxxx</color>**” for the minimum Java heap size in the **<color #ed1c24>cbs.opt</color>** file.
+If you wish to use the default Java heap size settings, then the additional options above are not required in the cbs.opt file.
 To configure follow the steps below:
@@ Line 94: / Line 96: @@
   - Locate the **cbs.opt** file in the $APPLICATION_HOME\conf folder.\\  {{public:documents_and_guides:windowscbsopt.png}}
-  - Open the file, add the options “**com.ahsay.obs.core.job.MigrateV6Data.Xmx=<color #ed1c24>value</color>**” and “**com.ahsay.obs.core.job.MigrateV6Data.Xms=<color #ed1c24>value</color>**” then save.\\  {{public:documents_and_guides:windowsoptions.png}}
+  - Open the file, add the options “**com.ahsay.obs.core.job.MigrateV6Data.Xmx=<color #ed1c24>value</color>**” and “**com.ahsay.obs.core.job.MigrateV6Data.Xms=<color #ed1c24>value</color>**” then save.\\  {{public:documents_and_guides:windowsoptions.png}}\\  For the Java heap size settings in the cbs.opt file, there is no need to specify “m”.
   - Restart the AhsayCBS service.\\  {{public:documents_and_guides:cbsservice.png?600}}

User Tools

Site Tools

Differences

Page Tools