Saving/Backing-up your work?

[Kree8tiviT]

Altho I am fairly new to Trainz2006.......things are rapidly getting to the point where I am starting to have a substantial "investment" in time, energy, and effort.

Started building route....have imported a lot of my custom models for it, and like everyone, have a fair amount of downloaded content in use.

I know from my past experience doing this with Microsoft Trainsim...bad things WILL happen, just a matter of when........so with that in mind, ......

What is the best way to save/backup all this hard work?

Have read where some recommend copying the "local" folder to disc ( which I have done). Problem with that is the humongous size of the file folder, which will only keep getting larger and larger.....and no doubt most of you have even larger number of files. must be a better way?

Auran seems to like their "archive" method.........is this a viable alternative?
Have not yet gotten into all the ins-and-outs of that archive system.......and not even sure if it can be used for assets that are currently actively in use. Any dvantages to this?

Appreciate any thoughts/ideas.......as I hope to avoid the frustration of seeing months and months of work disappear as I have in the past with MSTS.

Regards,
Mark

 

[jytte]

Yea, things will happen, bet on it!

As you keep downloading things (and you will), you are going to have a huge backup no matter what.

You can archive all the files you've made and all the ones you've downloaded. Then backup the archive(s). That way you wouldn't be backing up the "native" content of TRS. But with all the maintenance that that involves (keeping track etc) I really don't think it's worth the trouble. Besides, your "custom" content will be far more than the "native" soon enough :hehe:

As you've probably read in other posts, people are backing up 20some gigs and more. You just learn to live with it. I suggest you get a big external drive, set it up for auto-backup (yes, local folder), and then you won't have to worry about a thing.

I only use archiving, when I want to move an entire route (including dependencies) to another computer.

That's my 2 cents worth.