fronttaya.blogg.se

Airport disk archive
Airport disk archive










airport disk archive

Really want to delete it because it might be valuable at some point. I would like to be able to selectively "archive" some of my data toĭisk (or cheaper storage) once it is no longer important. And if you ever needed it again, doing the reverse of my process above to get those keys back into your main redis-server would be fairly straightforward. Now, keep that rdb file somewhere for cheap, safe keeping. I then terminated that temporary redis-server and the memory was reclaimed. And now I have that rdb, which is just the content that I wanted to archive. I did a SAVE to ensure that the rdb file for that instance was up to date. Then, I wrote a short script that basically just called KEYS user_* (I understand the blocking nature of KEYS, my key space is so small it didn't matter, you can use SCAN if that is an issue for you.) Then, for each key, I MIGRATED them to that new redis-server instance. So, I started up another instance of redis-server, on another port locally (6380?) or another machine, it makes no difference. My archival needs were on a user basis, some user's data was no longer needed to be kept in redis. All of my keys were of the structure user_. I was benefited by the fact that my key space is segmented out by different users. Are there redis corollaries to these processes? Is there someway to make an rdb or aof file that is a subset of the data?Īny help or input on this matter would be appreciated! Hwang recently asked what I did, so I'm posting what I ended up doing. Or maybe I have to mysql database and I want to move one table to another database. sql file isn't directly useful to me, but I could reimport the data if/when I need it. If this were mysql, I would have my different tables and would very easily just dump it to a. I have quite a bit of data (very large bitmaps) associated with this data set, and frankly I can't afford the space once the id is no longer relevant or important. I can view them quite easily in with the command line, but I can't do anything with them, persay. So when I am done with id 4, I want to "archive" all all keys that match id_4_*. I don't really want to delete it because it might be valuable at some point.Īll of my keys are named id_. I would like to be able to selectively "archive" some of my data to disk (or cheaper storage) once it is no longer important.

airport disk archive

I am mostly familiar with persistence (rdb and aof). I have been using redis a lot lately, and really am loving it.












Airport disk archive