Re: Dir, Filespace backup question
Using Aristotle's experimental model (pure mental what-if), I've concluded it might be possible to export the /app filesystem to tape, rename the filesystem to /app/users/fred, import the filesystem from tape to get your /app filesystem back. My mental gyrations lead me to believe you would then have all your {/app}/users/fred backup/archive data in the {/app/users/fred} backup. I wonder what would happen for expiration of /app/users/david/* files in the {/app/users/fred} filespace? Hmm Maybe you could season with a bit of rebinding? I think this would be a fun experiment if I can find the time. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 4:18 AM To: [EMAIL PROTECTED] Subject: Re: Dir, Filespace backup question One thing you have to watch out for is that... when you do that you alter the keys which TSM uses... Key fields in various situations are NODE, FILE_SYSTEM (filespace_name), directory path ie stuff between the mount point & where the file resides (hl_name), FILE (ll_name) Now you used to have /app/1st72gbarray/somedir/somefile keys used to be app 1st72gbarray/somedir somefile now if you do what it seems you will do your keys will change as follows... app/1st72gbarray somedir somefile So in the future you might have to do the following... If looking for older copies of backups & archives use q backup {/app}/1st72gbarray/somedir/somefile If looking for newer copies of backups & archives use q backup {/app/1st72gbarray}/somedir/somefile Use the {} to designate what should constitute the ~file_system~ name Oh, and I guess since it radically changes the keys, it goes without saying that it will assume the new names are all new files... There is the ability to rename your filesystems within TSM but I've never specifically looked at the results of that action as it relates to the issues mentioned above... hope this helps, later, Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Farren Minns [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 4:08 AM To: [EMAIL PROTECTED] Subject: Dir, Filespace backup question Hi TSMers I have a question for you. I'm running TSM 4.2.2.12 on a Solaris 2.7 machine. We are about to do some reconfiguration of the file systems of one of our clients as follows. At the moment we have one massive /app dir with loads of subdirs for various applications (5 72GB disks software raided...yuk). What we are looking at doing is making some of the dir's actual mount points. i.e. the /app/users/fred would be copied to a new mount point making sure that all file permissions, access dates etc remain unchanged, and then mount that new file system as /app/users/fred (same as before). Will TSM see this as completely new data, regardless of whether or not we maintain the same dates, time stamp etc. If, so, is there a way round this? Please feel free to ask for more info If I have been too vague. Many thanks Farren Minns - John Wiley & Son Ltd
Re: Dir, Filespace backup question
One thing you have to watch out for is that... when you do that you alter the keys which TSM uses... Key fields in various situations are NODE, FILE_SYSTEM (filespace_name), directory path ie stuff between the mount point & where the file resides (hl_name), FILE (ll_name) Now you used to have /app/1st72gbarray/somedir/somefile keys used to be app 1st72gbarray/somedir somefile now if you do what it seems you will do your keys will change as follows... app/1st72gbarray somedir somefile So in the future you might have to do the following... If looking for older copies of backups & archives use q backup {/app}/1st72gbarray/somedir/somefile If looking for newer copies of backups & archives use q backup {/app/1st72gbarray}/somedir/somefile Use the {} to designate what should constitute the ~file_system~ name Oh, and I guess since it radically changes the keys, it goes without saying that it will assume the new names are all new files... There is the ability to rename your filesystems within TSM but I've never specifically looked at the results of that action as it relates to the issues mentioned above... hope this helps, later, Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Farren Minns [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 4:08 AM To: [EMAIL PROTECTED] Subject: Dir, Filespace backup question Hi TSMers I have a question for you. I'm running TSM 4.2.2.12 on a Solaris 2.7 machine. We are about to do some reconfiguration of the file systems of one of our clients as follows. At the moment we have one massive /app dir with loads of subdirs for various applications (5 72GB disks software raided...yuk). What we are looking at doing is making some of the dir's actual mount points. i.e. the /app/users/fred would be copied to a new mount point making sure that all file permissions, access dates etc remain unchanged, and then mount that new file system as /app/users/fred (same as before). Will TSM see this as completely new data, regardless of whether or not we maintain the same dates, time stamp etc. If, so, is there a way round this? Please feel free to ask for more info If I have been too vague. Many thanks Farren Minns - John Wiley & Son Ltd
Dir, Filespace backup question
Hi TSMers I have a question for you. I'm running TSM 4.2.2.12 on a Solaris 2.7 machine. We are about to do some reconfiguration of the file systems of one of our clients as follows. At the moment we have one massive /app dir with loads of subdirs for various applications (5 72GB disks software raided...yuk). What we are looking at doing is making some of the dir's actual mount points. i.e. the /app/users/fred would be copied to a new mount point making sure that all file permissions, access dates etc remain unchanged, and then mount that new file system as /app/users/fred (same as before). Will TSM see this as completely new data, regardless of whether or not we maintain the same dates, time stamp etc. If, so, is there a way round this? Please feel free to ask for more info If I have been too vague. Many thanks Farren Minns - John Wiley & Son Ltd