Piartool and multiple collectives

Hello, I would like to ask about how piartool works.

In my case, I have multiple Collectives available in my PI SMT..

If I run piartool to register/unregister archives in the command line, does it only apply to the currently active Collective/s?

  • Hello ​ ,

    as far as I am aware piartool does not register / unregister archives on Collectives. You need to run piartool on the PI Data Archive host which you want to modify the archive registration on.

  • Thank you very much for your reply.

    Currently, I am running PI SMT on a QA PI server. I am quite new to PI so I still do not fully understand how all of this works.

    In PI SMT, it seems that I can select/deselect one or multiple Data archive servers at a time on the left side of the screen, and the displayed archives changes depending on the selected server.

    I initially thought that piartool will work depending on what I have currently selected on the PI SMT.

    In the documentation, I read something about Remote operation of PI Data Archive Utilities, but I don't fully understand it yet.

    I am looking to make a scheduled batch file to unregister archives and copy them to another drive and then register them.. We have one primary Production Data archive server and multiple secondary Data Archive Servers. Is this batch file possible to be run from one location? Or do we have to login to each server and set an individual batch file for each Data Archive server?

  • Welcome to the PI Community ​ !

    What's the intended use of this batch file?

    PI Backup supports VSS which stands for Volume Shadow copy Service. The great thing is that it allows to backup files while they are in use by another process. PI Backup allows you to capture backups without any service disruption or otherwise downtime.

    If you like to synchronize archives between the members of a PI Collective, PI Collective manager can do this. By the way, PI Collective Manager also takes a PI Backup of the Primary, copies it to Secondary nodes and registers it there.

    All members of a PI Data Archive Collective operate independently. There is certain information which is synched from Primary to Secondary nodes but e.g. archives are independent. To ensure all data arrives on all members of a PI Collective, use PI Buffer Subsystem to buffer on interface nodes and to fan the data to all members in the Collective.

  • Hello again, thank you for reply...

    We have a lot of data archive files (100s of GB worth I think) that we need to move to a new network drive location.

    I come across piartool and thought that we can make a batch file that will unregister an archive, copy that archive file to the new location, then register the copied archive.. Because we have a lot of archives, doing this by hand for each archive in the PI SMT will take a long time.

    In our collective, there is a primary Server and multiple secondary servers that all contain data archives that we need to move.

  • Hello ​ ,

    for this purpose a script could come in handy and I don't want to keep you away from pursuing this approach but it is also possible to unregister archive files in bulk using the corresponding plug-in for PI SMT (Operation -> Archives).

    Please be careful and consider taking a full PI Backup prior to taking any other action. Please do not unregister the Primary archive and make sure you have a listing of the archives as they are registered now. Piartool can be used to retrieve such an archive list.