I need to recover a virtual Windows 10 from my backup machine.

The work machine's folder to receive it is alan@albury
The backup machine folder currently holding it is alan@churchill

I had ssh'd into churchill from albury.
From the source directory I entered the copy string:

alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows 10-x64" alan@albury.

It started "doing something", ran for quite a while and the prompt reapeared.

BUT I am blowed if I can see the copied directory!

What am I doing wrong?

--
Mint 21.1, kernel 5.15.0-72-generic, Cinnamon 5.6.8
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.

On 5/24/2023 7:42 AM, pinnerite wrote:
> I need to recover a virtual Windows 10 from my backup machine.
>
> The work machine's folder to receive it is alan@albury
> The backup machine folder currently holding it is alan@churchill
>
> I had ssh'd into churchill from albury.
> From the source directory I entered the copy string:
>
> alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows 10-x64" alan@albury.
>
> It started "doing something", ran for quite a while and the prompt reapeared.
>
> BUT I am blowed if I can see the copied directory!
>
> What am I doing wrong?
>
>

# Local to remote

scp robnet.htm pi@192.168.1.101:/home/pi/robnet.htm

# Remote to local

scp pi@192.168.1.101:/home/pi/robnet.htm robnet.htm

Notice that the usage of an IP address, takes care of the
fact the user does not have their own domain registered with DNS.

How does scp know what "albury" and "churchill" are ?

What namespace is that ? Is there some nameserver which knows
"albury" to be a fully qualified name ?

Does this work ? This checks DNS, and maybe it consults /etc/hosts (but maybe not).

nslookup albury

nslookup churchill

One of the checks some softwares do, is they do reverse
lookup, and verify that both name to IP and IP to name, are consistent.
An /etc/hosts resolution, fails such tests, and reverse lookup is a
way of checking that the domain is an "official registered DNS one".

A FQDN (fully qualified domain name) might play a part in
precise delivery of goods. Turn on some verbose-ness so
you can get more feedback.

scp -vvv robnet.htm pi@192.168.1.101:/home/pi/robnet.htm

"-v Verbose mode. Causes scp and ssh(1) to print debugging messages
about their progress. This is helpful in debugging
connection, authentication, and configuration problems."

Commands also return an error code as a number ("errno"), which can
be displayed if you use the correct command, *immediately*
after a failed command.

echo $?

For example, here I am displaying the errno from my failed "foobar" attempt.
If all had gone well, the errno == 0. Other values indicate a problem.

me@home:/home/me $ foobar

foobar: command not found

me@home:/home/me $ echo $?

127

Then I look it up (it's a bash error), and verify the value.

https://linuxconfig.org/how-to-fix-bash-127-error-return-code

"Exit code 127 error status in Bash script"

"The 127 error code indicates “command not found”. This occurs
when any given command within your Bash script or on Bash
command line is not found in any of the paths defined by
PATH system environment variable."

That's just to show that I really got the errno I was expecting :-)

*******

You can check the manual page for scp, to see what errno values it uses.
Well, maybe not.

"EXIT STATUS
The scp utility exits 0 on success, and >0 if an error occurs." <=== Gee, thanks.

Paul

On 5/24/23 04:42, pinnerite wrote:
> What am I doing wrong?
>

So many things.
Not sure where to begin.

On 2023-05-24, pinnerite wrote:
> I need to recover a virtual Windows 10 from my backup machine.
> [...]
> alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows
> 10-x64" alan@albury.
> [...]
> What am I doing wrong?

Did you literally only write "scp -r Win10_x64 alan@albury"?

Or is that a typo here on Usenet, and the actual command was "scp -r
Win10_x64 alan@albury:" ?

The trailing colon is critical to indicating a remote host. If you
forgot it, scp will have just created a new directory
"/home/backup/alan/Vbox_VM/alan@albury".

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On Wed, 24 May 2023 18:57:07 -0700
stepore <stepore@be.here.now> wrote:

> On 5/24/23 04:42, pinnerite wrote:
> > What am I doing wrong?
> >
>
> So many things.
> Not sure where to begin.
>

Make a stab at it. I'll wait.

--
Mint 21.1, kernel 5.15.0-72-generic, Cinnamon 5.6.8
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.

On Thu, 25 May 2023 09:46:25 -0000 (UTC)
Dan Purgert <dan@djph.net> wrote:

> On 2023-05-24, pinnerite wrote:
> > I need to recover a virtual Windows 10 from my backup machine.
> > [...]
> > alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows
> > 10-x64" alan@albury.
> > [...]
> > What am I doing wrong?
>
> Did you literally only write "scp -r Win10_x64 alan@albury"?
>
> Or is that a typo here on Usenet, and the actual command was "scp -r
> Win10_x64 alan@albury:" ?
>
> The trailing colon is critical to indicating a remote host. If you
> forgot it, scp will have just created a new directory
> "/home/backup/alan/Vbox_VM/alan@albury".
>

Ah! That is what happened. I got round it by moving the backup drive to the target machine, booting on a flash drive and cp'ing. Sledgehammer ,I know.

Thank you, Alan

--
Mint 21.1, kernel 5.15.0-72-generic, Cinnamon 5.6.8
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.

On 5/26/2023 5:27 AM, pinnerite wrote:
> On Thu, 25 May 2023 09:46:25 -0000 (UTC)
> Dan Purgert <dan@djph.net> wrote:
>
>> On 2023-05-24, pinnerite wrote:
>>> I need to recover a virtual Windows 10 from my backup machine.
>>> [...]
>>> alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows
>>> 10-x64" alan@albury.
>>> [...]
>>> What am I doing wrong?
>>
>> Did you literally only write "scp -r Win10_x64 alan@albury"?
>>
>> Or is that a typo here on Usenet, and the actual command was "scp -r
>> Win10_x64 alan@albury:" ?
>>
>> The trailing colon is critical to indicating a remote host. If you
>> forgot it, scp will have just created a new directory
>> "/home/backup/alan/Vbox_VM/alan@albury".
>>
>
> Ah! That is what happened. I got round it by moving the backup drive to the target machine, booting on a flash drive and cp'ing. Sledgehammer ,I know.
>
> Thank you, Alan

Does that mean you inadvertently made a backup ?

The luck of some people.

Paul

On Fri, 26 May 2023 06:32:00 -0400
Paul <nospam@needed.invalid> wrote:

> On 5/26/2023 5:27 AM, pinnerite wrote:
> > On Thu, 25 May 2023 09:46:25 -0000 (UTC)
> > Dan Purgert <dan@djph.net> wrote:
> >
> >> On 2023-05-24, pinnerite wrote:
> >>> I need to recover a virtual Windows 10 from my backup machine.
> >>> [...]
> >>> alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows
> >>> 10-x64" alan@albury.
> >>> [...]
> >>> What am I doing wrong?
> >>
> >> Did you literally only write "scp -r Win10_x64 alan@albury"?
> >>
> >> Or is that a typo here on Usenet, and the actual command was "scp -r
> >> Win10_x64 alan@albury:" ?
> >>
> >> The trailing colon is critical to indicating a remote host. If you
> >> forgot it, scp will have just created a new directory
> >> "/home/backup/alan/Vbox_VM/alan@albury".
> >>
> >
> > Ah! That is what happened. I got round it by moving the backup drive to the target machine, booting on a flash drive and cp'ing. Sledgehammer ,I know.
> >
> > Thank you, Alan
>
> Does that mean you inadvertently made a backup ?
>
> The luck of some people.
>
> Paul

Yawn, I guess I need to explain. Just before the millenium I feared that the extended break might give local theives to break in and steal our equipment. It had happene to my adjacent neighbour.

My solution was to buy a second hard drive for every machine and take a clone, keeping the drives offsite (at home).

I kept up the habit even though I no longer have staff. Periodically I take a clone of my main machine.
Until two years ago i had a second machine to which I would take backups via rsync across the LAN.
However, two years ago I moved home and had to mothball the second machine until I was completely settled. That happened last week and I have backed up twice since then.

However occasionally I will need to write back one or more files from the second machine thatv has neither monitor nor keyboard. (It did have two years ago) I no longer have the desk space, so it is ssh and scp.

Is that clear?

Regards, Alan

--
Mint 21.1, kernel 5.15.0-72-generic, Cinnamon 5.6.8
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.

On 5/26/2023 4:44 PM, pinnerite wrote:
> On Fri, 26 May 2023 06:32:00 -0400
> Paul <nospam@needed.invalid> wrote:
>
>> On 5/26/2023 5:27 AM, pinnerite wrote:
>>> On Thu, 25 May 2023 09:46:25 -0000 (UTC)
>>> Dan Purgert <dan@djph.net> wrote:
>>>
>>>> On 2023-05-24, pinnerite wrote:
>>>>> I need to recover a virtual Windows 10 from my backup machine.
>>>>> [...]
>>>>> alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows
>>>>> 10-x64" alan@albury.
>>>>> [...]
>>>>> What am I doing wrong?
>>>>
>>>> Did you literally only write "scp -r Win10_x64 alan@albury"?
>>>>
>>>> Or is that a typo here on Usenet, and the actual command was "scp -r
>>>> Win10_x64 alan@albury:" ?
>>>>
>>>> The trailing colon is critical to indicating a remote host. If you
>>>> forgot it, scp will have just created a new directory
>>>> "/home/backup/alan/Vbox_VM/alan@albury".
>>>>
>>>
>>> Ah! That is what happened. I got round it by moving the backup drive to the target machine, booting on a flash drive and cp'ing. Sledgehammer ,I know.
>>>
>>> Thank you, Alan
>>
>> Does that mean you inadvertently made a backup ?
>>
>> The luck of some people.
>>
>> Paul
>
> Yawn, I guess I need to explain. Just before the millenium I feared that the extended break might give local theives to break in and steal our equipment. It had happene to my adjacent neighbour.
>
> My solution was to buy a second hard drive for every machine and take a clone, keeping the drives offsite (at home).
>
> I kept up the habit even though I no longer have staff. Periodically I take a clone of my main machine.
> Until two years ago i had a second machine to which I would take backups via rsync across the LAN.
> However, two years ago I moved home and had to mothball the second machine until I was completely settled. That happened last week and I have backed up twice since then.
>
> However occasionally I will need to write back one or more files from the second machine thatv has neither monitor nor keyboard. (It did have two years ago) I no longer have the desk space, so it is ssh and scp.
>
> Is that clear?
>
> Regards, Alan

I use RS232 at 57.6 Kbaud between computers, when I want
to have a terminal-like session. The machines have a null modem
cable between them.

I'm lucky, that without checking for the presence of such things,
both machines have 2x5 header for RS232. They no longer bother with
the archaic DB-9 or whatever, on the back of the computer. This
leaves it "up to the user to fashion their own cable".

Several releases ago, someone "perfected" SAMBA file sharing, to the
extent that if you did Properties on something in your File Manager,
they had placed a Sharing tab, and you could enable Sharing (the sharing
dialog did all the work.

But this seemed to be broken on purpose on distributions after that. Still
this gives another means to transfer files. Linux distros can run
Client SAMBA or Server SAMBA, and can push or pull files. SAMBA has
rudimentary crypto on it (only 128 bit), and I would not really
be running such a thing on the Internet. But it's OK inside a
computer room.

You could also be running NFS, but I haven't set up a thing like
that in a lot of years.

If the machine is headless, there may be ways of setting up
connections to it, using junk you already have. For example, back
when I was working, I carried an "RS232 bag" between employers,
because employers never had RS232 stuff when I needed it. And then
when I didn't have a job any more, that bag provides the adapters
for my interconnect between machines. RS232 is absolute rubbish when
it comes to connector types, and to get across the room costs
a lot of money when the job really should have been so simple.
(Half the adapters seem to be gender changers.)

When the serial port is on the SuperIO chip (a "well known" port unlike
USB ones), the Linux boot line, the one with "quiet splash" on it,
you can add this

console=ttyS0,57600n8

and that's all you need to make the RS232 work for that session.

Paul

On 5/26/23 02:18, pinnerite wrote:
> Make a stab at it. I'll wait.
>

Paul gave you some suggestions to start.

On Fri, 26 May 2023 19:18:13 -0400
Paul <nospam@needed.invalid> wrote:

> On 5/26/2023 4:44 PM, pinnerite wrote:
> > On Fri, 26 May 2023 06:32:00 -0400
> > Paul <nospam@needed.invalid> wrote:
> >
> >> On 5/26/2023 5:27 AM, pinnerite wrote:
> >>> On Thu, 25 May 2023 09:46:25 -0000 (UTC)
> >>> Dan Purgert <dan@djph.net> wrote:
> >>>
> >>>> On 2023-05-24, pinnerite wrote:
> >>>>> I need to recover a virtual Windows 10 from my backup machine.
> >>>>> [...]
> >>>>> alan@churchill:/home/backup/alan/VirtualBox_VMs$ scp -r ./"Windows
> >>>>> 10-x64" alan@albury.
> >>>>> [...]
> >>>>> What am I doing wrong?
> >>>>
> >>>> Did you literally only write "scp -r Win10_x64 alan@albury"?
> >>>>
> >>>> Or is that a typo here on Usenet, and the actual command was "scp -r
> >>>> Win10_x64 alan@albury:" ?
> >>>>
> >>>> The trailing colon is critical to indicating a remote host. If you
> >>>> forgot it, scp will have just created a new directory
> >>>> "/home/backup/alan/Vbox_VM/alan@albury".
> >>>>
> >>>
> >>> Ah! That is what happened. I got round it by moving the backup drive to the target machine, booting on a flash drive and cp'ing. Sledgehammer ,I know.
> >>>
> >>> Thank you, Alan
> >>
> >> Does that mean you inadvertently made a backup ?
> >>
> >> The luck of some people.
> >>
> >> Paul
> >
> > Yawn, I guess I need to explain. Just before the millenium I feared that the extended break might give local theives to break in and steal our equipment. It had happene to my adjacent neighbour.
> >
> > My solution was to buy a second hard drive for every machine and take a clone, keeping the drives offsite (at home).
> >
> > I kept up the habit even though I no longer have staff. Periodically I take a clone of my main machine.
> > Until two years ago i had a second machine to which I would take backups via rsync across the LAN.
> > However, two years ago I moved home and had to mothball the second machine until I was completely settled. That happened last week and I have backed up twice since then.
> >
> > However occasionally I will need to write back one or more files from the second machine thatv has neither monitor nor keyboard. (It did have two years ago) I no longer have the desk space, so it is ssh and scp.
> >
> > Is that clear?
> >
> > Regards, Alan
>
> I use RS232 at 57.6 Kbaud between computers, when I want
> to have a terminal-like session. The machines have a null modem
> cable between them.
>
> I'm lucky, that without checking for the presence of such things,
> both machines have 2x5 header for RS232. They no longer bother with
> the archaic DB-9 or whatever, on the back of the computer. This
> leaves it "up to the user to fashion their own cable".
>
> Several releases ago, someone "perfected" SAMBA file sharing, to the
> extent that if you did Properties on something in your File Manager,
> they had placed a Sharing tab, and you could enable Sharing (the sharing
> dialog did all the work.
>
> But this seemed to be broken on purpose on distributions after that. Still
> this gives another means to transfer files. Linux distros can run
> Client SAMBA or Server SAMBA, and can push or pull files. SAMBA has
> rudimentary crypto on it (only 128 bit), and I would not really
> be running such a thing on the Internet. But it's OK inside a
> computer room.
>
> You could also be running NFS, but I haven't set up a thing like
> that in a lot of years.
>
> If the machine is headless, there may be ways of setting up
> connections to it, using junk you already have. For example, back
> when I was working, I carried an "RS232 bag" between employers,
> because employers never had RS232 stuff when I needed it. And then
> when I didn't have a job any more, that bag provides the adapters
> for my interconnect between machines. RS232 is absolute rubbish when
> it comes to connector types, and to get across the room costs
> a lot of money when the job really should have been so simple.
> (Half the adapters seem to be gender changers.)
>
> When the serial port is on the SuperIO chip (a "well known" port unlike
> USB ones), the Linux boot line, the one with "quiet splash" on it,
> you can add this
>
> console=ttyS0,57600n8
>
> and that's all you need to make the RS232 work for that session.
>
> Paul

I am fixed now but I like sopund of SAMBA as I already use it on my main machine.

Alan

--
Mint 21.1, kernel 5.15.0-72-generic, Cinnamon 5.6.8
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.