search

SUSE / suse-best-practices

SUSE Best Practices documentation series
43 stars 74 forks source link

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

Open roseswe opened 2 months ago

roseswe commented 2 months ago

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 commented 1 month ago

@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.