ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
I've read near everything that I can find on this until I'm blue in the face, including searching through this site, and the help pages in dsmc on the client. This is for Linux. I'm still a little fuzzy on what initiates a partial incremental backup and how it's different from a full incremental backup. In this case, I'm excluding an incremental by date from the discussion since that makes more sense to me.
Can someone kindly explain to me then what exactly happens (or doesn't happen; maybe that's more important) during a partial incremental backup? Other than the fact that you're not hitting all the data in the file system, what does it not do that a full incremental does?
[ This is what I've gathered ]
When I run dsmc on the client (interactively or passing arguments to it from the command line), and I specify 'incr', or if a scheduled backup is running, and the Action parameter is set to incremental, then a full incremental will be performed as long as the specified path is a file system, e.g. /home, and not a subdirectory, e.g. /home/username. If I specify no file system, but I have statements in the stanza like 'domain filesystem1', domain 'filesystem2', etc. then likewise a full incremental will be performed.
Is this correct?
[ This is where I'm confused ]
A partial incremental might not expire files? So if the file is deleted from disk then it won't be marked as inactive? Or it will, but values defined in the copygroup, like verdeleted, verexists, etc. might not be updated? Both? Also it won't rebind files if a management class changes? That right?
As near as I can tell, I'm not doing any partial incrementals. All backups are full incrementals. But if I elected to run a partial incremental then what is the down side? What do I need to be aware of? What is the gotcha there?
Thanks.
Can someone kindly explain to me then what exactly happens (or doesn't happen; maybe that's more important) during a partial incremental backup? Other than the fact that you're not hitting all the data in the file system, what does it not do that a full incremental does?
[ This is what I've gathered ]
When I run dsmc on the client (interactively or passing arguments to it from the command line), and I specify 'incr', or if a scheduled backup is running, and the Action parameter is set to incremental, then a full incremental will be performed as long as the specified path is a file system, e.g. /home, and not a subdirectory, e.g. /home/username. If I specify no file system, but I have statements in the stanza like 'domain filesystem1', domain 'filesystem2', etc. then likewise a full incremental will be performed.
Is this correct?
[ This is where I'm confused ]
A partial incremental might not expire files? So if the file is deleted from disk then it won't be marked as inactive? Or it will, but values defined in the copygroup, like verdeleted, verexists, etc. might not be updated? Both? Also it won't rebind files if a management class changes? That right?
As near as I can tell, I'm not doing any partial incrementals. All backups are full incrementals. But if I elected to run a partial incremental then what is the down side? What do I need to be aware of? What is the gotcha there?
Thanks.