PF sync has been started, but due to some issues (eg. network slowness) there is need to change the job.
Desired is using another server which is in another location and where connectivity is much better.
Replicating all PFs from the old to new PF server is not an option since the link is too slow.
Since there is no local replica on new target PF server and since the PF already exists in the org the tool will show the existing PF as grayed out (no replica) and the tool will create a new PF with an underscore or a number appended at the end.
QMM PF sync can only work with a folder or with a replica.
If there is no replica and replicating a folder is not possible then this approach can be used:
in target move the PF to Aelita Recycle Bin
re-enumerate the server or re-add the org (not absolutely needed)
create a new PF job and configure the tool to create the PF in target, this will work and new PF with the same name will be created, since there is no PF with such name in the org
Preserving the old job during the testing is a good idea, but in this case the PFs should be excluded from the PF sync (including subfolders) and collections should be disabled and agents stopped.
Later, when new job works as expected, the old job can be safely deleted.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center