.proi directory

[agaribay]

Right now our ".proi" directory is located on our C: drive. Considering
I.T. is not able to backup our workspaces, due to location, I was
wondering if we could change the directory to some other location.



If this is doable, do we need Admin rights to change? Details would be
nice.





* WF2



* Intralink 3.3





Thanks!



-Art








.

.

This message (including any attachments) contains

confidential and/or proprietary information intended

only for the addressee. Any unauthorized disclosure,

copying, distribution or reliance on the contents of this

information is strictly prohibited and may constitute a violation

of law. If you are not the intended recipient, please notify the

sender immediately by responding to this e-mail, and delete the

message from your system. If you have any questions about this

e-mail please notify the sender immediately.

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[SteveBarnhart]

Art,

You can change the location of the .proi directory by setting the variable as follows in a startup batch script:

set PDM_LDB_PATH=destination path

Keep in mind that each user will need their own .proi location. You can use a variable like %user_profile% in the destination path if your users have their own computer logins.

Typically, the .proi is stored locally for performance reasons. There may be other issues with creating a backup of the .proi also. Standard practice is to simply require users to check in theirchanges on a regular (daily) basis. Then the changes will be covered by the server database.

[ptc-2860737]

You can set your Workspace location anywhere you like as shown below,
however from my experience you can't just move a current Workspace to a
new drive letter because Ilink will be confused by the change in drive
letters. So you'll have to start new Workspaces in the new location.


Cheers

Doug Barton
Senior Mechanical Designer
Parker Hannifin Electronic Controls
Electronic Controls Division
1305 Clarence Avenue
Winnipeg, MB R3T 1T4 Canada
direct 204 453 3339 x309
fax 204 452 7156
-
www.parker.com/ecd





Steve Barnhart <->
03-10-2010 07:41 AM
Please respond to
Steve Barnhart <->


To
-
cc

Subject
[proesys] - RE: .proi directory






Art,
You can change the location of the .proi directory by setting the variable
as follows in a startup batch script:
set PDM_LDB_PATH=destination path
Keep in mind that each user will need their own .proi location. You can
use a variable like %user_profile% in the destination path if your users
have their own computer logins.
Typically, the .proi is stored locally for performance reasons. There may
be other issues with creating a backup of the .proi also. Standard
practice is to simply require users to check in their changes on a regular
(daily) basis. Then the changes will be covered by the server database.

Site Links: View post online View mailing list online Send new post
via email Manage your subscription Use of this email content is
governed by the terms of service at:

[FredericVannest]

It is good practice to check everything in and start with a new .proi,
but...
in the rare cases where it is needed to move the .proi to a new drive
letter, you can covert it to the new location:

ldbconvert <ldb_path> <flag_reset_userdata> <old_port@old_host>
<new_port@new_host> <old_file_path> <new_file_path>


I didn't find anything about it in the ptc knowledge base, so I guess it
is unsupported, but it works...
Used it for one of our users some time ago, this was the cmd I used:

C:\ptc\proiclient3.4\i486_nt\obj>ldbconvert c:\work\nva 1 7777@bvwsrv05
7777@bvwsrv05 d:\work\nva c:\work\nva

The syntax where you don't specify a server move didn't work for us, so
just trick it into moving from your ilink server to the same server...

Cheers,

Frederic
---
Frederic Vanneste
Development Engineer Mechanics
CAD Administrator
Security & Monitoring division
BARCO N.V.
Pres. Kennedypark 35
B-8500 Kortrijk

[JOES]

When we originally deployed Intralink about 10 years ago, we put the .proi
on our network drive. However, we had two cases of corrupted workspaces in
the first week. PTC claimed it was a result of a network issue & they
recommend keeping the .proi local. Unless you have a rock solid network,
you may experience the same issues.

That being said, I must admit, our network is anything but stable & never
has been. Network admin denies it, blames software, software/data guys
blame admin, we get nothing & are grateful to be employed. And I try to
regularly remind our users to check in daily no matter what.

Regards,
Joe S.

[DanielReid]

Our Australia division uses network drives for their .proi. I was
surprised when I found out but it works for them. If anyone wants more
details I could ask the admin there to comment.

Daniel