How to Recover Corrupted Linux using Veritas System Recovery 18
Good Day. I have to test how to recover a corrupted linux system using VSR18 for linux. Below are the specs of the unit. OS: Rhel 7.3 Disk: 2x500 GB (Raid 1) I already peformed a backup of all volumes before corrupting the system. After corrupting the file system, the 2 disks (sda and sdb) became unknown, LVM disk (for OS) was gone.LVM disk(for swap) was also gone. With this i would like to know if what steps i will take to recover the system. Question 1. Do i have to partition first the unknowndisks (sda and sdb)? Boot was located at the the 2 disks and create a LVM partition afterwards? 2. Was the Raid 1 Configuration already gone due to corruption?
restore linux backup on a linux physical system without os
Hi i have installed Sym_System_Recovery_2013R2_3.1.0.53611_Linux_Edition.tar.gz on one of my physcal linux server now i want to know can i get full backup from my physical server and when all of my data on physical server delet now if i have a symantec recovery disk can i recover my system with that full backup and os boot after backup restored ? Best regards
Symantec Recovery Disk
I need to restore a linux server red hat enterprise 5, I have the symantec recovery disk and images files are in a Windows 2003 file server, I can bootfrom cd,I configure network interface, but I dont know how findthe images files. How can Iconnect to shared resources in the Windows server? Ireachserver with ping command. I am basic linux user.booting from a cloned hard on a laptop
Hi, I cloned a linux CentOS hard drive of a server PC which included a LVM. Then I connected my external hard to the usb port of my laptop. I wanted to boot my laptop from the CentOS of external hard so i could use the programs which were installed on PC.So I restarted the laptop and press F11 button to select the desired OS. I can see the CentOS of external hard but when select it the following message appears: ========================================= Booting 'CentOS (2.6.18-308.24.1.e15)' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.18-308.24.1.e15 ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1e00, size=0x1cf514] initrd /initrd 0 0x37e62000, 0x18d36e bytes] Memory for crash kernel (0x0 to 0x0) notwithin permissible range Red Hat nash version 5.1.19.6 starting unable to access resume device (/dev/VolGroop00/LogVol101) mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory kernel panic - not syncing: Attempted to kill init! ============================================ by the way, when i log in to windows of my laptop and use Virtual Box, i can mount both boot and lvm partition of external hard and i can see the content of lvm and the programs of my interest.but i cant run the programs. Thanks in advanceSystem Recovery 18 SP1 Linux Edition basic questions
Hi, I have a customer using the trialware version of VSR18 SP1 Linux Edition testing backup and restore under the following configuration: Server: HPE DL360 Gen10 OS: RHEL 7.4 Update 4 They have a couple of basic questions which I'd appreciate feedback on. 1. Regarding what is included in the backup If an NFS share on another server is mounted to this server and the volume to be backed up includes this mount point, does this NFS share get included in the backup? 2. Regarding differences in backup/restore operation due to differences in volume configuration Is there a big difference between backup and restore operation due to differences in volume configuration (i.e. non-LVM versus LVM)? Other than specifying volumes differently from the command line, I believe there isn't much difference. Btw, I intend to provide this KB https://www.veritas.com/support/en_US/article.100031664.html https://www.veritas.com/support/en_US/article.100041317.html https://www.veritas.com/support/en_US/article.100043262.html 3. Install location Where is the Linux Edition software installed to? What directories? I know the commands are installed under /usr/sbin but what about other locations? They need to document this in one of their own documents so any information on this would be appreciated. Thanks!VSR-L failed to backup
Have you tried installing in a cluster environment? If you try to back up in a cluster environment, the following failure occurs. issue detail: -var_log_symsr_application date: 2018-06-02T01:13:11.1843020Z Backup of /dev/sdkc5 to /osbackup/pcscsdbp2/system_023.v2i. GUID: 14592315-6746-e711-8dee-b0d14d44d42f date: 2018-06-02T01:13:11.1846980Z Error E5D40020: Unable to snap volumes. Error E0A20019: Backup Failed. -proc_mounts log /dev/sdkd1 /osbackup ext4 rw,relatime,barrier=1,stripe=64,data=ordered 0 0 /dev/sdkc5 / ext4 rw,relatime,barrier=1,stripe=64,data=ordered 0 0 -Dmesg log Snapping Device(Maj, Min): (66, 257),BlockSize: 4096, NumSectors: 131072, RelocFileName: /boot/.symantec/sdkc1, NumOfRelocEntries: 11659.EnableVtrack: 0, doNotTouchVtrack: 1, App PID: 12132. 0th index is not actually written, pending to be written. Moved the state to DEVICE_UNSNAPPED. Deleted COW and released the SnapAccessDevice. Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Snapping Device(Maj, Min): (66, 257),BlockSize: 4096, NumSectors: 131072, RelocFileName: /boot/.symantec/sdkc1, NumOfRelocEntries: 11659.EnableVtrack: 0, doNotTouchVtrack: 1, App PID: 62532. Moved the state to DEVICE_UNSNAPPED. Deleted COW and released the SnapAccessDevice. Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Snapping Device(Maj, Min): (66, 259),BlockSize: 4096, NumSectors: 2621440, RelocFileName: /var/log/.symantec/sdkc3, NumOfRelocEntries: 24920.EnableVtrack: 0, doNotTouchVtrack: 1, App PID: 49033. Moved the state to DEVICE_UNSNAPPED. Deleted COW and released the SnapAccessDevice. Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Snapping Device(Maj, Min): (66, 261),BlockSize: 4096, NumSectors: 62092288, RelocFileName: //.symantec/sdkc5, NumOfRelocEntries: 1161988.EnableVtrack: 0, doNotTouchVtrack: 1, App PID: 35959. Moved the state to DEVICE_UNSNAPPED. Deleted COW and released the SnapAccessDevice. Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Snapping Device(Maj, Min): (66, 261),BlockSize: 4096, NumSectors: 62092288, RelocFileName: //.symantec/sdkc5, NumOfRelocEntries: 1162728.EnableVtrack: 0, doNotTouchVtrack: 1, App PID: 24361. Moved the state to DEVICE_UNSNAPPED. Deleted COW and released the SnapAccessDevice. Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command Driver is not able to process The Ioctl command