Re: [Veritas-bu] Backing up ZFS snapshots
Simple, make an exclude_list containing: /pool/Teamcenter/ Then specify in your backup list: /pool/Teamcenter/.zfs/snapshot/backup Eric -Original Message- From: Alexander Skwar [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 3:53 PM Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Backing up ZFS snapshots Johnson, Eric schrieb: You can control whether the .zfs directory for snapshots is visible or not woth the zfs set snapdir=visible filesyste option. I know - but how does that solve the problem? If .zfs were visible, wouldn't this make even more problems? Suppose I'd backup /pool, this would cause the original /pool/Teamcenter and also the snapshot underneath /pool/Teamcenter/.zfs/snapshot/backup to be stored on tape. That's absolutely not what I want - I do not want to store the (more or less) same content twice - I don't work at Imation, or any other tape vendor, you know ;) Alexander Skwar -- If I want your opinion, I'll ask you to fill out the necessary form. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Nah, that's exactly the route, that I do NOT want to go. To quote my OP: | I don't really | want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup | to the Backup Selections of a policy, as this would mean, that | the Backup Selections would have to be updated, when a new | zfs is created. I don't like this. Or did I misunderstand you? Nope. I had read that as meaning you didn't want to keep changing the selection in the policy for updated snapshots (like backup.yymmdd), not that changing it as filesystems came and went was the issue. If you're just worried about the hands-on work, it could be scripted. There's a few situations I've had where a static configuration just wouldn't work (usually involving netapps and snapshots made by another application that didn't want to be controlled). So I ran a script daily that modifed the NBU configuration. Here, it could poll for zfs filesystems and make sure they (or a valid snapshot) are in the bakcup selections list. That still leaves the extra communication necessary to support the script though. I'm just not sure what else you can do without more explicit support for ZFS within the client. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Have you tried a symlink into the snapshot dir? Karl [EMAIL PROTECTED] wrote on 03/08/2007 10:27:42 AM: Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/. zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. How do you do that? Alexander Skwar ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
You can control whether the .zfs directory for snapshots is visible or not woth the zfs set snapdir=visible filesyste option. From the zfs manpage: snapdir=hidden | visible Controls whether the .zfs directory is hidden or visi- ble in the root of the file system as discussed in the Snapshots section. The default value is hidden. Eric -Original Message- From: Alexander Skwar [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:28 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Backing up ZFS snapshots Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/.zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. How do you do that? Alexander Skwar ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Mike L. Varney schrieb: NetBackup would happily backup the symlink as if it were an individual file. It would not follow the link. Exactly. What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Alexander Skwar -- If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee. -- Larry Wall in [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Johnson, Eric schrieb: You can control whether the .zfs directory for snapshots is visible or not woth the zfs set snapdir=visible filesyste option. I know - but how does that solve the problem? If .zfs were visible, wouldn't this make even more problems? Suppose I'd backup /pool, this would cause the original /pool/Teamcenter and also the snapshot underneath /pool/Teamcenter/.zfs/snapshot/backup to be stored on tape. That's absolutely not what I want - I do not want to store the (more or less) same content twice - I don't work at Imation, or any other tape vendor, you know ;) Alexander Skwar -- If I want your opinion, I'll ask you to fill out the necessary form. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
I would think you could specify the hidden directory on the command line to back up the snapshot directory. It wouldnt be the matter of the backup client not getting access to the directory; the hidden directory just doesn't show up when the client is iterating thru the filesystem. -- M Alexander Skwar [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/08/2007 04:54 PM Please respond to veritas-bu@mailman.eng.auburn.edu To cc veritas-bu@mailman.eng.auburn.edu Subject Re: [Veritas-bu] Backing up ZFS snapshots Mike L. Varney schrieb: NetBackup would happily backup the symlink as if it were an individual file. It would not follow the link. Exactly. What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Alexander Skwar -- If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee. -- Larry Wall in [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Since the client knows the snapshot involved, it could give the correct name to the process (/fs/.zfs/snapshot/name). Also, you can rename snapshots. A script could make sure that the most recent snaphot is always called 'current' or something. You place that name on the backup list of the profile. Then when it's time to rotate, the script could rename 'current' to a timestamp and create a new 'current'. Or maybe rotate like netapp 'daily.0' - 'daily.1' etc... -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
On 3/8/2007 10:27 AM, Alexander Skwar wrote: Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/.zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. I haven't used zfs, but what happens if the policy specifies /pool/*/.zfs ? Enable cross mount-points and does the right thing happen? Try a bpdir from the master using that directory spec and see if your files are listed. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Darren Dunham [EMAIL PROTECTED]: What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Since the client knows the snapshot involved, it could give the correct name to the process (/fs/.zfs/snapshot/name). Okay. But what would I have to add to the Backup Selections properties of the Policy? Also, you can rename snapshots. A script could make sure that the most recent snaphot is always called 'current' or something. The snapshot currently is called backup. So, that's already a static name. You place that name on the backup list of the profile. Nah, that's exactly the route, that I do NOT want to go. To quote my OP: | I don't really | want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup | to the Backup Selections of a policy, as this would mean, that | the Backup Selections would have to be updated, when a new | zfs is created. I don't like this. Or did I misunderstand you? Thanks, Alexander Skwar ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
