Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-27 Thread 'awokd' via qubes-users
On Tue, December 26, 2017 8:48 pm, yreb...@riseup.net wrote:
> On 2017-12-26 10:14, awokd wrote:
>
>> On Tue, December 26, 2017 7:15 pm, yreb...@riseup.net wrote:
>>
>>> fwiw, I am unable to actually add backupVM diskspace for the same
>>> reason, duh.  I think my only option is to remove the huge dom0 file ,
>>> but I'm still wondering how do I get a system wide understanding of
>>> how 3.2  is using the 1GB  HD,  seems should be otherwise plenty of
>>> room to run 3.2 ... sigh
>>>
>>
>> In dom0, do
>> cd / du -hd1
>>
>> then cd into large directories and repeat du -hd1.
>
> Ok, thx
>
>
> only thing seems strange is in a Debian AppVM (my only Deb AppVM)  I have
> 2 files private.img and volatile.img  which  end up  *near 1.3Gb
> any idea  if this is normal ?

1.3GB is not a lot of space so yes, that's pretty normal.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0b878405adff195a3029c5c13f9f5431.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-26 Thread yrebstv
On 2017-12-26 10:14, awokd wrote:
> On Tue, December 26, 2017 7:15 pm, yreb...@riseup.net wrote:
>> fwiw, I am unable to actually add backupVM diskspace for the same reason,
>> duh.  I think my only option is to remove the huge dom0 file , but I'm
>> still wondering how do I get a system wide understanding of how 3.2  is
>> using the 1GB  HD,  seems should be otherwise plenty of room to run 3.2
>> ... sigh
> 
> In dom0, do
> cd /
> du -hd1
> 
> then cd into large directories and repeat du -hd1.

Ok, thx

only thing seems strange is in a Debian AppVM (my only Deb AppVM)  I
have 2 files private.img and volatile.img  which  end up  *near 1.3Gb   
any idea  if this is normal ?




-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3400f0c49c70f0f85b09e13f436bc599%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-26 Thread 'awokd' via qubes-users
On Tue, December 26, 2017 7:15 pm, yreb...@riseup.net wrote:
> fwiw, I am unable to actually add backupVM diskspace for the same reason,
> duh.  I think my only option is to remove the huge dom0 file , but I'm
> still wondering how do I get a system wide understanding of how 3.2  is
> using the 1GB  HD,  seems should be otherwise plenty of room to run 3.2
> ... sigh

In dom0, do
cd /
du -hd1

then cd into large directories and repeat du -hd1.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/39687cdd55b534d5e5930247568256b5.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-26 Thread yrebstv
fwiw, I am unable to actually add backupVM diskspace for the same
reason, duh.  I think my only option is to remove the huge dom0 file ,
but I'm still wondering how do I get a system wide understanding of how 
3.2  is using the 1GB  HD,  seems should be otherwise plenty of room to 
run 3.2 ... sigh

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/84c38c96a40f58423c01f4ba3e75980c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-26 Thread yrebstv

 re: /var/tmp  is  dom0  I am unable  to  cut and paste  from
 dom0 what I see is /dev/mapper/qubes_dom0-root  952848292
 780151168(used) 123272164(available) 87%   / and various others
 smaller directories   ; I don't know what a "partial restore"
 would look like ; I never touch dom0 :0

>>>
>>> It would be some large directories in /var/tmp that start with
>>> `restore_`. But it sounds like that's not your problem. Pretty
>>> sure it's what we diagnosed above (large backups in dom0 home).
>>>
>>
>> - And *Once something is in dom0  files  it can't be moved
>> *out to any other VMs ,
> 
> You can move files from dom0 to other VMs:
> 
> https://www.qubes-os.org/doc/copy-from-dom0/
> 
>> so guess I need to  delete the  large  AppVM backup, that is
>> *indeed in dom0 /home   and re-back it up to an another internal
>> HD  would seem to be preferable , that backing up to dom0 to
>> dom0 (since I guess I'll be backing up "everything" and if that's
>> too large then maybe I'll skip the Templates...

Well I rm 'd all but the 1 large successful photo AppVM. And instead of
re-backing it up to backupVM (AppVM) I attached another internal HD to
the backupVM and am trying to back to it( by 1st doing qvm-copy-to-vm
   , however it's complaining  "qfile-dom0-agent: File
copy: no space left on device" 

I do note that whatever qubes_dom0-root ?file is above is stating 87%
used . (this qubest install is running on a 1GB HD there should be
plenty of run, I have a lot of AppVM perhaps each one walls off a
certain amount of the HD whether they are used or not ?  or perhaps I
need to allow   backupVM  AppVM  more "Basic-> Disk storage -> private
storage max size: which is currently set to 2048MB ? l0l change that to
512000 MB   maybe ?




>> But, again just curious,  are the Templates , Whonix, and AppVMs,
>> dom0 going to be *importable   into   Qubes 4.0  ?  in general , I
>> don't really use Deb-8  which it sounds like will be in Q4.0, and
>> Fedora's Templates will be F26  *not F25 ... ?
>>
> 
> I haven't personally experimented with this much, so I'll leave it to
> someone who has done so to comment on whether it's possible.


Isn't part of the purpose for a 3.2  backup  being to enable to
eventually   "import" their  VMs  into  4.0  from 3.2  ???   Seems to me
this would be something basic  task that folks  are going to do? 
or maybe it's so trivial  for all  the  pro users out there , doesn't
need commenting ?  

or:  if 4.0  is going to come stock  with Fedora 26 ,  are  AppVMs 
based on Fedora 25  even  going to be  "import"-able   into  4.0 ?   
I'd really not have to re-tweak all my Firefox  instances again for
example  :)


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/54c0c72dd023e1bc2477006d6a1d7206%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-25 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-12-25 12:44, yreb...@riseup.net wrote:
> On 2017-12-24 16:01, Andrew David Wong wrote:
>> 
>> On 2017-12-24 19:08, yreb...@riseup.net wrote:
>>> On 2017-12-23 11:11, Andrew David Wong wrote:
 On 2017-12-22 21:30, yreb...@riseup.net wrote:
> On 2017-12-22 09:50, awokd wrote:
>> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via 
>> qubes-users wrote:
>>> On Friday, 22 December 2017 02:42:57 CET 
>>> yreb...@riseup.net wrote:
>>> 
 assuming 4.0 is going to come out of the box with 
 like Debian 9 and Fed 26?
>> 
>> If you have room for it, back up everything! You can 
>> restore selectively later.
> 
> thanks for the two replies, *However, neither gets to the 
> gist of my inquiry. Namely, which VMs am I supposed to be 
> backing up,
 
 You should back up every VM that contains data that you don't
 want to lose and can't replace. For most people, this means
 backing up every VM that contains things like documents,
 emails, photos, and videos. If you're short on space, it's
 not necessary to make backups of things that you know you'll
 be able to download easily again later (e.g., an unmodified
 TemplateVM).
 
> Dom0 (which for some reason is over *500GB!)  , hence  I 
> can't backup "everything" even with a 2GB internal HD that 
> I'm trying to use
> 
 
 For most users, the main reason to back up dom0 is because 
 that's where your dom0 user settings are stored. Normally, 
 dom0 should not be that large, since you're only backing up 
 the home directory. (You're using qvm-backup, right?) It 
 sounds like you didn't expect it to be that large, so if 
 there's not enough data in your home directory to account
 for it, check /var/tmp to see if you have a lot of partial 
 restores taking up space.
 
> I was thinking of skipping the 1 large offline AppVM where 
> I keep old photos, and did, so why did  the Templates and 
> Dom0 come out to such a *Huge filesize,   what would be 
> typical ???
> 
>> From what your saying can I skip the Debian 8 Template, I
>> have 2 AppVMs
> and the Whonix stuff based on it I guess
> 
>>> 
>>> 
>>> What is the default backup location from the GUI VM Manager
>> 
>> It looks like the default is dom0. (Not sure, since I usually
>> use the CLI, but I just tried going through the first few prompts
>> in the GUI, and the default target was dom0.)
>> 
>>> : I'm wondering now where I backed up my 300GB VM with old 
>>> photos back in May 2017 maybe that has something to do
>>> with the size problem I'm encountering .. I probably wanna
>>> know where is it anyway. I don't think I thought to change it
>>> from the default setting, as I was new, and still am to what 
>>> behaviour to expect from Qubes systems ...and just let it back 
>>> up where-ever the default would be.
>>> 
>> 
>> Yeah, it sound like you probably have ~500GB worth of backups in 
>> your dom0 home directory. You'll probably want to move those to 
>> another location before backing up dom0 (if you don't want to 
>> include those backups in your backup).
>> 
>>> PS: keeping in mind, my perhaps, *only reason to be attempting 
>>> a backup would be to migrate it to 4.0  ,
>> 
>> I recommend making frequent backups (so that you don't lose data 
>> in an unexpected hardware or software malfunction), not just for 
>> migration.
>> 
>>> so I  *still want to back up Templates and Dom0??
>> 
>> That really depends on you. The answer will be different for 
>> different people. The main consideration is whether you have any 
>> data in dom0's home or in your TemplateVMs that you don't want
>> to lose. Personally, I would back everything up just in case.
>> You may not end up using it all in the migration process, but
>> the problem is that you may not be entirely certain, before that 
>> process is complete, which data you will want to have migrated. 
>> In hindsight, you may wish you had migrated more. You can always 
>> exclude data you have, but you can't include data you no longer 
>> have.
>> 
>>> Most of my AppVMs are just for browsing the web and the 15 
>>> different times, I've reset up  firefox with perhaps a few 
>>> downloads . considering that would there be some reason to
>>>  backup AppVMs .
>>> 
>>> 
>>> Maybe the only VM that matters *is the 300GB AppVM with photos 
>>> in it , that stays offline ?
>>> 
>> 
>> Again, it really just depends on what data you want to keep. 
>> Given your uncertainty, I highly recommend backing up 
>> *everything* so that you don't regret losing something later. It 
>> sounds like you're talking about less than a terabyte in total, 
>> which is a pretty small amount of data relative to hard drive 
>> capacities these days. Better safe than sorry!
>> 
>>> 
>>> re: /var/tmp  is  dom0  I am unable  to  cut and paste  

Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-25 Thread yrebstv
On 2017-12-24 16:01, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-12-24 19:08, yreb...@riseup.net wrote:
>> On 2017-12-23 11:11, Andrew David Wong wrote:
>>> On 2017-12-22 21:30, yreb...@riseup.net wrote:
 On 2017-12-22 09:50, awokd wrote:
> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via
> qubes-users wrote:
>> On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net
>> wrote:
>>
>>> assuming 4.0 is going to come out of the box with like
>>> Debian 9 and Fed 26?
>
> If you have room for it, back up everything! You can restore
>  selectively later.

 thanks for the two replies, *However, neither gets to the gist
 of my inquiry. Namely, which VMs am I supposed to be backing
 up,
>>>
>>> You should back up every VM that contains data that you don't
>>> want to lose and can't replace. For most people, this means
>>> backing up every VM that contains things like documents, emails,
>>> photos, and videos. If you're short on space, it's not necessary
>>> to make backups of things that you know you'll be able to
>>> download easily again later (e.g., an unmodified TemplateVM).
>>>
 Dom0 (which for some reason is over *500GB!)  , hence  I can't
  backup "everything" even with a 2GB internal HD that I'm
 trying to use

>>>
>>> For most users, the main reason to back up dom0 is because that's
>>> where your dom0 user settings are stored. Normally, dom0 should
>>> not be that large, since you're only backing up the home
>>> directory. (You're using qvm-backup, right?) It sounds like you
>>> didn't expect it to be that large, so if there's not enough data
>>> in your home directory to account for it, check /var/tmp to see
>>> if you have a lot of partial restores taking up space.
>>>
 I was thinking of skipping the 1 large offline AppVM where I
 keep old photos, and did, so why did  the Templates and Dom0
 come out to such a *Huge filesize,   what would be typical ???

> From what your saying can I skip the Debian 8 Template, I
> have 2 AppVMs
 and the Whonix stuff based on it I guess

>>
>>
>> What is the default backup location from the GUI VM Manager
> 
> It looks like the default is dom0. (Not sure, since I usually use the
> CLI, but I just tried going through the first few prompts in the GUI,
> and the default target was dom0.)
> 
>> : I'm wondering now where I backed up my 300GB VM with old photos
>> back in May 2017 maybe that has something to do with the size
>> problem I'm encountering .. I probably wanna know where is it
>> anyway. I don't think I thought to change it from the default
>> setting, as I was new, and still am to what behaviour to expect
>> from Qubes systems ...and just let it back up where-ever the
>> default would be.
>>
> 
> Yeah, it sound like you probably have ~500GB worth of backups in your
> dom0 home directory. You'll probably want to move those to another
> location before backing up dom0 (if you don't want to include those
> backups in your backup).
> 
>> PS: keeping in mind, my perhaps, *only reason to be attempting a
>> backup would be to migrate it to 4.0  ,
> 
> I recommend making frequent backups (so that you don't lose data in an
> unexpected hardware or software malfunction), not just for migration.
> 
>> so I  *still want to back up Templates and Dom0??
> 
> That really depends on you. The answer will be different for different
> people. The main consideration is whether you have any data in dom0's
> home or in your TemplateVMs that you don't want to lose. Personally, I
> would back everything up just in case. You may not end up using it all
> in the migration process, but the problem is that you may not be
> entirely certain, before that process is complete, which data you will
> want to have migrated. In hindsight, you may wish you had migrated
> more. You can always exclude data you have, but you can't include data
> you no longer have.
> 
>> Most of my AppVMs are just for browsing the web and the 15
>> different times, I've reset up  firefox with perhaps a few
>> downloads . considering that would there be some reason to
>> backup AppVMs .
>>
>>
>> Maybe the only VM that matters *is the 300GB AppVM with photos in
>> it , that stays offline ?
>>
> 
> Again, it really just depends on what data you want to keep. Given
> your uncertainty, I highly recommend backing up *everything* so that
> you don't regret losing something later. It sounds like you're talking
> about less than a terabyte in total, which is a pretty small amount of
> data relative to hard drive capacities these days. Better safe than
> sorry!
> 
>>
>> re: /var/tmp  is  dom0  I am unable  to  cut and paste  from  dom0
>> what I see is /dev/mapper/qubes_dom0-root  952848292
>> 780151168(used) 123272164(available) 87%   / and various others
>> smaller directories   ; I don't know what a "partial restore"
>> would look like ; I never touch 

Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-24 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-12-24 19:08, yreb...@riseup.net wrote:
> On 2017-12-23 11:11, Andrew David Wong wrote:
>> On 2017-12-22 21:30, yreb...@riseup.net wrote:
>>> On 2017-12-22 09:50, awokd wrote:
 On Fri, December 22, 2017 10:29 am, 'Tom Zander' via 
 qubes-users wrote:
> On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net
> wrote:
> 
>> assuming 4.0 is going to come out of the box with like 
>> Debian 9 and Fed 26?
 
 If you have room for it, back up everything! You can restore
  selectively later.
>>> 
>>> thanks for the two replies, *However, neither gets to the gist 
>>> of my inquiry. Namely, which VMs am I supposed to be backing 
>>> up,
>> 
>> You should back up every VM that contains data that you don't 
>> want to lose and can't replace. For most people, this means 
>> backing up every VM that contains things like documents, emails, 
>> photos, and videos. If you're short on space, it's not necessary 
>> to make backups of things that you know you'll be able to 
>> download easily again later (e.g., an unmodified TemplateVM).
>> 
>>> Dom0 (which for some reason is over *500GB!)  , hence  I can't
>>>  backup "everything" even with a 2GB internal HD that I'm
>>> trying to use
>>> 
>> 
>> For most users, the main reason to back up dom0 is because that's
>> where your dom0 user settings are stored. Normally, dom0 should
>> not be that large, since you're only backing up the home 
>> directory. (You're using qvm-backup, right?) It sounds like you 
>> didn't expect it to be that large, so if there's not enough data 
>> in your home directory to account for it, check /var/tmp to see 
>> if you have a lot of partial restores taking up space.
>> 
>>> I was thinking of skipping the 1 large offline AppVM where I 
>>> keep old photos, and did, so why did  the Templates and Dom0 
>>> come out to such a *Huge filesize,   what would be typical ???
>>> 
 From what your saying can I skip the Debian 8 Template, I 
 have 2 AppVMs
>>> and the Whonix stuff based on it I guess
>>> 
> 
> 
> What is the default backup location from the GUI VM Manager

It looks like the default is dom0. (Not sure, since I usually use the
CLI, but I just tried going through the first few prompts in the GUI,
and the default target was dom0.)

> : I'm wondering now where I backed up my 300GB VM with old photos 
> back in May 2017 maybe that has something to do with the size 
> problem I'm encountering .. I probably wanna know where is it 
> anyway. I don't think I thought to change it from the default 
> setting, as I was new, and still am to what behaviour to expect 
> from Qubes systems ...and just let it back up where-ever the 
> default would be.
> 

Yeah, it sound like you probably have ~500GB worth of backups in your
dom0 home directory. You'll probably want to move those to another
location before backing up dom0 (if you don't want to include those
backups in your backup).

> PS: keeping in mind, my perhaps, *only reason to be attempting a 
> backup would be to migrate it to 4.0  ,

I recommend making frequent backups (so that you don't lose data in an
unexpected hardware or software malfunction), not just for migration.

> so I  *still want to back up Templates and Dom0??

That really depends on you. The answer will be different for different
people. The main consideration is whether you have any data in dom0's
home or in your TemplateVMs that you don't want to lose. Personally, I
would back everything up just in case. You may not end up using it all
in the migration process, but the problem is that you may not be
entirely certain, before that process is complete, which data you will
want to have migrated. In hindsight, you may wish you had migrated
more. You can always exclude data you have, but you can't include data
you no longer have.

> Most of my AppVMs are just for browsing the web and the 15 
> different times, I've reset up  firefox with perhaps a few 
> downloads . considering that would there be some reason to 
> backup AppVMs .
> 
> 
> Maybe the only VM that matters *is the 300GB AppVM with photos in 
> it , that stays offline ?
> 

Again, it really just depends on what data you want to keep. Given
your uncertainty, I highly recommend backing up *everything* so that
you don't regret losing something later. It sounds like you're talking
about less than a terabyte in total, which is a pretty small amount of
data relative to hard drive capacities these days. Better safe than
sorry!

> 
> re: /var/tmp  is  dom0  I am unable  to  cut and paste  from  dom0 
> what I see is /dev/mapper/qubes_dom0-root  952848292 
> 780151168(used) 123272164(available) 87%   / and various others 
> smaller directories   ; I don't know what a "partial restore"
> would look like ; I never touch dom0 :0
> 

It would be some large directories in /var/tmp that start with
`restore_`. But it sounds like that's not your problem. Pretty 

Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-24 Thread yrebstv
On 2017-12-23 11:11, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-12-22 21:30, yreb...@riseup.net wrote:
>> On 2017-12-22 09:50, awokd wrote:
>>> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via qubes-users
>>>  wrote:
 On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net
 wrote:

> assuming 4.0 is going to come out of the box with like Debian
> 9 and Fed 26?
>>>
>>> If you have room for it, back up everything! You can restore
>>> selectively later.
>>
>> thanks for the two replies, *However, neither gets to the gist of
>> my inquiry. Namely, which VMs am I supposed to be backing up,
> 
> You should back up every VM that contains data that you don't want to
> lose and can't replace. For most people, this means backing up every
> VM that contains things like documents, emails, photos, and videos. If
> you're short on space, it's not necessary to make backups of things
> that you know you'll be able to download easily again later (e.g., an
> unmodified TemplateVM).
> 
>> Dom0 (which for some reason is over *500GB!)  , hence  I can't
>> backup "everything" even with a 2GB internal HD that I'm trying to
>>  use
>>
> 
> For most users, the main reason to back up dom0 is because that's
> where your dom0 user settings are stored. Normally, dom0 should not be
> that large, since you're only backing up the home directory. (You're
> using qvm-backup, right?) It sounds like you didn't expect it to be
> that large, so if there's not enough data in your home directory to
> account for it, check /var/tmp to see if you have a lot of partial
> restores taking up space.
> 
>> I was thinking of skipping the 1 large offline AppVM where I keep
>> old photos, and did, so why did  the Templates and Dom0  come out
>> to such a *Huge filesize,   what would be typical ???
>>
>>> From what your saying can I skip the Debian 8 Template, I have 2
>>>  AppVMs
>> and the Whonix stuff based on it I guess
>>
> 
> - -- 
> Andrew David Wong (Axon)


What is the default backup location from the GUI VM Manager : I'm
wondering now where I backed up my 300GB VM with old photos back in May
2017 maybe that has something to do with the size problem I'm
encountering .. I probably wanna know where is it anyway. I don't
think I thought to change it from the default setting, as I was new, and
still am to what behaviour to expect from Qubes systems ...and just let
it back up where-ever the default would be. 

PS: keeping in mind, my perhaps, *only reason to be attempting a backup
would be to migrate it to 4.0  , so I  *still want to back up Templates
and Dom0??  Most of my AppVMs are just for browsing the web and the 15
different times, I've reset up  firefox with perhaps a few downloads
. considering that would there be some reason to backup AppVMs .


Maybe the only VM that matters *is the 300GB AppVM with photos in it ,
that stays offline ?


re: /var/tmp  is  dom0  I am unable  to  cut and paste  from  dom0  what
I see is 
/dev/mapper/qubes_dom0-root  952848292  780151168(used) 
123272164(available) 87%   / 
and
various others smaller directories   ; I don't know what a "partial
restore" would look like ; I never touch dom0 :0

--
cc: the user group
--

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/04a90bcb398de37dce6a3d3ba4d83320%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-23 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-12-23 15:11, Andrew David Wong wrote:
> On 2017-12-22 21:30, yreb...@riseup.net wrote:
>> On 2017-12-22 09:50, awokd wrote:
>>> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via 
>>> qubes-users wrote:
 On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net 
 wrote:
 
> assuming 4.0 is going to come out of the box with like 
> Debian 9 and Fed 26?
>>> 
>>> If you have room for it, back up everything! You can restore 
>>> selectively later.
> 
>> thanks for the two replies, *However, neither gets to the gist
>> of my inquiry. Namely, which VMs am I supposed to be backing up,
> 
> You should back up every VM that contains data that you don't want 
> to lose and can't replace. For most people, this means backing up 
> every VM that contains things like documents, emails, photos, and 
> videos. If you're short on space, it's not necessary to make 
> backups of things that you know you'll be able to download easily 
> again later (e.g., an unmodified TemplateVM).
> 
>> Dom0 (which for some reason is over *500GB!)  , hence  I can't 
>> backup "everything" even with a 2GB internal HD that I'm trying 
>> to use
> 
> 
> For most users, the main reason to back up dom0 is because that's 
> where your dom0 user settings are stored. Normally, dom0 should
> not be that large, since you're only backing up the home
> directory. (You're using qvm-backup, right?) It sounds like you
> didn't expect it to be that large, so if there's not enough data in
> your home directory to account for it, check /var/tmp to see if you
> have a lot of partial restores taking up space.
> 

Just to clarify: Having a lot of data in /var/tmp shouldn't affect the
size of dom0 when you back it up using qvm-backup (since, again,
you're only backing up the home directory). But I mention it because I
don't know whether you're looking at the total size of dom0, and one
common reason for the total size of dom0 becoming unexpectedly large
is that /var/tmp fills up with partial restores.

>> I was thinking of skipping the 1 large offline AppVM where I
>> keep old photos, and did, so why did  the Templates and Dom0
>> come out to such a *Huge filesize,   what would be typical ???
> 
>>> From what your saying can I skip the Debian 8 Template, I have 
>>> 2 AppVMs
>> and the Whonix stuff based on it I guess
> 

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaPsnSAAoJENtN07w5UDAw2MEP/1SRKX9T6cUEcqOsX9ack9qT
tId1swRf52oDae+Wrst55VeUGTWL3CtMH1wQnqBjiJ7fF93CJ/UhJJ6zwAnnD2jM
PhINCdUV5iVZDJ6W1yBsrtU9izSfwxSb8PwiSW0Zg43iPrzB/pdGn9vhrs3Gts1o
jEfewgOuBAWPbcNKNegKMBKlTpXaGpsUki6v9K/kLq7Vk01pg5vwzYtL7Qqniz9m
CDI4/GxM8YQjbwDAV+xhQa3/oZ44AjK1osfPGGD1VFafiuyE9gRbl70FoFiZIcpH
RjoQSJbiacSnfDitf9FiEAe/A+Hiv3wZ7nejE6mv2hk3PbIgoRnLqXbEDBl/YcZl
E//WyeK3UXfdCgAqWV81GnE1mtlt72elLu1rBSPF+kr+1KNu+zwKcaAKhvh47SdA
B53+qYpuTvo/Rm66nink5QIDQIoR4RU3NZK//JTPzzF1NDvOqdc5u8c6n+W6OnzX
4WOIuBZetuuq9BrDnQpL3M1DEzOwWmWKA9PBrJXxHeGslwxRj5EfwOWIIFcp8+WO
usJwAbVf7nirwtSL+yHnu1d2jXL9ocVRlTrv94M4+PaFyVJ0sn1F8iZtDYmysXye
PGAhrj1Vk7XqWgWu1JvWZuxg+6UMaTXVWy/oipfjyD8vVi7i+ZjS0HVP9rknPumn
9kDeKM27/9l/eycZbu6i
=+fzT
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ea2919a0-3fa5-153e-7a23-7ffd009b80e7%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-23 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-12-22 21:30, yreb...@riseup.net wrote:
> On 2017-12-22 09:50, awokd wrote:
>> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via qubes-users
>>  wrote:
>>> On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net 
>>> wrote:
>>> 
 assuming 4.0 is going to come out of the box with like Debian
 9 and Fed 26?
>> 
>> If you have room for it, back up everything! You can restore 
>> selectively later.
> 
> thanks for the two replies, *However, neither gets to the gist of 
> my inquiry. Namely, which VMs am I supposed to be backing up,

You should back up every VM that contains data that you don't want to
lose and can't replace. For most people, this means backing up every
VM that contains things like documents, emails, photos, and videos. If
you're short on space, it's not necessary to make backups of things
that you know you'll be able to download easily again later (e.g., an
unmodified TemplateVM).

> Dom0 (which for some reason is over *500GB!)  , hence  I can't 
> backup "everything" even with a 2GB internal HD that I'm trying to
>  use
> 

For most users, the main reason to back up dom0 is because that's
where your dom0 user settings are stored. Normally, dom0 should not be
that large, since you're only backing up the home directory. (You're
using qvm-backup, right?) It sounds like you didn't expect it to be
that large, so if there's not enough data in your home directory to
account for it, check /var/tmp to see if you have a lot of partial
restores taking up space.

> I was thinking of skipping the 1 large offline AppVM where I keep 
> old photos, and did, so why did  the Templates and Dom0  come out 
> to such a *Huge filesize,   what would be typical ???
> 
>> From what your saying can I skip the Debian 8 Template, I have 2
>>  AppVMs
> and the Whonix stuff based on it I guess
> 

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaPsaXAAoJENtN07w5UDAwdL0P/iAUGEnnayXcy49YMdZOAjnG
dVjNhbEn20d1a9ye//Ic49PJLQ8aIhj54EctZI52NpwdPJFY0MRTgz4Mp1yMjHyO
n7fvABD/rkTLOvriJ4KUy1irU7aBN7WkHG3LWWAM5Y/EEDfHcSfoW9qfkc0qFNOj
YnZUcHUi1blGMCwlI/2XV6YQ2deznAiMc/p7AprTw0q8lpskmKgD3o4HJIYgKBj7
b2k/MZy//ZYBtNWVobxS4r6aqjvOkJ5sMRRHj7LyJk/A9w6SViAy6KDAPe2u2Nw5
i1PH27P9J6ulXm6apBxATLymCspmLF3co29lbjAnwi3NkJYCtmA8DqRBpSRwvFZC
yXrUffVP63LWLivW0svHDD9NXkzucL/DAGDXWN/X1yaasGibHT/tht2AC49o9prP
8224jqxW6qoRLYzpE2fvRA8ezW9EObSV3+ywaKuEX/78rUIi1na+9CcZXAW5iADx
Py+T2tWZ0qNm7c3VeHLA66TizUyqp8trFY0L2EjiW2Yhbx/B/IriPKgQfQsF3ukt
UBklqinl+6mKYtL0ilSOqdEop8AsXgfMy1r0da0mJWYsiXzRYiZpzCbkKgNYhAhQ
J/IEpWIq+UXsfYDc1mrRIMvfPlmid1UuiTHiMoJsIM4FdJ3Cy9GQp2J2WEBEHSt+
s2/cylsUDfe+3maOxeED
=lvvi
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fa768149-20c0-b0c2-5708-7a6d90f9f7b1%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-23 Thread Todd Lasman

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/21/2017 05:42 PM, yreb...@riseup.net wrote:
> hello, I went through the docs on creating a backup of the VMs, trouble > is 
> , I don't have the basic concept of which VMs to backup, e.g. Dom0
is > said to be 500Gb by itself, and the Deb 8 and Fed 25 are also
hundreds > of Gbs, as is my non-network VM where I keep all my old
photos , which > I did backup to somewhere, it's the only VM I've ever
backed up. > > But, lets say I skip the large "old docs" file ; and
wanted to migrate > my VMs to 4.0 , just which VMs would be translatable
to 4.0 assuming > 4.0 is going to come out of the box with like Debian 9
and Fed 26? > > Am I/do people just back up AppVMs and mostly just for
3.2 ? or what am > I missing . I am a basic user as you can guess :)
> My practice is to back up all my AppVM's and Dom0. The reason for the
appVM's is that each one has specific docs along with specific
customizations. I back up Dom0 because I store some scripts there. To my
knowledge, backing up Dom0 only backs up the home directory, so I'd
check the contents of your home directory in dom0 to see why you have
500Gb stuff stored there.

I don't back up templates, as they are easily downloaded, and I don't
back up trivial, easily creatable appVM's like my backupVM, which is
essentially an empty placeholder for mounting external media.

Hope this helps.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJaPpAvAAoJEOaMWwQFV9eFxrIQAJdhrgA5CfoMuVKisEQEfyuv
v6c08hX9eVWo3Uz0mdXfzzGxGe5ixfxbLz4ZtGOwfKioljKJhkK7QCaBT7PCYTFG
TrRdgp1lrxHcg0RTzdQLedRltMbYOlrStbGR+6YoZyhEkrIhGsG/hEEBCrdovavZ
Xca2D3k8UHxJUxkGZ4SLJMjmkxGAIV+lsJnlWhPh1F0XsF/oZIJIye8n6A65HbMA
1sLeOslURUfo+nmg/mh9cFuwIMS+w7Xoy6qVxjd2SxygnqPkNHZsoiLU36kio5kf
Ei9XfgYWlCNdIFBqnBWrSBeanepap3POCjv2uGcJ1AIY7KNu09SXxOdLSHOuVWvj
nNKH7NmBwz7PILYBNYlf8uzipmEKGxX8IzNw0QVN5miGRi5RMbKTnxWt/3XocHiH
Fw/NR5CEeCDmnsgM8AAyeTHlPh7k6W2QWSNnlA1Qx4hE12FZKJ6iJep3F+bFakE2
APBb7AAWU7+gYaeBCLsJ4g/vOxB/M32vHnM8kPDaa6WrC3g2cQpz1esJlvrXPOq0
c0KDxx66fp09K4ykuw3DvQH6yjDoPicYbnrvGI+8WzfdfvOgoeP2M3VajKM928/p
MDK+Au7BO51qyCSmpeO5VZldLC8IxStWVtVEmQ41VYoyjOrrtx5OL4l8ub3QQbTg
71toB1pFBdieIUci2wvN
=FIL2
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fc92f4b2-27dd-b41a-4c69-1451a4425fbc%40nowlas.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-22 Thread yrebstv
On 2017-12-22 09:50, awokd wrote:
> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via qubes-users wrote:
>> On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net wrote:
>>
>>> assuming 4.0 is going to come out of the box with like Debian 9 and Fed
>>> 26?
> 
> If you have room for it, back up everything! You can restore selectively
> later.

thanks for the two replies, *However, neither gets to the gist of my
inquiry. Namely, which VMs am I supposed to be backing up, Dom0 (which
for some reason is over *500GB!)  , hence  I can't backup "everything"
even with a 2GB internal HD that I'm trying to use 

I was thinking of skipping the 1 large offline AppVM where I keep old
photos, and did, so why did  the Templates and Dom0  come out to such a
*Huge filesize,   what would be typical ??? 

>From what your saying can I skip the Debian 8 Template, I have 2 AppVMs
and the Whonix stuff based on it I guess 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/31d315564e9db9c896af46fcbb4fa81e%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-22 Thread 'awokd' via qubes-users
On Fri, December 22, 2017 10:29 am, 'Tom Zander' via qubes-users wrote:
> On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net wrote:
>
>> assuming 4.0 is going to come out of the box with like Debian 9 and Fed
>> 26?

If you have room for it, back up everything! You can restore selectively
later.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c5c7299a732439f748c74d4474a0e450.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Which 3.2 VMs to backup and for eventual 4.0 migration?

2017-12-22 Thread 'Tom Zander' via qubes-users
On Friday, 22 December 2017 02:42:57 CET yreb...@riseup.net wrote:
>  assuming
> 4.0 is going to come out of the box with like Debian 9 and Fed 26?

Fedora 26 is not going to be used in 4.0, maybe in 4.1

source;
https://groups.google.com/forum/#!msg/qubes-devel/13PZgSOaajA/RvBh02ANCAAJ

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/36072167.FdIqrO2KI0%40strawberry.
For more options, visit https://groups.google.com/d/optout.