Search the Community

Hello, I wounder if there is any way to reduce or compact the size of Jet database, we are using PlasticSCM for 5+ years now, and it is really great, but we are facing the issue with big database size. I was trying to workaround this issue using either: archive command or distributing database files on more than one hard drive 1- Archive command I read about the 'archive' command as the documentation says it is used to reduce the size of the database, so correct me if I am wrong what is the use of 'archive' command? Here is the documentation about archiving But I could not find any help regarding 'compact' command for Jet database 2- Distributing database on multiple hard drive Is there any way to specify hard drive per repository? or maybe specify multiple hard drives then using some rules if the first drive is almost full the database will start using the secondary drive and so on I also thought about using 'hardlink' (symlink) but I am not sure if that has a side effect on integrity or performance of Jet database Related post: Thanks,

Hi. I saw that Plastic 6 has an all new, super fast backend named Jet and got really curious about it. I didn't see anything mentioned about backups, so I decided to ask how it will work. Do you have to stop the server and copy the files like SQLite or is there support for backing the system up like SQL Server, where you can backup without stopping the server. Thanks!