-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NETWORKER backing up only the ISO file? #2367
Comments
This is the output I see on the Networker logs.
Thank you, |
Hello Support, So with the same setting when I do a REAR backup to an NFS server it backs up the system files not only the ISO image. '/boot' '/' 'swap' '/dev' Why is Networker backing up these files? Regards, |
@IT-Guy-1973 First of all 1.17.2 is really old! Please upgrade ReaR to 2.4 or 2.5. |
@gdha When I ran "yum in rear" on my RedHat v6.10 system it installed this version. I will look to upgrade it soon. But so far it has been working great. Some background: Regards, |
Hello Support, I was able to restore using NSR to another new system (VM) with the same hard disk sizes. However, when restoring to the new system REAR identified that the IP was different but it said "Disks are identical" and started the restore without prompting me. I had two disks on this system one 80GB and the other 40GB. Both belong to different volume groups. But REAR restored all data to one disk and (80GB) and kept the other disk free. The system after restore went to maintenance mode and I had to manually comment out the file system that belongs to the second VG to bring the system up. Regards, |
@IT-Guy-1973 You don't have that in your old ReaR 1.17.2 version. See the ReaR release notes for some more info ReaR version 2.3 has an improved MIGRATION_MODE autodetection ReaR version 2.4 has major rework and changed default behaviour ReaR version 2.5 has lots of other improvements that are in particular Newer ReaR will never start the restore without prompting you. Note that resizing only happens for plain disk partitions Furthermore see the section Or just better: |
Hello @jsmeix , I updated the rear to v2.4. The first thing I noticed with the new version is that it does not prompt for the network card. The IP is already there of the source system. One reason to use REAR for us is to upgrade systems by building another system. Therefore, we need to restore the system onto another system while the source system is in production. We cannot afford to have an IP conflict. Luckily the v2.4 of REAR stops at the prompt. I changed the original IP that was there with REAR to a different IP so that no IP conflict happens. The other option that I am looking for is the list of disks or file systems that I could select for the restore. We almost all of the time need only the root disk to be restored. The root disk would be about 30 GB. We have databases on other disks that run to TB's and we should not restore those with REAR. I do not see the option presented in REAR with Networker. How can I select what disks o file systems to restore? Because Networker anyway backs up everything and I cannot stop Networker from backing all the mounted file systems. How can we select what to restore when restoring through REAR v2.4? Thank you, |
Hi @IT-Guy-1973. Within Legato Networker configuration there are IMHO possibilities to exclude files/directories based on patterns and wildcards (IMHO named backup directives) or determine the backup filesystems in the saveset. So it is - as @gdha pointed to - always the responsibility of the EXTERNAL backup tool what files will be recovered to the system. Cheers, |
@IT-Guy-1973
see "Some general information FYI" in Additionally see
|
@IT-Guy-1973
Offhandedly I think the currently best way to do that is What is currently not well supported in ReaR is that the user can In general regarding system migration with ReaR see |
Only as a side note FYI about my "future dream" |
Hello Holger, Thank you. Our systems would normally have a "rootvg" volume group and then data volume groups that include files systems related to applications and/or databases. All file systems are backed up by Networker. The goal is to recover any file or file system if needed. As a system admin I may have to recover only the rootvg. So I will have a system where many disks are attached and the ISO image from REAR is mounted. I boot off the ISO image and when I run "rear recover" I should ONLY restore everything in rootvg and NOTHING in datavgs. Can I use this parameter to do it with REAR? ONLY_INCLUDE_VG=() Networker will have all the data backed up as their job is to take care of any data on that system. Regards, |
@IT-Guy-1973
So there is no code about ONLY_INCLUDE_VG Accordingly it seems ONLY_INCLUDE_VG is only used Therefore I think if your Legato Networker backup contains |
Hello @jsmeix , Thank you for your reply above regarding the "ONLY_INCLUDE_VG". I was thinking of it in terms of restore. Like in - only include vgxx when restoring. But as you pointed out this parameter is not related to NSR. Also, I am still going through your earlier responses to my question. It looks like the options I have is to edit the disk layout files during restore. But let me carefully read all you posted here before I raise another question. Thank you, |
Hello @jsmeix , When using Networker with REAR there is absolutely no way to control what is restored on the VM. With REAR you can select what disks you want etc ... But when the restore happens it is going to restore everything Networker backed up. Example: I have a volume group on disk "/dev/sdb" named nmonvg and a file system in it name /nmon_data. If I disable the "/dev/sdb" using REAR the "/nmon_data" will anyway get restored on a directory under /. @jsmeix Let me know if my understanding of this is correct. Regards, |
Yes, you are absolutely correct. I tried to change what needs to be restored but that cannot be done. Even if I change the disk layout hoping it will not restore certain volume groups the restore happens on the rootvg as directories. Regards, |
Hi, @IT-Guy-1973. In my use case EMC Networker backups all data of a (single) server. The setup backups the dedicated filesystems /, /var/log, etc. instead of ALL. Furthermore it is possible to exclude all unwanted data i.e. the database files of a MySQL in /data/mysqldata/ or all logfiles in /var/log/ and so on. When it comes to a disaster recovery ReaR prepares my (single) server with all required filesystems and afterwards EMC Networker is triggered to restore all the backuped files into them. Using NSR_CLIENT_MODE=YES it is possible to i.e. execute EMC Networker's "recovery" tool manually to recover data of dedicated filessystems or manually select all the data required. NSR_CLIENT_MODE=YES waits until someone recovered the data with EMC Networker. Regards, |
Hello @hpannenb , I added NSR_CLIENT_MODE=YES to the site.conf file. Now, as you mention correctly the restore stops at the "rear>" prompt. At this point do I need to inform the backup team to initiate a restore from their end or can I run the "recover" command at my end to perform the restore? I have 3 file systems on this system. I need to avoid installing /nmon_data. I only need / and /boot only. On the restore system I see: /mnt/local/ file systems. I am not very familiar with NSR commands. Please let me know what I need to do at this point. Thank you, |
Hi, @IT-Guy-1973 You can handle it as You prefer. Either execute the recovery on Your own or with the help of Your backup team. Quiet some time ago I found the required EMC Networker commands at this page here. You can look for "recover". With this and the knowledge from the ReaR sources in
I propose You check Your backup strategy if Sincerely, |
Hello @hpannenb , Thank you for the information. I have not tried this yet. But hopefully, I will try this tomorrow. Thank you for sharing the Networker command-line help page as well. Networker commands are pretty hard to assemble. Regards, |
Hello @hpannenb , I ran the commands you had provided. I had to manually add the hostname and the Networker server name. It worked. However, I did not see the boot image been created at the end. It is at the "rear>" prompt now after the restore. Do I need to run any manual commands at this point to get the boot image created before I reboot the newly restored system? Please see the attachment. |
Hi, @IT-Guy-1973. You should have seen a prompt beforehand
I suppose at the prompt You entered the "recover" command. When Your manual EMC recovery has been completed type "exit"(+ENTER) to continue the restore process. Regards, |
@hpannenb Thank you for your valuable input. It all worked perfectly! I did restore multiple times to get a feel of the process. Thank you again, |
@IT-Guy-1973 |
@jsmeix Yes sir, you can. I also like to thank you for providing me with answers to the questions that I have raised with this request as well as other requests in the past. Regards, |
@IT-Guy-1973 |
ReaR version ("/usr/sbin/rear -V"): 1.17.2
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" or "lsblk" as makeshift):
Description of the issue (ideally so that others can reproduce it):
I am able to run "rear -vD mkbackup" and see the following messages.
To me, this looks like it is backing up the "/var/lib/rear/output/rear-lnxjump01.iso " file only. According to my site.conf file I should be backing up '/boot' '/' 'swap' '/dev' as well.
Why are those file systems not been backed up?
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
The text was updated successfully, but these errors were encountered: