Skip to content
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

[doc] Issue in "COPY THE KEY AND KEY-DATA FILE FROM THE PRIMARY TO THE SECONDARY SITE" #450

Open
roseswe opened this issue Sep 17, 2024 · 1 comment
Labels

Comments

@roseswe
Copy link

roseswe commented Sep 17, 2024

COPY THE KEY AND KEY-DATA FILE FROM THE PRIMARY TO THE SECONDARY SITE:

https://documentation.suse.com/sbp/sap-15/html/SLES4SAP-hana-sr-guide-PerfOpt-15/index.html#id-1.9.8.4

We assume the rsync syntax is missing here an argument like destination or source.

Why not simple scp the files? (To ensure the file is really copied, rsync may not)....

@fmherschel
Copy link
Member

fmherschel commented Sep 27, 2024

@roseswe The rsync does include source and destination:
rsync -va {,<node1-siteB>:}$PWD/data/SSFS_<SID>.DAT

The braces '{}' are the trick here :) ... try:

echo rsync -va {,mynode1-siteB:}$PWD/data/SSFS_SUS.DAT

and you see what I mean... The given command copies a file from a local server relative from the current directory to an remote server at exactly the same location.

And why should scp be better as rsync? I prefer rsync, because I have seen lot of installations broken by consultants using scp (with default flags) vs rsync (with typical flags), if things are copied recursive or with directories. scp does by default copy the referenced file (breaks symlinks) while rsync by default copied the rererences (keeps symlinks).
However you are allowed to use scp instead. I think this is not really an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants