Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Archiving client files with longer retention period than backup policy

Created: 29 Apr 2013 • Updated: 29 Apr 2013 | 4 comments
This issue has been solved. See solution.

I'd like to archive some files off our Centos 5.6 system, using the NetBackup 7.5 client.  Our server is running also 7.5 under Solaris.

I believe I understand how archives differ from backups, and that I have to initiate it from the client interface.  Two questions though:

The only backup policy for this client has a 6 month retention, and the policy selection is a lot broader than just the files of interest.  I figure as long as the policy selection is wider than the files, I'm ok.  But how to specify a longer retention?  Do I have to create a new policy (call it "Archive"?) and select that at the time of backup somehow?  I see no seperate option to "archive" in the client interface.

Also I see mention in previous posts that the policy selected must have a user archive schedule that permits this.  Looking at the existing policy, I don't see where this is specified.

Thanks for any advice....Lyle

Operating Systems:

Comments 4 CommentsJump to latest comment

mph999's picture

User archive is set in the schedule and is found in the 'type of backup' dropdown. 

x2 cllick a schedule and you should see it.

You don't need a new policy, you need a new schedule - this should then work.  You can adjust the retention time as you need within this new schedule.

You select the files to backup in the BAR gui on the client, then when you click the 'backup' button (I was using the Java GUI) you should see a tick box to select to archive, as opposed to just backup.

Hope this makes sense.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
Lylex's picture

Oops, spoke too soon....

I've created a new schedule under the existing policy, and set the "Type of Backup" to "User Archive".  Gave that schedule the retention time and volume pool I wanted.

When I start a backup from the BAR client, I select my files and select the "Archive files" checkbox.

Great!   But the job fails without much explanation.  I notice in the details in the Activity Log, the Job Policy and Job Schedule are both *NULL*.

What associates my starting an archive on the client with the schedule (and retention) I made on the server?

Thanks....Lyle

mph999's picture

I'll x2 check my advice, I am very sure it is correct so I think you have a separate issue, or a slight mis-config

"What associates my starting an archive on the client with the schedule (and retention) I made on the server?" 

The exsistance of a userbackup or userarchieve on a policy that has the client listed.

I've just tried this without a user backup/ archive schedule, it fails with status 135 and the job policy and jobschdule show as null.

I added it all back, ran a backup by selecting files in the BAR gui, worked fine.

Oh, you did give the schedule a backup window didn't you ?  A backup window must be open, this defines the times you are allowed to run a user job.

One other thing, when you do a restore, you have to select the policy type as 'Archive'.

Perhaps post up the policy details here if you still have no luck.

bppllist <policyname> -U

Here is mine, as an example

root@womble  $ bppllist womble_sp1 -U
------------------------------------------------------------
 
Policy Name:       womble_sp1
 
  Policy Type:         Standard
  Active:              yes
  Effective date:      04/15/2013 20:04:54
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    no
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           ad_sp1
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)
 
  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Solaris       Solaris10     womble
 
  Include:  /netbackup/testdata
 
  Schedule:              archive
    Type:                User Archive
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     01:00:00  -->  Sunday     24:00:00
          Monday     01:00:00  -->  Monday     24:00:00
          Tuesday    01:00:00  -->  Tuesday    24:00:00
          Wednesday  01:00:00  -->  Wednesday  24:00:00
          Thursday   01:00:00  -->  Thursday   24:00:00
          Friday     01:00:00  -->  Friday     24:00:00
          Saturday   01:00:00  -->  Saturday   24:00:00
 
  Schedule:              Full
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     0 (1 week)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
 
Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805