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

backupData requires pools to have different names even if they are on different machines #28

Open
fritz-hh opened this issue Nov 4, 2018 · 0 comments
Labels

Comments

@fritz-hh
Copy link
Owner

fritz-hh commented Nov 4, 2018

Hello Fritz,

Thank you for these scripts! They appear to be exactly what I was looking for (manageSnapshots.sh and backupData.sh in particular). I've just got one issue ... I'm trying to backup datasets on my primary storage server to a backup server. The servers are very similar in configuration, right down to the names of the pools/datasets. When I invoke backupData.sh from the command line:

./backupData.sh -s [email protected] Pool01/Misc Pool01/Misc

Nothing much happens, and I get the following in backupData.sh.log:

20171006_165920	INFO	-------------------------------------
20171006_165920	ERROR	SSH connection test successful.
20171006_165920	ERROR	The source filesystem "Pool01/Misc" is in the same pool than the destination filesystem "Pool01/Misc"

Am I doing something wrong? It also occurs to me that perhaps the script requires the storage pool to have a different name, even when located on another server. Any comment?

Thanks again!
Chris

@fritz-hh fritz-hh added the bug label Nov 4, 2018
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

1 participant