-
- Expert
- Posts: 235
- Liked: 37 times
- Joined: Aug 06, 2013 10:40 am
- Full Name: Peter Jansen
- Contact:
veeamconfig patchiso tmp working directory
Is there a way to redirect the temporary working dir whilst creating a recovery image?
In creating a recovery image with veeamconfig config patchiso --input xxxxx --output yyyyy i notice some work being done by gzip in /tmp. My /tmp is rather small and gets no space left. The image creation fails. Due to standards I cannot increase /tmp.
thanks,
Peter
In creating a recovery image with veeamconfig config patchiso --input xxxxx --output yyyyy i notice some work being done by gzip in /tmp. My /tmp is rather small and gets no space left. The image creation fails. Due to standards I cannot increase /tmp.
thanks,
Peter
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: veeamconfig patchiso tmp working directory
Hi,
Please go to /etc/veeam/veeam.ini, uncomment and change temporarydirectory= /tmp/veeam parameter.
No service restart is required.
Thanks!
Please go to /etc/veeam/veeam.ini, uncomment and change temporarydirectory= /tmp/veeam parameter.
No service restart is required.
Thanks!
-
- Expert
- Posts: 235
- Liked: 37 times
- Joined: Aug 06, 2013 10:40 am
- Full Name: Peter Jansen
- Contact:
Re: veeamconfig patchiso tmp working directory
ok thanks, works fine!
grtz, Peter
grtz, Peter
-
- Influencer
- Posts: 19
- Liked: 1 time
- Joined: Oct 28, 2020 2:03 pm
- Contact:
[MERGED] File indexing location
Hi,
I have setup a new backup job for a Linux server and I have enabled guest file system indexing.
I have noted that VEEAM stores index info in /tmp/veeam/index by default.
Is there a way to change the location for index info?
Thanks in advance for your feedback.
I have setup a new backup job for a Linux server and I have enabled guest file system indexing.
I have noted that VEEAM stores index info in /tmp/veeam/index by default.
Is there a way to change the location for index info?
Thanks in advance for your feedback.
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: veeamconfig patchiso tmp working directory
Hello,
did you try changing see the temporarydirectory option in /etc/veeam/veeam.ini as mentioned above?
Best regards,
Hannes
did you try changing see the temporarydirectory option in /etc/veeam/veeam.ini as mentioned above?
Best regards,
Hannes
-
- Influencer
- Posts: 19
- Liked: 1 time
- Joined: Oct 28, 2020 2:03 pm
- Contact:
Re: veeamconfig patchiso tmp working directory
Thanks for your support.
Changes were applied successfully.
Changes were applied successfully.
-
- Enthusiast
- Posts: 27
- Liked: 2 times
- Joined: May 05, 2020 5:50 pm
- Full Name: Ryan
- Contact:
Re: veeamconfig patchiso tmp working directory
In version 5.0 i don't see this line in the /etc/veeam/veeam.ini file
but i added the line (sans the backtics)
`temporarydirectory= /var/temp`
But yet in the logs i still see it using /tmp/veeam as the directory?
veeamconfig patchiso --input veeam-recovery-media-5.0.2.4567_x86_64.iso --output veeam-recovery-media-5.0.2.4567_x86_64.patch.iso --efi
Creating custom Veeam Recovery Media...
FATAL ERROR:write_file: failed to create file /tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/rootfs/usr/lib/modules/4.19.0-18-amd64/kernel/drivers/net/usb/ch9200.ko, because Too many open files
Exit code: [1]
Failed to execute script command unsquashfs -no-progress -dest /tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/rootfs /tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/patched_iso/filesystem.squashfs
Failed to unpack squashfs image [/tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/patched_iso/filesystem.squashfs] to directory [/tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/rootfs].
I have also already tried doing the troubleshooting steps for this error below.
https://www.veeam.com/kb4121
And have not had any luck.
but i added the line (sans the backtics)
`temporarydirectory= /var/temp`
But yet in the logs i still see it using /tmp/veeam as the directory?
veeamconfig patchiso --input veeam-recovery-media-5.0.2.4567_x86_64.iso --output veeam-recovery-media-5.0.2.4567_x86_64.patch.iso --efi
Creating custom Veeam Recovery Media...
FATAL ERROR:write_file: failed to create file /tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/rootfs/usr/lib/modules/4.19.0-18-amd64/kernel/drivers/net/usb/ch9200.ko, because Too many open files
Exit code: [1]
Failed to execute script command unsquashfs -no-progress -dest /tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/rootfs /tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/patched_iso/filesystem.squashfs
Failed to unpack squashfs image [/tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/patched_iso/filesystem.squashfs] to directory [/tmp/veeam/livecd-{b59af0e7-7fc6-4682-93c2-bb7e2f344728}/rootfs].
I have also already tried doing the troubleshooting steps for this error below.
https://www.veeam.com/kb4121
And have not had any luck.
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: veeamconfig patchiso tmp working directory
Hello,
Thanks,
Hannes
if KB4121 did not help, what did Veeam support say? case number?because Too many open files
Thanks,
Hannes
Who is online
Users browsing this forum: No registered users and 11 guests