ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
Hello,
This is on linux. I have a situation where I want to back up a bind mount, e.g. /x/projects/data and not the actual file system name, e.g. /projects/old/data. Both are listed in /etc/fstab. The actual file system has two directories: /projects/old/data/export, lost+found. The bind mount uses /projects/old/data/export, so lost+found is not accessible from it. I cannot change the actual file system name, though. For testing, up until now, I've been using a domain statement in the stanza as:
domain /projects/old/data
1. Given that the bind mount is listed as a file system in /etc/fstab then should I be able to change the domain statement to ???:
domain /x/projects/data
and simply have it run another full incremental backup wherein it will run a first time full, and then only changes after that? Will it function the same way? Or will it somehow do something goofy and insist on running a partial incremental backup?
2. I will need to back up the lost+found directory separately. I cannot add another bind mount entry for that at this time, however.
Can I simply add a statement in the stanza for that as:
/projects/old/data/lost+found
How would I do that?
We've been using domain statements to force TSM to only back up what is specifically enumerated in the stanza. This way, if someone creates a new file system, it won't just get backed up unless we add it. Also, while we're working our way through the first-time fulls, we don't have to have exclude statements to instruct TSM to exclude everything other than what we've added thus far. This makes the domain statement very handy, but I was under the impression that it could only be used for a file system, and /projects/old/data/lost+found is not a file system, only /projects/old/data.
Maybe I'd need something onerous like ???:
domain /x/projects/data
domain /projects/old/data
exclude.dir /projects/old/data/export
So the first one would hit everything under /x/projects/data, which is really everything under export, and the second one would grab everything other than export, due to the exclude, so this would include lost+found, but if anyone added anything else under there at some point later down the road then it would grab that, too?
This is on linux. I have a situation where I want to back up a bind mount, e.g. /x/projects/data and not the actual file system name, e.g. /projects/old/data. Both are listed in /etc/fstab. The actual file system has two directories: /projects/old/data/export, lost+found. The bind mount uses /projects/old/data/export, so lost+found is not accessible from it. I cannot change the actual file system name, though. For testing, up until now, I've been using a domain statement in the stanza as:
domain /projects/old/data
1. Given that the bind mount is listed as a file system in /etc/fstab then should I be able to change the domain statement to ???:
domain /x/projects/data
and simply have it run another full incremental backup wherein it will run a first time full, and then only changes after that? Will it function the same way? Or will it somehow do something goofy and insist on running a partial incremental backup?
2. I will need to back up the lost+found directory separately. I cannot add another bind mount entry for that at this time, however.
Can I simply add a statement in the stanza for that as:
/projects/old/data/lost+found
How would I do that?
We've been using domain statements to force TSM to only back up what is specifically enumerated in the stanza. This way, if someone creates a new file system, it won't just get backed up unless we add it. Also, while we're working our way through the first-time fulls, we don't have to have exclude statements to instruct TSM to exclude everything other than what we've added thus far. This makes the domain statement very handy, but I was under the impression that it could only be used for a file system, and /projects/old/data/lost+found is not a file system, only /projects/old/data.
Maybe I'd need something onerous like ???:
domain /x/projects/data
domain /projects/old/data
exclude.dir /projects/old/data/export
So the first one would hit everything under /x/projects/data, which is really everything under export, and the second one would grab everything other than export, due to the exclude, so this would include lost+found, but if anyone added anything else under there at some point later down the road then it would grab that, too?
