Nothing will happen, because those files are always excluded. So now if you try to backup with the command To exclude an entire disk you need two commands, one to exclude the drive and one to exclude the files in the root folder, like this If you absolutely never want to let anyone backup the c: drive in any circumstances, then use EXCLUDE statements as these will always apply. This approach will also allow you to backup selected files or directories from an excluded diskÄsmc selective c:\tivoli\tsm\* -subdir=yes This is not necessarily a bad thing, it means that you can exclude the c: from scheduled backups, but when you really want a backup, you can do it manually. Will backup the entire c: drive, even though it is excluded in the domain statement. If you manually select a volume that is excluded in the dsm.opt file, then it will be backed up. However, the DOMAIN ALL-LOCAL approach will only work if you are backing up at domain level with a scheduled backup. Specific selection criteria for the Windows System Object is given below. This means that all drives are backed up except the c: drive, and you do not need to change the dsm.opt file as drives are added or removed. A good variant, if you never wanted to backup your c: drive for example is The problem with these approaches is that you need to remember to update the dsm.opt file if you add new drives You can select and exclude drives from scheduled backups by placing an entry in the DSM.OPT file on the client, with a line which looks like this for a Windows client
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |