odd, I provided extensive info in my opening post, but somehow I cannot see that anymore. Well, here we go again:
I have a v14 fileserver appliance (with some mods), running on bare metal. I intend to replace my server, and upgrade to v15 fileserver on VMware. The backup is approx 80GB. I want to test the procedure first, so I started ant2.medium instance on AWS, with 600GB HDD. The tklbam-restore has been running for over 36 hours now. Afer peaking the first hours, now showing very little IO or network activity.
more info
odd, I provided extensive info in my opening post, but somehow I cannot see that anymore. Well, here we go again:
I have a v14 fileserver appliance (with some mods), running on bare metal. I intend to replace my server, and upgrade to v15 fileserver on VMware. The backup is approx 80GB. I want to test the procedure first, so I started ant2.medium instance on AWS, with 600GB HDD. The tklbam-restore has been running for over 36 hours now. Afer peaking the first hours, now showing very little IO or network activity.
last lines in /var/log/tklbam-restore
output df -h
tklbam-restore keeps hogging cpu
Why is tklbam so busy? What is it doing? Why doesn't it finish or throw an error? What else can I check?