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 commandSystem 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!
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?Veritas System Recovery for Linux 18 Cannot Mount Recovery Point
Hi I'm testing the Veritas System Recovery 18 for Linux on Rhel 7.3 server. Independent backup and creation of custom SDR were successful. But when i'm about to test the restoration (whole system), i cannot mount the backup storage. please see error. Note: The recovery point is located on the computer in a different partition (stored on external). sh-4:# mount /dev/sdc1 /tmp/backup mount: mount point /tmp/backup does not existVeritas System Recovery for Linux 16 Cannot Backup
Hi Everyone. Can somebody help me. I've installed VSR for linux (Rhel 7.3) without a license (trial period). I'm using it for a week. But when i conducted a backup testing using "symsr utility", it says Warning: Application license has expired. It will now run with reduced functionality. and the backup job i'd created was not executed. see attached file. i need to complete my testing. ;(