in our operation we have seen some file / folder ownership management problems (inability to take ownership) seen between relicated servers. ie a remote server is down = no way to transfer ownership to other servers / sites.
i think there is the need to have some improved functionality on this topic and other general topics relating to the replicated environment.
is it sufficient to accept that if a remote server is down that there is no way ever to get ownership back of files back? despite very short or zero lease times etc etc.
i would have thought that the provider server would be able to force ownership back to itself or other server if the files were not checked out. i have searched to no avail & also have been advised by our VAR group that we cannot do this.
if that is the case then i feel that with some consideration of improved functional development that this would be possible or at the least have something along the lines of automatical ownership transfer configure to send ownership from remote sites after hours, back to the server who owns the files again before business resumes the next day. that way if a site does not boot up at the start of business, the other remote servers have the choice to take ownership if it is urgent.
this may not be the answer but with sensible discussion and development there may be solutions to the situations that could arise.
If you've attempted to use the Refrence Repair Utility you'll quickly become frustrated it could really use some enhancements
In the settings I should be able to browse and select the Inventor Project File. The slash is opposite "/" to all other pathing in the settings and caused me some grief the first time I used this
I shouldn't have to close the utility when its done processing a folder. I should be able to pick a new folder and continue
I should be able to select multiple folders to process
It would be nice to be able to browse for folders to process
It can error and stop. As a script / batch processing utility it should just log the error and continue. There should be 0-interaction by the user until it is done
When it errors, it says to look at the log, but when you look at the log there is absolutely nothing about the error or what caused it to stop
I would assume that most people run the scan not on the server, apply the changes to the .xml not on the server, but then need to go to the server to import the fixes. It would be nice to be able to "push" the fixes from the same system used to scan and fix.
I use the command line to import the fixes but then need to use the ADMS Console logs to see any errors.... huh? The import needs to have its own GUI that writes its own log / error report
Once a file\folder is replicated from one site to another, the challenge is to unreplicate.
Currently there appears to be 2 options to unreplicate a file.
1) In the ADMS Console, edit the "Replicated Folder" and untick the folder that you want to unreplicate, then delete the file(s) from the vault, re-add it to the "unreplicated" folder. This will prevent the file from being replicated in future
2) Disable the Vault on the site, delete the local filestore, Enable it. This can be dangerous if the file is not present on at least one other site. Its OK if you know all files are replicated to at least one site.
The wish is to untick a folder in the "Replicated Folder" dialogue for that site and for the ADMS Console to check to see if that file appears on another site before allowing the Admin to unreplicate the folder. Once the check is completed, the files in the selected folder are removed from that sites filestore.
If you think this would be a useful enhancement, add a comment to this thread...
There should be a relatively simple option in ADMS to truncate data from the vault, or to backup just the configuration.
Doing an implementation at a publicly traded company means going to a multi-stage process (dev, test, UAT, Prod) with multiple vault environments to verify the configuration before go-live. It would be very convenient to be able to either remove all of the files from the vault to provide a clean starting point for a new environment.
Alternately, the option to backup JUST the configuration would be a huge help as well.