You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please would it make sense to store the target identifier passed at the initial synchronization to the target root dataset properties? The next run could read this identifier, without having to pass the correct one to the syncoid params.
IMO this could reduce the risk of entering an identifier which does not correspond to the given target.
Thanks a lot for any response.
With regards,
Pavel.
The text was updated successfully, but these errors were encountered:
My use case is quite standard - several local backup drive sets, basically rotated (but with skips). Since the synchronization command should use the --identifier param corresponding to the given drive in such case, there is quite a high chance of mistake. That's why I am wondering whether the drive-set specific identifier could be read from some custom property on the target, e.g. optionally, with some --use-stored-identifier option...
Hi,
Please would it make sense to store the target identifier passed at the initial synchronization to the target root dataset properties? The next run could read this identifier, without having to pass the correct one to the syncoid params.
IMO this could reduce the risk of entering an identifier which does not correspond to the given target.
Thanks a lot for any response.
With regards,
Pavel.
The text was updated successfully, but these errors were encountered: