bpend_notify for disk staging

[Sean_-]

Did anybody been tried to use bpend_notify script for disk staging schedule or policy ?

Thank you !!!

Regards
Sean

[Yasuhisa_Ishika]

If I remeber right, bpend_notify is invoked from bpbkar process.
So I guess as follows:

* can use with backup which uses Disk-Staging Storage Unit(DSSU).
bpbkar works on clinet host.

* cannot use in duplicating procedure in which NB make copy of images from DSSU to Final Destination Storage Unit(FDSU).
bpbkar doesn't works in duplication.

My testing environment is now under reconstruction, so I cannot check it today. Sorry.

[TempoVisitor]

If you want to launch the Stage 2, means the duplication at the thend of the backup job, this must be done from the master server, not from the client.

bpend_notify is launched on the client. Therefore you cannot use it here.

backup_exit_notify is launched on the master server at the end of a job. You should put the command bpbackup -DSSU DiskStagingSTUName.

Kerkael

[Sean_-]

thank you ... I have tried the backup_exit_notify script which run at master server, it works fine for DSSU ! thank you.

could i use bpend_notify script at client ? however my policy name will be __DSSU_POLICY_"your_dssu_name" ?
I couldn't add __DSSU_POLICY_"my_dssu_name" at the back of bpend_notify script.

I have tried the bpend_notify script as follow: bpend_notify.__DSSU_POLICY_"my_dssu_name"

but still failed.

I tried to backup my data at my master server. and actually want to use the bpend_notify script to change the retention period of copy 2 and copy 3 of my stage 2 data which has been transfer to tape. I don't want the retention period of DSSU (1st copy) to be the same as my FDSU (2nd and 3rd copies).

this because the 1st copy will easily used up the space ... and I need to use a short retention period to clean up the space.

I am using solaris 9, netbackup enterprise 5.1.

thanks.

[TempoVisitor]

The bpend_notify launched from the client can only use commands from the client.
This means you can only ask it to launch a
bpbackup -p USERPOLICY - s USERBACKUP/ARCHIVE -f FILELIST

bpbackup can not be used from the client to start nor a FULL nor an INCR schedule backup.

It can neither start a STAGE 2 for a DSSU.

If you really want a client machine to have the right to start a FULL or INCR or DSSU, then you need to tell NBU this machine is a console.

This is done by adding the name of this machine in your /usr/openv/netbackup/bp.conf file, as a second entry SERVER = CLIENT_MACHINE
Don't add it in first position ... this must be the name of the master !

Beware, however, because this machine has now full right to administrate your whole master server and NBU configuration. This means any root user on the client machine would be a full NBU Administrator !!!!! This should only be done if you know this client machine does belong to you, as an administrator.

Then, from the command bpbackup, you must specify the name of your server :
bpbackup -S MASTERSERVER -DSSU DiskStagingSTU

For a different retention period for your copies 2 and 3, this is done through the DSSU Schedule you modify from the GUI in the Storage Unit entries. There, if you multiple copies your Stage 2, you can specify a different retention period for each of your copies.

If you want to modify the retention period of an existing image, you can only do this from command line :
bpexpdate -m MEDIAID (or) -backupid IMAGENAME -d mm/dd/yyyy HH:MM:SS -force

-force is not to be asked for confirmation

Kerkael

[Sean_-]

> The bpend_notify launched from the client can
> only use commands from the client.
> This means you can only ask it to launch a
> bpbackup -p USERPOLICY - s
> USERBACKUP/ARCHIVE -f FILELIST
>
> bpbackup can not be used from the client to
> start nor a FULL nor an INCR schedule
> backup.
>
> It can neither start a STAGE 2 for a DSSU.
>
> If you really want a client machine to have the right
> to start a FULL or INCR or DSSU,
> then you need to tell NBU this machine is a
> console.
>
> This is done by adding the name of this machine in
> your /usr/openv/netbackup/bp.conf file, as a
> second entry SERVER = CLIENT_MACHINE
> Don't add it in first position ... this must be the
> name of the master !
>
> Beware, however, because this machine has now full
> right to administrate your whole master server and
> NBU configuration. This means any root user on the
> client machine would be a full NBU Administrator
> !!!!! This should only be done if you know this
> client machine does belong to you, as an
> administrator.
>
> Then, from the command bpbackup, you must
> specify the name of your server :
> bpbackup -S MASTERSERVER -DSSU
> DiskStagingSTU
>
> For a different retention period for your copies 2
> and 3, this is done through the DSSU Schedule you
> modify from the GUI in the Storage Unit entries.
> There, if you multiple copies your Stage 2,
> you can specify a different retention period for each
> of your copies.
>
> If you want to modify the retention period of an
> existing image, you can only do this from command
> line :
> bpexpdate -m MEDIAID (or) -backupid
> IMAGENAME -d mm/dd/yyyy HH:MM:SS
> -force
>
> -force is not to be asked for confirmation
>
> Kerkael

hi kerkael,

Thank you for your reply ...

I am now using the retention period to expire the copies 2 and copies 3, instead of using disk staging method to delete the backup images.

Will try to use script to change the retention period. I am not able to change the retention period while at final stage of disk staging (FDSU).

Thank you Kerkael .
Sean