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 sys 5 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