Comprehensive data protection for all workloads
Post Reply
antman157
Influencer
Posts: 17
Liked: 2 times
Joined: Apr 03, 2013 2:53 pm
Full Name: Anthony Jones
Contact:
Contact antman157

File level backups filling up Linux History

Post by antman157 »

Ive got some file level backup jobs setup and they are running fine, but I noticed that every night when Veeam runs, it will fill up and overwrite my Linux history. Anyone else ran into this issue? 12.0.0.1420 P20230412

Here is an example:

Code: Select all

  907  2023-10-26 07:10:46 stty -echo
  908  2023-10-26 07:10:46 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 2c19c0f1-67bd-4093-b085-5978c06b86f7
  909  2023-10-26 07:10:46 whoami; echo $?; echo 17a59b7e-5a5e-490c-9329-1f5773cf192e
  910  2023-10-26 07:10:46 unalias -a; echo $?; echo 0248d652-0742-4dd4-a0ad-c90819c0d995
  911  2023-10-26 07:10:46 stty -echo
  912  2023-10-26 07:10:46 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 390efdc1-73fb-414a-9e99-aa502c868bfa
  913  2023-10-26 07:10:46 /tmp/VeeamAgent3d4e436a-0ff4-4c7e-a57f-a38b1f2ae0f4 -l flush,/var/log/VeeamBackup/Utils/VeeamAgent.FileOperation.Server__cli.log,/tmp/VeeamBackup/Utils/VeeamAgent.FileOperation.Server__cli.log -i c0ed3597-83b8-4485-8fcf-092f0db3b085 -g 2500-3300 --setFileLimit 4096 --argsFilePath /tmp/f8d1bc05-59fd-4bef-a46f-1e0b0645404b ; echo f9434252-aa8f-418d-a9ba-9817765b912e
  914  2023-10-26 07:09:28 stty -echo
  915  2023-10-26 07:09:28 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 233ca40a-57ad-49e5-a185-61e20ebd1351
  916  2023-10-26 07:09:28 whoami; echo $?; echo e85f4374-0bde-42af-8906-35ed70c9ae5f
  917  2023-10-26 07:09:28 unalias -a; echo $?; echo 00eea8e4-b531-4c67-94d0-85a7892b67c2
  918  2023-10-26 07:09:28 stty -echo
  919  2023-10-26 07:09:28 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 73f971d1-d212-42e4-b37c-4d0c205ee203
  920  2023-10-26 07:09:28 /tmp/VeeamAgent6c5555bd-d75c-4185-9183-281a18013c81 -l flush,/var/log/VeeamBackup/VeeamAgent.GetContentInfoOperation__cli.log,/tmp/VeeamBackup/VeeamAgent.GetContentInfoOperation__cli.log -i 26243ed6-eda4-4969-a2c4-1c80fa01c3d6 -g 2500-3300 --setFileLimit 4096 --argsFilePath /tmp/fdb9820f-0526-45cb-b2fd-64e4fc20bb2a ; echo a2c87db8-891b-4813-aaac-ad96be8573f2
  921  2023-10-26 07:09:31 stty -echo
  922  2023-10-26 07:09:31 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo e8aa3150-491e-45cd-9ef2-da59037c2d66
  923  2023-10-26 07:09:31 whoami; echo $?; echo 56b472dd-f987-4489-90eb-e8c426c3b4ef
  924  2023-10-26 07:09:31 unalias -a; echo $?; echo 6588fa03-c66b-4f48-a5ac-417d7c414fcc
  925  2023-10-26 07:09:31 stty -echo
  926  2023-10-26 07:09:31 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 75f27aa3-715b-4f2a-a781-24bbccd81b9a
  927  2023-10-26 07:09:31 (cd /tmp && perl veeam_soap99199fc8-2cd7-4f1a-92d1-fafc307f8d7e.pl -d -c -l lib99199fc8-2cd7-4f1a-92d1-fafc307f8d7e -e /tmp/veeam_error99199fc8-2cd7-4f1a-92d1-fafc307f8d7e 2>> /tmp/veeam_error99199fc8-2cd7-4f1a-92d1-fafc307f8d7e) || cat /tmp/veeam_error99199fc8-2cd7-4f1a-92d1-fafc307f8d7e 2>&1
  928  2023-10-26 10:25:31 stty -echo
  929  2023-10-26 10:25:31 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 26c8e9ee-f194-4e08-bfab-b3d90b17d425
  930  2023-10-26 10:25:31 whoami; echo $?; echo ac867820-9a98-400b-a3bb-fddfbac99a40
  931  2023-10-26 10:25:31 unalias -a; echo $?; echo 72daba74-a310-47a9-868a-283f7dce7385
  932  2023-10-26 10:25:31 stty -echo
  933  2023-10-26 10:25:31 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo d5e77501-c948-4894-a19a-f8a3c3d24b08
  934  2023-10-26 10:25:31 /tmp/VeeamAgent1866cb16-20d9-46e8-8796-fabb8a2b726a -l flush,/var/log/VeeamBackup/Util.VolumesHostDiscover__cli.log,/tmp/VeeamBackup/Util.VolumesHostDiscover__cli.log -i 2da11d84-b3c5-4d03-ae3f-edb45f80a85d -g 2500-3300 --setFileLimit 4096 --argsFilePath /tmp/2f811fde-62d8-4704-8786-eafb58bfaace ; echo 282e0db2-f9b1-4e5c-9169-31decc4bbecb
  935  2023-10-26 10:25:34 stty -echo
  936  2023-10-26 10:25:34 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo f1430b9d-94ea-4ee6-b093-9501573a948b
  937  2023-10-26 10:25:34 whoami; echo $?; echo 095f917a-fffe-4c10-8054-a00c9d32e2f0
  938  2023-10-26 10:25:34 unalias -a; echo $?; echo f6d857b8-ef09-4b56-a567-32562ac6ee22
  939  2023-10-26 10:25:34 stty -echo
  940  2023-10-26 10:25:34 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo a77ddd6c-94b9-448d-ac72-faf180951c4b
  941  2023-10-26 10:25:34 (cd /tmp && perl veeam_soap4a889076-af36-4877-8bfe-3c49e6d4cfe1.pl -d -c -l lib4a889076-af36-4877-8bfe-3c49e6d4cfe1 -e /tmp/veeam_error4a889076-af36-4877-8bfe-3c49e6d4cfe1 2>> /tmp/veeam_error4a889076-af36-4877-8bfe-3c49e6d4cfe1) || cat /tmp/veeam_error4a889076-af36-4877-8bfe-3c49e6d4cfe1 2>&1
  942  2023-10-26 14:22:28 stty -echo
  943  2023-10-26 14:22:28 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 70ad9e04-46a4-46cf-bc0c-2c56517cc027
  944  2023-10-26 14:22:28 whoami; echo $?; echo fe8f318b-b8c0-4636-93db-87c61a2bdc0e
  945  2023-10-26 14:22:28 unalias -a; echo $?; echo 2f28f6ce-60db-49ac-9370-413be2800c05
  946  2023-10-26 14:22:28 stty -echo
  947  2023-10-26 14:22:28 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 6bde89d9-359f-4956-940f-c9b84e6b49ed
  948  2023-10-26 14:22:28 /tmp/VeeamAgentca734600-1476-46fc-9e76-f221bfa6f1b7 -l flush,/var/log/VeeamBackup/Util.VolumesHostDiscover__cli.log,/tmp/VeeamBackup/Util.VolumesHostDiscover__cli.log -i 58d541a9-a575-43bb-8757-e44429024a41 -g 2500-3300 --setFileLimit 4096 --argsFilePath /tmp/e60fc06d-14f8-46c5-93b5-3f6ebc77fd77 ; echo a4ea2c2e-3aa4-4bb8-819f-92c6b9676f0d
  949  2023-10-26 14:22:30 stty -echo
  950  2023-10-26 14:22:30 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo cbddbd6d-fd84-4f3c-bfa2-cbf09347c909
  951  2023-10-26 14:22:30 whoami; echo $?; echo ae8251c3-ea2e-4bdc-9b32-53a17cb2ef07
  952  2023-10-26 14:22:30 unalias -a; echo $?; echo d8313ab6-4cb5-43c5-bb5a-ed337d1946eb
  953  2023-10-26 14:22:30 stty -echo
  954  2023-10-26 14:22:30 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 99e10910-dccc-41af-8f7a-12f570fb086e
  991  2024-01-26 11:04:33 stty -echo
  992  2024-01-26 11:04:33 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo d6e34aa3-3151-42cd-b57e-5422cc9a905b
  993  2024-01-26 11:04:33 whoami; echo $?; echo 06a5aa89-beb2-4cf3-b60c-4e14844302c1
  994  2024-01-26 11:04:33 unalias -a; echo $?; echo db7ae422-9b18-464b-b0d2-d8362a48b639
  995  2024-01-26 11:04:33 stty -echo
  996  2024-01-26 11:04:33 export PS1="VEEAM_TERMINAL_PROMPT$"; echo $?; echo 67aad7aa-442c-4f51-b881-92412478de68
  997  2024-01-26 11:04:33 whoami; echo $?; echo b6aa5759-ef5c-4cca-b85c-84e0da2737b0
  998  2024-01-26 11:04:33 unalias -a; echo $?; echo 3c415744-e5b9-4e9f-87dd-5da469709ed9
  999  2024-01-26 11:04:33 whoami; echo $?; echo ce942b5c-8420-4721-a5d5-2e592ff5ba72
 1000  2024-01-26 11:04:33 which mount.nfs; echo $?; echo 8e368026-2834-49fe-9a69-ff91678c8ee7
 1001  2024-01-26 11:20:02 history
Top
PTide
Product Manager
Posts: 6489
Liked: 753 times
Joined: May 19, 2015 1:46 pm
Contact:
Contact PTide

Re: File level backups filling up Linux History

Post by PTide » 1 person likes this post

Hi,

I have already scheduled this behavior for fixing in future versions.

Thanks!
Top
Post Reply

Return to “Veeam Backup & Replication”



Who is online

Users browsing this forum: MILJW002, Semrush [Bot] and 250 guests