Register / Login | Desktop view |
Prion wrote:I am somewhat new to this and would like to set up two different capture strategies that would
1) capture the entire system, preferrably overnight after which the system would be put to sleep or switched off
2) capture whatever might be worth capturing in terms of data in my user's space (Documents, Pictures, Movies, Music, etc.)
Question 1:
I imagine that capturing software while it is running is asking for trouble, so presumably I would need to be running a different operating system of the same type (10.6 in my case running on the 2.5 USB drive) to backup my main harddrive in the MBP. Likewise, I would need to be logged out for capturing my user data (task #2). Correct? How do I set this up then?
If so, this would limit my backup frequency in particular for task #2 because I would then let it run at noon and at night. Perhaps that is sufficient but I don't know. How do you handle this? I cannot imagine logging our every hour for my backup to take place.
Question 2:
Can I rename a drive that I previously captured data to with Qrecall and still continue capturing data to or restoring data from?
Can I copy the content of the 2.5 drive to another drive (with a different name) and use that drive to boot from? I would assume that I would need to use CarbonCopyCloner to keep the new drive bootable (or can I use Diskutil?).
Question 3:
Playing around with the TimeCapsule it seems as though QRecall is perfectly willing to accept an external harddrive connected to the TimeCapsule's USB port.
At least while I am at home (near the TCapsule) I would prefer to archive to that disk because then I would not need to connect and unconnect the drives used for backup.
Question 4:
I am unsure if I should include the user data also in the system backup to have some redundancy or if that just fills the thing up too quickly.
Since I cannot easily prune the user data if I find that the case it might be worth asking you pros here.
Question 5: What do I need to do to ensure that my backup is safe on the one hand but that I will be able to restore a backup and not fail because of insufficient privileges over the files to be restored?
I know, many questions and I would appreciate your help very much
James Bucanek wrote:
Remove the Ignore If No Archive conditional from the hourly capture of your home folder. The action will run regardless of whether your network volume is mounted or not. If the volume can be mounted, QRecall will mount it and run. It the volume isn't available, QRecall will complain.
Ben Bass wrote:I was wondering if there was a way to keep the QRecall archive on a network volume, have it auto-mount when the volume is available, but not have QRecall or the OS complain that the network volume is unreachable.
I saw some early comments about a command line version, which would be awesome as I could write my own scripts if necessary where I can check which network they are on and have the archiving cleanly fail if they are not.
James Bucanek wrote:Ben Bass wrote:I was wondering if there was a way to keep the QRecall archive on a network volume, have it auto-mount when the volume is available, but not have QRecall or the OS complain that the network volume is unreachable.
Not at this time. QRecall will attempt to auto-mount any volume before an action begins, but a failure to mount that volume is considered a fatal error, and QRecall will complain about it.
If this is something that people would like, I can put it on the to-do list.
I saw some early comments about a command line version, which would be awesome as I could write my own scripts if necessary where I can check which network they are on and have the archiving cleanly fail if they are not.
A command line version is definitely in the works. Right now, QRecall is undergoing a lot of testing. It just had its core file system logic completely rewritten so it uses Apple's approved APIs. It's going to need a lot of testing before I spring it on any unexacting beta testers.
James Bucanek wrote:Ben Bass wrote:I was wondering if there was a way to keep the QRecall archive on a network volume, have it auto-mount when the volume is available, but not have QRecall or the OS complain that the network volume is unreachable.
Not at this time. QRecall will attempt to auto-mount any volume before an action begins, but a failure to mount that volume is considered a fatal error, and QRecall will complain about it.
If this is something that people would like, I can put it on the to-do list.
I saw some early comments about a command line version, which would be awesome as I could write my own scripts if necessary where I can check which network they are on and have the archiving cleanly fail if they are not.
A command line version is definitely in the works. Right now, QRecall is undergoing a lot of testing. It just had its core file system logic completely rewritten so it uses Apple's approved APIs. It's going to need a lot of testing before I spring it on any unexacting beta testers.