简体   繁体   English

以口是心非的方式将文件映射到卷?

[英]Mapping of file to volume in duplicity/duply?

Duplicity backs up my files as duplicity-full.TIMESTAMP.vol*.difftar.gz chunks where * is 1,2,3, ... . Duplicity 将我的文件备份为duplicity-full.TIMESTAMP.vol*.difftar.gz块,其中*是 1,2,3, ...。 On the other hand, ~/.cache/duplicity/profile/duplicity-full.TIMESTAMP.manifest contains volumes and file list:另一方面, ~/.cache/duplicity/profile/duplicity-full.TIMESTAMP.manifest包含卷和文件列表:

Hostname striker
Localdir /data/pnlpipe3/ukftractography
Volume 1:
    StartingPath   .  
    EndingPath     .git/objects/pack 3188
    Hash SHA1 d77131425a74f6f10eb5bc89ee4277805fb35e68
Volume 2:
    StartingPath   .git/objects/pack
    EndingPath     build/ITK/.git/objects/pack 743
    Hash SHA1 a983bb4e0379d6304da7aec9739a609b0704d270
...
...
Filelist 129500
    new      .git/FETCH_HEAD
    new      .git/HEAD
    new      .git/ORIG_HEAD
...
...

But given a file, is there a command in duplicity to find out which volume contains that file?但是给定一个文件,是否有口是心非的命令来找出哪个卷包含该文件? It is important for retrieving from glacier deep archive.这对于从冰川深层档案中检索很重要。 According to your man page, the user must manually migrate the storage type from glacier to standard before being able to retrieve a file.根据您的手册页,用户必须在能够检索文件之前手动将存储类型从冰川迁移到标准。 If I do not know which of my volumes contains my file, I won't know which volume to migrate.如果我不知道我的哪个卷包含我的文件,我就不知道要迁移哪个卷。 Migration has to be done by hand clicking through the web interface.必须通过 Web 界面手动单击来完成迁移。 So migrating all volumes is not an option either.因此,迁移所有卷也不是一种选择。

There is no command to find out which volume contains a file.没有命令可以找出哪个卷包含文件。 It is derived internally from the manifest by being between StartingPath and EndingPath of a volume.它是在卷的 StartingPath 和 EndingPath 之间从清单内部派生的。 However, even if you have that info, duplicity would still need to work it's way through the incremental files to restore the file entirely.但是,即使您有这些信息,口是心非仍然需要通过增量文件来完全恢复文件。

So, bottom line is that you need to de-glacier the backup and let duplicity reassemble the file to its former state.所以,最重要的是你需要消除备份的冰川,让口是心非的将文件重新组合到它以前的状态。 See here for an answer on incremental backup that shows how duplicity stores backups.请参阅此处以获取有关增量备份的答案,该答案显示了口是心非如何存储备份。

The original boto+s3 backend would de-glacier the files, but it's been replaced by boto3+s3 which does not have that capability, yet.原始的 boto+s3 后端会去除文件的冰川,但它已被 boto3+s3 取代,它还没有这种能力。 We are looking for volunteers to port that functionality over.我们正在寻找志愿者来移植该功能。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM