Purge Script

[Anonymous]

Hello,

I prepared simple script for purging Vault and added it to windows task scheduler (just like backup script)

"C:\Program Files\Autodesk\ADMS 2018\ADMS Console\Connectivity.ADMSConsole.exe" -Opurge -N"Projects" -KEEPVERS1 -MINAGE21 -VUAdmin_name -VPAdmin_password -L"\\10.2.0.138\Kopie zapasowe\Vault\Vault_Purge.log"

In place of Admin_name and Admin_password i just put my login and password to ADMSC  (no spaces and quote marks, just like typed above). Vault name is quote marks.

The result in log is:

9/21/2018 10:00:08 PM ==== DataManagement.Common.Logging: DISABLED ====
9/21/2018 10:00:08 PM ==== Logging initiated: Core server version 23.3.21.0 ====
9/21/2018 10:00:08 PM  
9/21/2018 10:00:08 PM -Opurge -N"Rfmah" -KEEPVERS1 -MINAGE21 -EXCLCMTDo not purge -VU[username] -VP[password] -L"\\Server1\Backup\Vault\Vault_Purge.log" 
9/21/2018 10:00:09 PM Connectivity.Request.Common.RequestLibrary - RequestRuntimeStop()
9/21/2018 10:00:09 PM Connectivity.Request.Vault.RequestLibrary - RequestRuntimeStop()
9/21/2018 10:00:09 PM Connectivity.Request.Foundation.RequestLibrary - RequestRuntimeStop()
9/21/2018 10:00:09 PM Connectivity.Request.Document.RequestLibrary - RequestRuntimeStop()

The purge isn't performed. What may be the possible reason ?

Best Regards,

ZZ 

[psaarloos]

Hi,

Try to write the log file to a location on the machine itself (eg. C:\Temp\Purgelog.log). The ADMS Console probably hasn't got permissions on the network drive because out of the box ADMS is using the default local AutodeskVault account.

[reidmatthew]

Hi @Anonymous, thanks for posting to the Vault forums.

Have you had any success with the suggestions from @psaarloos?

I have a few additional thoughts of things to consider and try from your end. First, it looks like your purge script is executed successfully from the log file snippet you provided. However, you claim that the desired files are not actually purged from your Vault. I wonder if there are purge version rules or exceptions you are running into which are excluding files from being purged. I would suggest you look into purging a Vault from the Data Management Server Console (ADMS) interface first to get the proper rules and exceptions before attempting to purge from a command script. Specifically, I would recommend you also look at the "UNCONTROLLED" switch in the purge script switch list. This UNCONTROLLED switch corresponds to the "Purge versions not controlled by lifecycles" checkbox in the Purge Files dialog in the ADMS when trying to purge a Vault.

Let us know if you have questions.

[tapani.kuikka]

Hello!, i am replying to this old thread, as i have more questions on the purge switches in the script or in the ADMS.

What does the switch "Purge versions not controlled by lifecycles" do?, is it only applying the purge to the files that are outside of any lifecycle in Vault?

When the "Purge versions not controlled by lifecycles" -check is checked, only then you can select "Versions except latest", "Versions older than days", "Exclude versions where comment contains" -options, so does this mean that we cannot purge by those manually set rules files that are controlled by a lifecycle?

Again when a purge is run without the "Purge versions not controlled by lifecycles" -checkbox active, then the Vault will purge files that are controlled by a lifecycle, and only will look the lifecycle rules of versions kept etc. ?

This behavior is the same for the purge script vs. manual purge files from ADMS?

So if this is right there is no way of controlling how many versions are kept from files that are in a lifecycle? For example i have a non-released state in my lifecycle, and it has controlled versions "first and last", and those are kept when Vault is purged, no matter what switches i have active (KEEPVERS5, Exclude comments, etc)?

The problem is that i really would like to keep more than just "first and last" version from my files in non-released lifecycle state, but i have not found any way to purge in a manner that would allow that?

Thanks!

[jentsch]

I have the same question. As I understand there ist no possibility to combine the rules with the rules of files which have a lifecycle. For example: I want to keep the last 5 versions of files which are younger than 60 days and have the state "in progress". But because these files have a lifecycle only the first and last Version will not be deleted. Is there a possibility to combine the rules of the lifecycle definition and the additional settings? Thanks.

---

@tapani.kuikka wrote:

Hello!, i am replying to this old thread, as i have more questions on the purge switches in the script or in the ADMS.

What does the switch "Purge versions not controlled by lifecycles" do?, is it only applying the purge to the files that are outside of any lifecycle in Vault?

When the "Purge versions not controlled by lifecycles" -check is checked, only then you can select "Versions except latest", "Versions older than days", "Exclude versions where comment contains" -options, so does this mean that we cannot purge by those manually set rules files that are controlled by a lifecycle?

Again when a purge is run without the "Purge versions not controlled by lifecycles" -checkbox active, then the Vault will purge files that are controlled by a lifecycle, and only will look the lifecycle rules of versions kept etc. ?

This behavior is the same for the purge script vs. manual purge files from ADMS?

So if this is right there is no way of controlling how many versions are kept from files that are in a lifecycle? For example i have a non-released state in my lifecycle, and it has controlled versions "first and last", and those are kept when Vault is purged, no matter what switches i have active (KEEPVERS5, Exclude comments, etc)?

The problem is that i really would like to keep more than just "first and last" version from my files in non-released lifecycle state, but i have not found any way to purge in a manner that would allow that?

Thanks!

---