auto saves inversion progressive

[wolf_72]

during the rescue cars, in the work directory you generate files in progression.... xxx.prt.3, xxx.prt.4, xxx.prt.5
and that makes me trouble back-up.
is it possible to reverse the progression so that the last saved file is always the xxx.prt.1?? ?

 

[nino67]

during the rescue cars, in the work directory you generate files in progression.... xxx.prt.3, xxx.prt.4, xxx.prt.5

Good morning, it's not about car rescues but "normal" saves! I don't know if you can reverse the sequence, you can avoid creating them, which is very unnotified. Alternatively, there are methods for "cleaning" folders, to be used before backup.

greetings

 

[wolf_72]

Good morning, it's not about car rescues but "normal" saves! I don't know if you can reverse the sequence, you can avoid creating them, which is very unnotified. Alternatively, there are methods for "cleaning" folders, to be used before backup.

greetings

using purge always leaves you the last progressive, the problem that when it does the end of the day backup I find myself a progressive higher than the one already saved and then in the backup I find them both, and so on... I think the only solution is to switch to a program that manages files (pdm or similar).

 

[nino67]

the pdm definitely solves you...... but it has a cost, not only cheap. I use windchill now and intralink before (used since the technician is now at the ced), indispensable in our structure! if you're not just generating documents... equipped with a pdm, otherwise you can think of creating some "apps" to rename the *.prt.xxx in *.prt.1 after purge!

 

[folle76]

you need to use a folder sync program rather than a backup program. your source folder to must be synchronized with the b backup folder so that all files not present in a and present in b are deleted by b and all files present in a and not present in b are added to b.

 

[folle76]

I used allwaysync successfully for years with such operation

 

[320i S]

the generation of the progressive rescue, can not be changed (windchill uses this procedure, although in a much more precise and precise way), remains the solution of mad76 for backups.
in 2018, however, I don't understand what the user's evening backups serve, working on the network and the servers of now, have cancelled these needs.