> 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, w
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 " option.
I know - but how does that solve the problem? If .zfs were
visible, wouldn'
"Mike L. Varney" <[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?
Ah, now I remember the problem I had, when I initially thought
about User Backups: How do I make a User Backup be a Incremental
Backup (
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
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" w
> > 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 correc
-- 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 h
Johnson, Eric schrieb:
> You can control whether the .zfs directory for snapshots is visible or
> not woth the "zfs set snapdir=visible " 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 t
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. Wh
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
ect
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 b
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 ju
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 PR
13 matches
Mail list logo