![]() It also provide an -ignore option that can be used to skip certain repositories when deciding the deletion criteriaĭoes that mean that the ignore option makes the snapshot immune against deletion or the opposite? There also seems to be a confusion with the term “repository” and “snapshot”. to tell the prune command to simply leave it alone? The only thing I can find is the -ignore option but I don’t quite understand what it does. Now here is a crucial question: how do I make sure that that snapshot never gets deleted (since it’s the only one with those (deleted) crashplan files)? Is there any way to mark a snapshot as “untouchable”, i.e. I’ll probably tag that snapshot sith “crashplan” or something so that I know where to find those crashplan files, should I ever need them. ![]() I’ll just include the folder in my existing repository and delete it once it has been backed up. Maybe recently, or maybe two years ago.Īnyway, the basic idea is that I restore the latest version of all files in my CrashPlan archive into a separate folder (not to the original location) and then I’ll simply back up that folder.įirst I thought I’d create a separate repository for that folder, but then I figured that is not necessary (or perhaps even disadvantageous). Simply because chances are that at least one of them has been deleted by mistake. My main aim in this whole exercise is to copy over the latest version of all files I ever backed up, including (and in particular) the ones that have in the meantime been deleted (I have CrashPlan set to keep at least one version of every file, no matter what). So, to start with, I think I can live with losing the the different versions/revisions of my backed up files that I can currently still access in CrashPlan. It seems that you did not installed mine, but the one from gfjardim.I have this idea about how I might be able to preserve some of my backup archive from CrashPlan when changing to Duplicacy and I wonder what the pitfalls might be or if there is a better strategy. NOTE: There are 2 CrashPlan dockers available in the Community Applications. Select the /win_share folder (or one on its subfolders) as the backup destination. win_share).Īfter applying the settings, access the CrashPlan GUI. With this plugin, you will be able to mount your Windows share on unRAID.Įdit the CrashPlan docker container settings and click the Add another Path, Port or Variable link.Īdd a new path, where the host path will be your mounted share (should be under /mnt/ I guess). If you don't want to install CrashPlan on your Windows server, then I think the following way should work (never tried).įirst, install the Unassigned Devices plugin. Select it and click the Start Backup button. You should see in the list your Windows server. From CrashPlan on unRAID, select the Destinations tab on the left and then the Computers tab on the top. If CrashPlan is installed on both your unRAID and Windows servers, then your Windows server can be a backup destination for unRAID. Warning! Make sure to read the Taking Over Existing Backup section from the documentation if you are installing this container to replace another CrashPlan installation (from Windows, Linux, Mac or even another Docker container). Post any questions or issues relating to this docker in this thread. Make sure to look at the complete documentation, available on Github ! It also has a very nice, mobile-friendly web UI to access CrashPlan's graphical interface, no misleading errors in log and is actively supported! Unlike other containers, this one is based on Alpine Linux, meaning that its size is very small (at least 50% smaller). Make sure to look at the support thread for more details. If you choose to migrate to CrashPan PRO, you can do it easily by installing my CrashPlan PRO docker container. Read the entire announcement and FAQ over at the CrashPlan for Home site. Users are offered to migrate to CrashPlan PRO (aka CrashPlan for Small Business) or Carbonite. CrashPlan for Home will no longer be available for use starting October 23, 2018. Effective August 22, 2017, Code42 will no longer offer new – or renew – CrashPlan for Home subscriptions, and we will begin to sunset the product over several months.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |