AcronisBackupRecoveryAdvancedServer's snapapi tossing notes

Objective: to back up the entire hard disk in a modified linux (modified based on centos5.4 and re-compiled the kernel), the hard disk is partitioned by LVM. Actually, I have already created a P2V image through vmwareconvert, but I still don't want to be reconciled, hoping to be a P2P image... objective: to back up the entire hard disk in a modified linux (modified based on centos 5.4 and re-compiled the kernel) system and create an LVM partition. In fact, I have already made a P2V image through vmware convert, but I am still unwilling to do so, hoping to create a P2P image.
 
If there is no LVM, this is very simple. If DD comes out, DD will go back, but Y does LVM (the default partitioning method of centos/RHEL), and I have very limited knowledge of LVM, there is only another way out: commercial backup programs-> acronis backup & recovery advanced server
 
Previous tossing:
 
1. the download of the linux agent is concealed. you must receive a prompt during server installation. Finally, you can download it from the portal that has registered the trial version.
 
2. you must install kernel-devel and gcc to install snapapi.
 
Finally, we found that we had to install an acronis LKM called snapapi to back up the LVM partition. Therefore, I am facing the following situations:
 
1. there may be no code for the current kernel, or a configuration file for the current kernel
 
2. kernel code of similar versions
 
3. have his LKM code
 
Error message:
 
[18458.932501] snapapi26: version magic '2. 6.18-164.15.1.el5.xxx SMP mod_unload 686 REGPARM 4 KSTACKS gcc-4.1 'shoshould be' 2. 6.18-164.15.1.el5.xxx SMP mod_unload 686 REGPARM gcc-4.1 ′
 
Analysis:
 
Modversion modmagic is inconsistent. The difference is that there is an extra 4 KSTACKS, and the LKM needs to be forcibly inserted.
 
 
 
Ideas:
 
1. remove the 4KSTACKS character
 
1. modify the binary file forcibly. I tried it with UE. ctrl + d deleted unnecessary characters and the result failed. The binary editor made by VI is not used, and files cannot be stored. the subsequent method is to find a better binary editor or modversion cracker that supports ELF files.
 
[1, 20218.918997] Verify ELF error [sec 1] (assertion 143)
[20218.919000] Module failed ELF checks
 
II. strong LKM insertion
 
1. modprobe-f parameter, system crash
 
2. remove modversion support when compiling LKM, just like adore-ng
 
This is a very foreign thing. the LKM compiled with dkms is now familiar with dkms. For more information, see
 
Http://kb.acronis.com/content/15649
 
Http://forum.acronis.com/forum/20374
 
From subaozi