SLP Query

[noazara]

I am very new to this.Please be more specific !!!

Hi We have a request to have a backup on tape for infinity.

We have a slp which do the backup on disk,then on tape .

1. I want to know the media id from this nbstlutil command .What can i run?
2. difference between image,copy and fragments?
3. how would i know which is my copy 1 and which is my cop2 and which is copy3 from this nbstlutil command?

NBU 7.1

LINUX redhat

bash-3.2$ sudo ./nbstlutil list   -backupid  bird24_1370616401 -U

Image:

 Master Server            : root21

 Backup ID                : bird24_1370616401

 Client                   : bird24

 Backup Time              : 1370616401 (Fri Jun  7 10:46:41 2013)

 Policy                   : test-full

 Client Type              : 0

 Schedule Type            : 0

 Storage Lifecycle Policy : slp-full23

 Storage Lifecycle State  : 3 (COMPLETE)

 Time In Process          : 1370621196 (Fri Jun  7 12:06:36 2013)

 Data Classification ID   : 7BB3B51AC99511E19A5F47C28D1966EA (BC)

 Version Number           : 4

 OriginMasterServer       : (none specified)

 OriginMasterServerID     : 00000000-0000-0000-0000-000000000000

 Import From Replica Time : 0 (Wed Dec 31 19:00:00 1969)

 Required Expiration Date : 0 (Wed Dec 31 19:00:00 1969)

 Created Date Time        : 1370621185 (Fri Jun  7 12:06:25 2013)

 Copy:

   Master Server       : root21

   Backup ID           : bird24_1370616401

   Copy Number         : 1

   Copy Type           : 0

   Expire Time         : 1373640401 (Fri Jul 12 10:46:41 2013)

   Expire LC Time      : 1373640401 (Fri Jul 12 10:46:41 2013)

   Try To Keep Time    : 1373640401 (Fri Jul 12 10:46:41 2013)

   Residence           : st1

   Copy State          : 3 (COMPLETE)

   Job ID              : 0

   Retention Type      : 0 (FIXED)

   MPX State           : 0 (FALSE)

   Source              : 0

   Destination ID      : 0

   Last Retry Time     : 0

   Fragment:

     Master Server     : root21

     Backup ID         : bird24_1370616401

     Copy Number       : 1

     Fragment Number   : 1

     Resume Count      : 0

     Media ID          : @aaaac

     Media Server      : root21

     Storage Server    : (none specified)

     Media Type        : 0 (DISK)

     Media Sub-Type    : 6 (STSDYNAMIC)

     Fragment State    : 1 (ACTIVE)

     Fragment Size     : 114528354304

     Delete Header     : 1

     Fragment ID       : @aaaac

   Fragment:

     Master Server     : root21

     Backup ID         : bird24_1370616401

     Copy Number       : 1

     Fragment Number   : 2

     Resume Count      : 0

     Media ID          : @aaaac

     Media Server      : root21

     Storage Server    : (none specified)

     Media Type        : 0 (DISK)

     Media Sub-Type    : 6 (STSDYNAMIC)

     Fragment State    : 1 (ACTIVE)

     Fragment Size     : 39873380352

     Delete Header     : 1

     Fragment ID       : @aaaac

[mph999]

1. I want to know the media id from this nbstlutil command .What can i run?
2. difference between image,copy and fragments?
3. how would i know which is my copy 1 and which is my cop2 and which is copy3 from this nbstlutil command?

(1)

From the output you provided, the media ID can be seen in the fragment section.

 Fragment ID       : @aaaac

In this case, this fragment in on disk, with 'ID' @aaaac

If the fragment was on tape, this would show the tape media ID.

there is no nbstlutil command that only shows the media ID.  You have to just run the command like you have done and pick out the bits you want, or use grep / awk commands to filter the parts you want, though this would be a little tricky in this example.

You could run without the -U and then you get the I / C /F parts all on x3 separate lines , but there are no headings for the individaul parts.  However, you can work out by comparing this output to the output you have shown, and see what each field is.  I haven't got an example at the moment, but it's fairly easy to work out the bits you want.  

(2)

Image/ Copy /Frag

The Image is the 'top' leve of a backup image, it is the component that 'contains' the Copy part and Fragment.

The Fragment part lists the 'fragments' which are in effect the actual data. The fragment has a configerable max size and if the data in the backup exceeds this then the backup will be split into multiple fragments.  So, if the fragment size was 100MB and the data size in the backup was 200MB then each copy of the backup would contain 2 fragements.  If the frag size was 200MB, then the backup would fit in 1 fragment.

The Copy is just a way to track other copies of the backup, as these contain different fragments which may have different retention times.

It is easier to look at the parts like this :

                                                                            Image

                 Copy1                                             Copy2                                        Copy3

          Fragment1                                            Fragment1                                Fragement1

          Fragment2                                            Fragment2                                Fragement2

          Fragment3                                            Fragment3                                Fragement3

 If you like, you can think about the Image and Copy parts as 'virtual' containers that are simply a way to keep track of the Fragments.  In NBU the fragments are the actual data on the disk (or tape).

If you think about it like a filing cabinet in an office.

The filing cabinet contains 3 draws.

I have 3 copies of a document, printed on paper.  All 3 copies are exactly the same.  Each copy is 3 pages long, so there are 9 pieces of paper in total.

I place one copy of the document in each draw.

Now, the filing cabnet itself = the Image

Each draw = Copy

The pieces of paper = the Fragments

(3)

You can see which copy is which - the copy number is shown in both the Copy part and the Frag part of the output.

Martin

[noazara]

My backup was also on media id.I am unable to see the media id in this command.Please suggest.I can see that in catalog section.

Thanks a lot martin !!!

[noazara]

IN my 2 environments.copy 2 is not showing in nbstlutil command.copy 2 is going on Tape.

copy 1 on data domain on site A 

copy 2 is on tapeon SITE A.

copy 3  replicated to DD on site B.

copy 4 replicated on DD on site C

COPY 1,3,4 is showing in the command But not the tape copy.

Please help !!!!

[Marianne]

Use bpimagelist instead:

bpimagelist -backupid  bird24_1370616401 -L

[mph999]

There is only one copy shown in the output you gave, you need to show all the output.

Alternatively,. you could use the bpimagelist command as Marianne suggests, then we can see what is happening.

You cannot specify individual copies with teh nbstlutil command, so if it is not listed it might be the case that the tape copy hasn't been made, or if it had, it was expired.

Martin

[noazara]

Thats fine.but why media id is not showing in the nbstlutil list command?Why it is not showing copy 2 which is tape?

[noazara]

I can see that from catalog section --copy 2 .it is showin  the media id.but not in the nbstlutil command.

Please help.

[Marianne]

Why not just use a command that gives you the information you need? - bpimagelist.

It is impossible for us non-NBU developers to tell you why a specific command does not give you the info you want/need.

Please bear in mind that you are using an older version of NBU - changes have been made to nbstlutil command in NBU 7.5.

[mph999]

You have only posted up part of the nbstlutil command, I can only see copy 1. You will need to post up the complete output so we can have a look at it, and also post up the bpimagelist output. Thanks Martin

[noazara]

Bpimagelist output is showing the media too. I am concerned that why nbstlutil list is not showing tape copy.?

[noazara]

Image:

 Master Server            : unixmaster01

 Backup ID                : clientunix01_1370823836

 Client                   : clientunix01

 Backup Time              : 1370823836 (Sun Jun  9 17:23:56 2013)

 Policy                   : unix23

 Client Type              : 0

 Schedule Type            : 4

 Storage Lifecycle Policy : slp1

 Storage Lifecycle State  : 3 (COMPLETE)

 Time In Process          : 1370824389 (Sun Jun  9 17:33:09 2013)

 Data Classification ID   : A99966040D6111E2A161A0BD5663F24E (MCR_SunGard)

 Version Number           : 6

 OriginMasterServer       : (none specified)

 OriginMasterServerID     : 00000000-0000-0000-0000-000000000000

 Import From Replica Time : 0 (Wed Dec 31 16:00:00 1969)

 Required Expiration Date : 0 (Wed Dec 31 16:00:00 1969)

 Created Date Time        : 1370824047 (Sun Jun  9 17:27:27 2013)

 Copy:

   Master Server       : unixmaster01

   Backup ID           : clientunix01_1370823836

   Copy Number         : 1

   Copy Type           : 0

   Expire Time         : 1372033436 (Sun Jun 23 17:23:56 2013)

   Expire LC Time      : 1372033436 (Sun Jun 23 17:23:56 2013)

   Try To Keep Time    : 1372033436 (Sun Jun 23 17:23:56 2013)

   Residence           : stu1

   Copy State          : 3 (COMPLETE)

   Job ID              : 0

   Retention Type      : 0 (FIXED)

   MPX State           : 0 (FALSE)

   Source              : 0

   Destination ID      : 0

   Last Retry Time     : 0

   Fragment:

     Master Server     : unixmaster01

     Backup ID         : clientunix01_1370823836

     Copy Number       : 1

     Fragment Number   : 1

     Resume Count      : 0

     Media ID          : @aaaab

     Media Server      : lx002

     Storage Server    : (none specified)

     Media Type        : 0 (DISK)

     Media Sub-Type    : 6 (STSDYNAMIC)

     Fragment State    : 1 (ACTIVE)

     Fragment Size     : 12004163584

     Delete Header     : 1

     Fragment ID       : @aaaab

 Copy:

   Master Server       : unixmaster01

   Backup ID           : clientunix01_1370823836

   Copy Number         : 3

   Copy Type           : 1

   Expire Time         : 1372033436 (Sun Jun 23 17:23:56 2013)

   Expire LC Time      : 1372033436 (Sun Jun 23 17:23:56 2013)

   Try To Keep Time    : 1372033436 (Sun Jun 23 17:23:56 2013)

   Residence           : stu2

   Copy State          : 3 (COMPLETE)

   Job ID              : 3055058

   Retention Type      : 0 (FIXED)

   MPX State           : 0 (FALSE)

   Source              : 1

   Destination ID      :

   Last Retry Time     : 1370824631

   Fragment:

     Master Server     : unixmaster01

     Backup ID         : clientunix01_1370823836

     Copy Number       : 3

     Fragment Number   : 1

     Resume Count      : 1

     Media ID          : @aaaav

     Media Server      : lx002

     Storage Server    : (none specified)

     Media Type        : 0 (DISK)

     Media Sub-Type    : 6 (STSDYNAMIC)

     Fragment State    : 1 (ACTIVE)

     Fragment Size     : 12004163584

     Delete Header     : 1

     Fragment ID       : @aaaav

In above instance,It is not showing copy2 which is on tape

[Marianne]

Please show us bpimagelist output as requested previously.

I am concerned that why nbstlutil list is not showing tape copy.?

I have said the following before:

Please bear in mind that you are using an older version of NBU - changes have been made to nbstlutil command in NBU 7.5.

[noazara]

So in NBU 7.1,nbstlutil list will not show details of tape copy?Am i correct

Below is the output:

-bash-3.2$ sudo ./bpimagelist -backupid bird24_1370616401 -L

Client:            bird24

Backup ID:         bird24_1370616401

Policy:            test

Policy Type:       Standard (0)

Proxy Client:      (none specified)

Creator:           root

Name1:             (none specified)

Sched Label:       Full

Schedule Type:     FULL (0)

Retention Level:   5 weeks (0)

Backup Time:       Fri 07 Jun 2013 10:46:41 AM ED (1370616401)

Elapsed Time:      4784 second(s)

Expiration Time:   Fri 12 Jul 2013 10:46:41 AM ED (1373640401)

Compressed:        no

Client Encrypted:  no

Kilobytes:         150782944

Number of Files:   98

Number of Copies:  4

Number of Fragments:   5

Histogram:         -1 -1 -1 -1 -1 -1 -1 -1 -1 -1

DB Compressed:     no

Files File Name:   test_1370616401_FULL.f

Previous Backup Files File Name:   (none specified)

Parent Backup Image File Name:   (none specified)

SW Version:        (none specified)

Options:           0x0

MPX:               0

TIR Info:          0

TIR Expiration:    Wed 31 Dec 1969 07:00:00 PM ES (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:  Wed 31 Dec 1969 07:00:00 PM ES (0)

BI Full Time:      Wed 31 Dec 1969 07:00:00 PM ES (0)

Request Pid:       0

Backup Status:     0

Stream Number:     0

Backup Copy:       Standard (0)

Files File size:     14587

PFI type:     0

IMAGE_ATTRIBUTE:     0

Primary Copy:      1

Image Type:        0  (Regular)

Job ID:            260669

Num Resumes:       2

Resume Expiration: Wed 31 Dec 1969 07:00:00 PM ES (0)

Data Classification:    BC

Data_Classification_ID: 7BB3B51AC99511E19A5F47C28D1966EA

Storage Lifecycle Policy:    slp1

Storage Lifecycle Policy Version:    4

STL_Completed:      3

Remote Expiration Time: Wed 31 Dec 1969 07:00:00 PM ES (0)

Origin Master Server:  (none specified)

Origin Master GUID:    (none specified)

Snap Time:      Wed 31 Dec 1969 07:00:00 PM ES (0)

Copy number:       1

 Fragment:         1

 Kilobytes:        111844096

 Remainder:        0

 Media Type:       Disk (0)

 Density:          qscsi (0)

 File Num:         0

 ID:               @aaaac

 Host:             master1

 Block Size:       262144

 Offset:           0

 Media Date:       Wed 31 Dec 1969 07:00:00 PM ES (0)

 Dev Written On:   -1

 Flags:            0x0

 Media Descriptor:        

 Expiration Time:  Fri 12 Jul 2013 10:46:41 AM ED (1373640401)

 MPX:              0

 retention_lvl:    5 weeks (0)

 Try to Keep Time:  Fri 12 Jul 2013 10:46:41 AM ED (1373640401)

 Copy Creation Time:  Fri 07 Jun 2013 12:06:25 PM ED (1370621185)

 checkpoint:       1

 resume num:       0

 Key tag:          *NULL*

 STL tag:          0

Copy number:       1

 Fragment:         2

 Kilobytes:        38938848

 Remainder:        0

 Media Type:       Disk (0)

 Density:          qscsi (0)

 File Num:         0

 ID:               @aaaac

 Host:             master1

 Block Size:       262144

 Offset:           0

 Media Date:       Wed 31 Dec 1969 07:00:00 PM ES (0)

 Dev Written On:   -1

 Flags:            0x0

 Media Descriptor:        

 checkpoint:       0

 resume num:       0

Copy number:       2

 Fragment:         1

 Kilobytes:        150782944

 Remainder:        0

 Media Type:       Media Manager (2)

 Density:          hcart3 (20)

 File Num:         4

 ID:               303263

 Host:             master1

 Block Size:       65536

 Offset:           11

 Media Date:       Fri 07 Jun 2013 05:50:26 AM ED (1370598626)

 Dev Written On:   4

 Flags:            0x0

 Media Descriptor:        ?

 Expiration Time:  Fri 12 Jul 2013 10:46:41 AM ED (1373640401)

 MPX:              0

 retention_lvl:    5 weeks (0)

 Try to Keep Time:  Fri 12 Jul 2013 10:46:41 AM ED (1373640401)

 Copy Creation Time:  Fri 07 Jun 2013 12:40:38 PM ED (1370623238)

 checkpoint:       0

 resume num:       0

 Key tag:          *NULL*

 STL tag:          *NULL*

Copy number:       3

 Fragment:         1

 Kilobytes:        150782944

 Remainder:        0

 Media Type:       Media Manager (2)

 Density:          hcart3 (20)

 File Num:         1

 ID:               AAB711

 Host:             master1

 Block Size:       65536

 Offset:           2

 Media Date:       Sun 09 Jun 2013 01:16:08 PM ED (1370798168)

 Dev Written On:   5

 Flags:            0x0

 Media Descriptor:        ?

 Expiration Time:            INFINITY       (2147483647)

 MPX:              0

 retention_lvl:    infinity (9)

 Try to Keep Time:  Wed 31 Dec 1969 07:00:00 PM ES (0)

 Copy Creation Time:  Sun 09 Jun 2013 02:07:37 PM ED (1370801257)

 checkpoint:       0

 resume num:       0

 Key tag:          *NULL*

 STL tag:          *NULL*

Copy number:       4

 Fragment:         1

 Kilobytes:        150782944

 Remainder:        0

 Media Type:       Media Manager (2)

 Density:          hcart3 (20)

 File Num:         1

 ID:               AAB717

 Host:             master1

 Block Size:       65536

 Offset:           2

 Media Date:       Sun 09 Jun 2013 01:16:08 PM ED (1370798168)

 Dev Written On:   7

 Flags:            0x0

 Media Descriptor:        ?

 Expiration Time:            INFINITY       (2147483647)

 MPX:              0

 retention_lvl:    infinity (9)

 Try to Keep Time:  Wed 31 Dec 1969 07:00:00 PM ES (0)

 Copy Creation Time:  Sun 09 Jun 2013 02:07:37 PM ED (1370801257)

 checkpoint:       0

 resume num:       0

 Key tag:          *NULL*

 STL tag:          *NULL*

[Marianne]

All I can tell you for sure is that bpimagelist works.

Glad I could help!

[noazara]

My query is why nbstlutil is not showing media id ? Is there any issues in my environment?

[mph999]

7.1 should show copies on tape, clearly here, something is wrong. I don't see anyting obvious in the imaglist output, I'll look again later as I have to go out. I will hazard a guess that the copy entry is not in the image.copy db table, and the fragments are not in the image.fragment table. Why they are missing could be many reasons, I'm not going to guess because I have no idea of the history of the system. Personally I would check another image and see if there is the same isseue, if so I would upgrade to at least 7.1.0.4 as improvements are constantly made. Another issue is to log a call and see if support can find something, nbdb_unload will be required as well as finding out if this is a one-off issue, or one that reoccurs, Martin

[Marianne]

We have no insight into your environment.

Are all copies made with SLP? Or with something else like vault or script, etc?

If 3rd copy is made with non-SLP method, it will explain why bpimagelist is reporting on tape copy and not nbstlutil. 

[noazara]

all are done by SLP.Vault is used to eject only.

[Marianne]

It seems you have 3 choices:

1: Upgrade/patch your master and media servers

2. Log a Support call

3. Use bpimagelist workaround.