This is more for curiosity's sake than urgent
Is there a technique for temporarily ignoring data, which has been backed up in the past, from normal daily incremental backups? Something straightforward, not altering file management class or such tricks.
The following example is a lame one, but I can't think of a better one at the moment. I know I've wondered how to do it for other reasons, and was able to use manual dsmc incremental filespec commands to backup only the data I wanted to process at the moment. But it would be nice to be able to have scheduled backups occur, or not have to construct convoluted filespecs.
Assume a Linux client, an inability to rename or reorganize the files because they belong to someone else. Client has a file space /export/d3, in which a subdirectory "bob" exists, alongside, say, a few hundred other subdirectories. Incremental backups have already been run on /export/d3 and some, if not all of "bob" has been backed up. You don't want to nuke your extant copies of "bob" objects, just ignore them for a while. Say while the owner of "bob" rearranges them, because there are millions of files, and he might make mistakes, but you don't want to capture the same files over and over again in different locations while he takes a month to do the organizing.
If one added to dsm.sys a domain statement (where there had been none at all before) like
domain ALL-LOCAL -/export/d3/bob
then I believe it would not be backed up. But would it and it's contents be marked inactive? They definitely would if you added an
exclude.dir /export/d3/bob
What if the thing you wanted to ignore was a file space? (If modifying the domain worked for a directory, it seems as if it would work for a file space.)
thanks.
Is there a technique for temporarily ignoring data, which has been backed up in the past, from normal daily incremental backups? Something straightforward, not altering file management class or such tricks.
The following example is a lame one, but I can't think of a better one at the moment. I know I've wondered how to do it for other reasons, and was able to use manual dsmc incremental filespec commands to backup only the data I wanted to process at the moment. But it would be nice to be able to have scheduled backups occur, or not have to construct convoluted filespecs.
Assume a Linux client, an inability to rename or reorganize the files because they belong to someone else. Client has a file space /export/d3, in which a subdirectory "bob" exists, alongside, say, a few hundred other subdirectories. Incremental backups have already been run on /export/d3 and some, if not all of "bob" has been backed up. You don't want to nuke your extant copies of "bob" objects, just ignore them for a while. Say while the owner of "bob" rearranges them, because there are millions of files, and he might make mistakes, but you don't want to capture the same files over and over again in different locations while he takes a month to do the organizing.
If one added to dsm.sys a domain statement (where there had been none at all before) like
domain ALL-LOCAL -/export/d3/bob
then I believe it would not be backed up. But would it and it's contents be marked inactive? They definitely would if you added an
exclude.dir /export/d3/bob
What if the thing you wanted to ignore was a file space? (If modifying the domain worked for a directory, it seems as if it would work for a file space.)
thanks.