05-21-2018 02:09 AM
I have created a BasicDisk (no license to do anything else). Policy created to backup to the basic disk with infinite retention period. From the basic disk I have staging schedule to copy the backups on the disk to tape. This works, however the retention level is set to 2 weeks. I know the default retention level for a basic disk is set to Level 1 which is 2 weeks, but I can not see where I can change the rentenion level for the basicdisk. I know I can set the retention level on the Master but other policies are using level 1 so can not do that.
~Unless there is another way to backup to disk then to tape with infinite retention level without buying additional licenses
Solved! Go to Solution.
05-21-2018 07:25 AM
Both backup copies (disk and tape) have INFINITY retention.
The reference to '2 weeks' in the staging job is a 'red herring'. You can ignore it.
The retention in the disk staging config is linked to the DSSU Frequency.
See this: https://www.veritas.com/support/en_US/doc/123711489-126541862-0/v41615072-126541862
Internally, NetBackup uses the retention level 1 setting for scheduling purposes with disk staging storage units.....
...
Make sure that the frequency period is set to make the backups occur more frequently than the retention level 1 setting indicates. (The default is two weeks.)
05-21-2018 06:20 AM
I am confused... where do you see that retention on disk is set to 2 weeks?
Where do you see this information?
I know the default retention level for a basic disk is set to Level 1 which is 2 weeks,
There is no such thing as default retention on basic disk. The policy schedule determines the retention period for disk and tape.
This means that the copy on disk and the copy on tape will have the same retention.
The only thing that will change image retention on disk is the High Water Mark for the storage unit.
When the HWM is reached, NBU will cleanup images that have been duplicated to tape until LWM is reached.
Herewith 2 TNs (still valid for current NBU versions):
DOCUMENTATION: Description of NetBackup Disk Staging Relocation Behavior
http://www.veritas.com/docs/000030287
Disk Staging Storage Unit (DSSU) cleanup behavior
http://www.veritas.com/docs/000036495
05-21-2018 06:29 AM
There;s no setting to change the 2 week retention. I only see that it has a 2 week retention when the copy/backup starts and it shows as 2 weeks. I have read that the defautl for basic disk is 2 weeks (level 1). My policies to disk are set to inifinte retention and that's not being copied over to the disk job
05-21-2018 06:34 AM
Please show us the policy config:
bppllist <policy-name> -U
And image info for a completed backup :
bpimagelist -backupid <backup_id> -L
05-21-2018 06:52 AM
bppllist <policy-name> -U - OUTPUT below
Policy Name: windows-fast-disk
Policy Type: MS-Windows
Active: yes
Effective date: 18/10/2006 14:42:22
Backup network drvs: no
Collect TIR info: no
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: yes
Interval: 15
Policy Priority: 50
Max Jobs/Policy: 6
Disaster Recovery: 0
Collect BMR info: no
Residence: celont62-DiskPool1-Large
Volume Pool: GMS_Data-Fast
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
Use Accelerator: no
Optimized Backup: no
HW/OS/Client: Windows-x64 Windows2008 celont85.internal.scee.net
Windows-x86 Windows2008 impulse.internal.scee.net
Windows-x64 Windows2008 celont79.internal.scee.net
Windows-x64 Windows2008 celont101.internal.scee.net
Include: ALL_LOCAL_DRIVES
Schedule: Full
Type: Full Backup
Frequency: every 4 days
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Maximum MPX: 4
Retention Level: 9 (infinity)
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
Daily Windows:
Sunday 00:00:00 --> Sunday 24:00:00
Monday 00:00:00 --> Monday 05:10:00
Friday 18:00:00 --> Sunday 00:00:00
Schedule: Differential
Type: Differential Incremental Backup
Frequency: every 12 hours
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 4
Retention Level: 9 (infinity)
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
Daily Windows:
Monday 18:00:00 --> Tuesday 05:00:00
Tuesday 18:00:00 --> Wednesday 05:00:00
Wednesday 18:00:00 --> Thursday 05:00:00
Thursday 18:00:00 --> Friday 05:00:00
Schedule: Daily-User
Type: User Backup
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 4
Retention Level: 5 (3 months)
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
Daily Windows:
Monday 04:00:00 --> Friday 16:00:00
05-21-2018 06:53 AM
image of the disk to tape job - shows 2 week retention
05-21-2018 06:55 AM
where do i get the backup id below?
bpimagelist -backupid <backup_id> -L
05-21-2018 07:08 AM
There are various ways to obtain image id's.
You can run bpimagelist -idonly and add parameters to narrow down the output, or list backup images for a particular client for a date/period.
bpimagelist command usage: https://www.veritas.com/support/en_US/doc/123533878-127136857-0/v123538598-127136857
From the policy output, we can look for image output for a client in this policy for a Full backup that (hopefully) ran yesterday:
bpimagelist -L -policy windows-fast-disk -sl Full -client celont85.internal.scee.net -d 05/20/2018
(adjust parameters to ensure images are found for successful backup and duplication)
05-21-2018 07:16 AM
Output of D:\Program Files\Veritas\NetBackup\bin\admincmd>bpimagelist -backupid celont85.i
nternal.scee.net_1526681174 -L > test.txt
below
Client: celont85.internal.scee.net
Backup ID: celont85.internal.scee.net_1526681174
Policy: Windows-Fast-Disk
Policy Type: MS-Windows (13)
Proxy Client: (none specified)
Creator: root
Name1: (none specified)
Sched Label: Full
Schedule Type: FULL (0)
Retention Level: infinity (9)
Backup Time: 18/05/2018 23:06:14 (1526681174)
Elapsed Time: 3639 second(s)
Expiration Time: INFINITY (2147483647)
Maximum Expiration Time: INFINITY (2147483647)
Compressed: no
Client Encrypted: no
Kilobytes: 28652769
Number of Files: 86672
Number of Copies: 2
Number of Fragments: 6
Histogram: 0 0 0 0 0 0 0 0 0 0
DB Compressed: no
Files File Name: Windows-Fast-Disk_1526681174_FULL.f
Previous Backup Files File Name: (none specified)
Parent Backup Image File Name: (none specified)
SW Version: (none specified)
Options: 0x0
MPX: 1
TIR Info: 0
TIR Expiration: 01/01/1970 00:00:00 (0)
Keyword: (none specified)
Ext Security Info: no
File Restore Raw: no
Image Dump Level: 0
File System Only: no
Object Descriptor: (none specified)
Previous BI Time: 01/01/1970 00:00:00 (0)
BI Full Time: 01/01/1970 00:00:00 (0)
Request Pid: 0
Backup Status: 0
Stream Number: 2
Backup Copy: Standard (0)
Files File size: 10836536
PFI type: 0
IMAGE_ATTRIBUTE: 0
Primary Copy: 1
Image Type: 0 (Regular)
Job ID: 804253
Num Resumes: 1
Resume Expiration: 01/01/1970 00:00:00 (0)
Data Classification: (none specified)
Data_Classification_ID: (none specified)
Storage Lifecycle Policy: (none specified)
Storage Lifecycle Policy Version: 0
STL_Completed: 0
Remote Expiration Time: 01/01/1970 00:00:00 (0)
Origin Master Server: (none specified)
Origin Master GUID: (none specified)
Snap Time: 18/05/2018 21:17:54 (1526674674)
IR Enabled: no
Client Character Set: 1
Image On Hold: 0
Kilobytes Data Transferred: 0
Copy number: 1
Fragment: 1
Kilobytes: 9812224
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: G:\Netbackup-DiskStageG\\celont85.internal.scee.net_1526681174_C1_F1
Host: celont62.internal.scee.net
Block Size: 262144
Offset: 0
Media Date: 01/01/1970 00:00:00 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: celont62.internal.scee.net
Expiration Time: INFINITY (2147483647)
MPX: 0
retention_lvl: infinity (9)
Try to Keep Time: 01/01/1970 00:00:00 (0)
Copy Creation Time: 19/05/2018 00:06:53 (1526684813)
Data Format: Tar
checkpoint: 1
resume num: 0
Key tag: *NULL*
STL tag: *NULL*
Copy on hold: 0
Copy number: 1
Fragment: 2
Kilobytes: 8036864
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: G:\Netbackup-DiskStageG\\celont85.internal.scee.net_1526681174_C1_F2
Host: celont62.internal.scee.net
Block Size: 262144
Offset: 0
Media Date: 01/01/1970 00:00:00 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: celont62.internal.scee.net
checkpoint: 1
resume num: 0
Copy on hold: 0
Copy number: 1
Fragment: 3
Kilobytes: 3250688
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: G:\Netbackup-DiskStageG\\celont85.internal.scee.net_1526681174_C1_F3
Host: celont62.internal.scee.net
Block Size: 262144
Offset: 0
Media Date: 01/01/1970 00:00:00 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: celont62.internal.scee.net
checkpoint: 1
resume num: 0
Copy on hold: 0
Copy number: 1
Fragment: 4
Kilobytes: 7203072
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: G:\Netbackup-DiskStageG\\celont85.internal.scee.net_1526681174_C1_F4
Host: celont62.internal.scee.net
Block Size: 262144
Offset: 0
Media Date: 01/01/1970 00:00:00 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: celont62.internal.scee.net
checkpoint: 1
resume num: 0
Copy on hold: 0
Copy number: 1
Fragment: 5
Kilobytes: 349921
Remainder: 0
Media Type: Disk (0)
Density: qscsi (0)
File Num: 0
ID: G:\Netbackup-DiskStageG\\celont85.internal.scee.net_1526681174_C1_F5
Host: celont62.internal.scee.net
Block Size: 262144
Offset: 0
Media Date: 01/01/1970 00:00:00 (0)
Dev Written On: -1
Flags: 0x0
Media Descriptor: celont62.internal.scee.net
checkpoint: 0
resume num: 0
Copy on hold: 0
Copy number: 2
Fragment: 1
Kilobytes: 28652769
Remainder: 0
Media Type: Media Manager (2)
Density: dlt3 (21)
File Num: 23
ID: JB7894
Host: celont64.internal.scee.net
Block Size: 65536
Offset: 10684307
Media Date: 18/05/2018 18:00:23 (1526662823)
Dev Written On: 3
Flags: 0x0
Media Descriptor: ?
Expiration Time: INFINITY (2147483647)
MPX: 0
retention_lvl: infinity (9)
Try to Keep Time: 01/01/1970 00:00:00 (0)
Copy Creation Time: 21/05/2018 13:32:36 (1526905956)
Data Format: Tar
checkpoint: 0
resume num: 1
Key tag: *NULL*
STL tag: *NULL*
Copy on hold: 0
05-21-2018 07:25 AM
Both backup copies (disk and tape) have INFINITY retention.
The reference to '2 weeks' in the staging job is a 'red herring'. You can ignore it.
The retention in the disk staging config is linked to the DSSU Frequency.
See this: https://www.veritas.com/support/en_US/doc/123711489-126541862-0/v41615072-126541862
Internally, NetBackup uses the retention level 1 setting for scheduling purposes with disk staging storage units.....
...
Make sure that the frequency period is set to make the backups occur more frequently than the retention level 1 setting indicates. (The default is two weeks.)
05-21-2018 07:29 AM
thanks very much Marianne
From the output of the commands you sent over I can see both the backup to disk and backup to tape are using inifinate retention, it's just the backup job shows 2 weeks (maybe by default).