Planned for Future Release

Allow Backup of individual Server TMs

We sometimes find ourselves in a situation where we have made changes to a server TM and discover that the changes were not good.

With file-based TMs, we always create a simple backup copy of the TM and if things go wrong we just delete the faulty one and use the backup.

It would be great if in GS there were a feature to create a "snapshot" or a "backup" of a single TM that DOES NOT involve exporting to TMX and possible restarting from scratch.

Burckhardt Rueffer

  • Hi Luis,

    Using the Recycle Bin approach would be a workaround, assuming that restoring from it really and reliably works. I would still prefer to have a backup that I can put aside and restore if/when I need it. I can think of several use-cases where this might be helpful, in addition to the one suggested initially:

    - Remove server TMs when it is clear that they will not be needed for some time.

    - Better archiving (combining all project assets including TM), especially on large one-off projects.

    - Clutter-removal

    I am aware that much of it can be accomplished by exporting into TMX, but that can be a very time-consuming process and does not guarantee of full round-trip.

  • Hi all,

    Would a "recycle-bin" concept be helpful here. I.e. we keep the deleted TM for 30 days (or any other configurable time) and only then physically remove it and allow you to restore it during the 30 day period?

    Thanks,

    Luis

  • I would add that this should OF COURSE be available in GS Cloud as well.

    As a little tip I would suggest options to backup

    - max X backups

    - max X days old backups

    - max X megabytes of backups

    (one should be able to select any combination)

  • Hi Burckhardt,

    this is a good idea, since it would allow front-side admins to take care of such tasks. I guess you already know that on the SQL-side this is possible: Nightly backups and reimporting an SQL container for example.

    Andreas