01-23-2017 02:38 AM - edited 01-23-2017 03:33 AM
Hi All,
Thanks for your always help!!
Currently i am performing a test scenario, which includes cascade OPT-DUP operation.
Here is the operation which i need to perform.
Cascade Opt-dup from Storage_Server_A to Storage_Server_B, and then Storage_Server_B to Storage_Server_C.
Below is the way which i am thinking to proceed for this test.
ON NBU Server:
After this images will be backed up to Storage_Server_A and then first opt-dup will be performed automatically through SLP_1 and images will be copied to Storage_Server_B.
Now my confusion is, whether the above steps will initiate the SLP_2 automatically for coping the images(second opt-dup) from Storage_Server_B to Storage_Server_C?
Or my understanding is wrong and there is some other way to initiate the second opt-dup?
Please give your valuable suggestion over this.
Thanks in advance
Solved! Go to Solution.
01-23-2017 06:39 AM
i.e. @Marianne is saying that with an SLP you can do this...
...a three layer cascade:
--> Backup to STU-A --> --> Duplication to STU-B --> --> --> Duplication to STU-C
...or this, which uses STU-A as the source to duplicate from for both copies/duplications:
--> Backup to STU-A --> --> Duplication to STU-B --> --> Duplication to STU-C
.
N.B: The only simple automated way to do this is using one SLP. You cannot use two SLPs, i.e. this will not work:
SLP1: --> Backup to STU-A --> --> Duplication to STU-B SLP2: --> Duplication
...because an SLP has to start with a "backup" stage.
01-25-2017 01:00 AM
bpduplicate is one of those 'trial and error' commands.
I would personally try with less parameters, e.g.
bpduplicate -backupid jpvm126_1485283746 -cn <copy_number> -dstunit Test_Su2_temp
PS:
I am curious about the type of disk pools and storage units you are using?
'Opt-dup' seems to indicate that this is some kind of dedupe storage?
You may want to try bpimmedia with these parameters (again - trial and error):
bpimmedia -stype <Storage Server Type> -dp <disk pool name>
01-23-2017 05:57 AM - edited 01-23-2017 05:58 AM
Sounds like one SLP with three stages:
--> Backup --> --> Duplication --> --> --> Duplication
01-23-2017 06:30 AM
01-23-2017 06:39 AM
i.e. @Marianne is saying that with an SLP you can do this...
...a three layer cascade:
--> Backup to STU-A --> --> Duplication to STU-B --> --> --> Duplication to STU-C
...or this, which uses STU-A as the source to duplicate from for both copies/duplications:
--> Backup to STU-A --> --> Duplication to STU-B --> --> Duplication to STU-C
.
N.B: The only simple automated way to do this is using one SLP. You cannot use two SLPs, i.e. this will not work:
SLP1: --> Backup to STU-A --> --> Duplication to STU-B SLP2: --> Duplication
...because an SLP has to start with a "backup" stage.
01-24-2017 03:21 AM
Hi All,
Thank you for your suggestion.
From your valuable suggestion, i have been able to perfrom the cascade opt-dup.
Now i need to do the reverse.
below is my requirement:
Currently there are Copy1 on STS-A, Copy2 on STS-B, and Copy3 on STS-C.
(1) Create another disk pool/STU for STS-A and STS-B.
(2) Perform Opt-dup from STS-C to STS-B (Copy4 is created on STS-B)
(3) Perform Opt-dup from STS-B to STS-A (Copy5 is created on STS-A)
(4) Set primary on Copy5
(5) Then, Restore data from Copy5
can you please help me in this too?
01-24-2017 04:18 AM - edited 01-24-2017 04:22 AM
You will have to use the "NetBackup Management / Catalog" functionality, and select "Action:" of "Duplicate", then search correctly, and then perform/request the duplication... all within the Admin Console GUI to perform a manual duplication... or use the CLI command bpduplicate.
To be able to restore from Copy 5, then you will need to ensure that during the last duplication, or in fact during each duplication, that you choose to make the new copy the primary copy.
Remember, NetBackup only ever restores from the primary copy.
01-24-2017 07:42 PM - edited 01-24-2017 10:30 PM
Dear @sdo,
Thanks for your suggetsions.
Unfortunately, i am not able to use the NBU GUI, and have to perform through CLI only.
Here i performed the few steps:
Initially -------------------------------------------------------------------------------- Backup-ID: jpvm126_1485283746 Policy: pqr1 Schedule Type: FULL Retention Level 1 Number of Files: 3 Compression: N Encryption: N Image Type: Regular Primary Copy: 1 Expires: Wed 08 Feb 2017 12:19:06 AM IST Image on Hold: 0 Copy Number: 1 Fragment Number: 1 Fragment Size (KB): 2097184 Media Type: Disk Density: - File Number: - Offset: - Host: jpvm126 Device Written On: - MPX: N Expires: Wed 08 Feb 2017 12:19:06 AM IST Retention Level: 1 MediaID: @aaagq Copy on Hold: 0 Copy Number: 2 Fragment Number: 1 Fragment Size (KB): 2097184 Media Type: Disk Density: - File Number: - Offset: - Host: jpvm126 Device Written On: - MPX: N Expires: Wed 08 Feb 2017 12:19:06 AM IST Retention Level: 1 MediaID: @aaagr Copy on Hold: 0 Copy Number: 3 Fragment Number: 1 Fragment Size (KB): 2097184 Media Type: Disk Density: - File Number: - Offset: - Host: jpvm126 Device Written On: - MPX: N Expires: Wed 08 Feb 2017 12:19:06 AM IST Retention Level: 1 MediaID: @aaags Copy on Hold: 0 After changing to primary copy Backup-ID: jpvm126_1485283746 Policy: pqr1 Schedule Type: FULL Retention Level 1 Number of Files: 3 Compression: N Encryption: N Image Type: Regular Primary Copy: 3 Expires: Wed 08 Feb 2017 12:19:06 AM IST Image on Hold: 0 Copy Number: 1 Fragment Number: 1 Fragment Size (KB): 2097184 Media Type: Disk Density: - File Number: - Offset: - Host: jpvm126 Device Written On: - MPX: N Expires: Wed 08 Feb 2017 12:19:06 AM IST Retention Level: 1 MediaID: @aaagq Copy on Hold: 0 Copy Number: 2 Fragment Number: 1 Fragment Size (KB): 2097184 Media Type: Disk Density: - File Number: - Offset: - Host: jpvm126 Device Written On: - MPX: N Expires: Wed 08 Feb 2017 12:19:06 AM IST Retention Level: 1 MediaID: @aaagr Copy on Hold: 0 Copy Number: 3 Fragment Number: 1 Fragment Size (KB): 2097184 Media Type: Disk Density: - File Number: - Offset: - Host: jpvm126 Device Written On: - MPX: N Expires: Wed 08 Feb 2017 12:19:06 AM IST Retention Level: 1 MediaID: @aaags Copy on Hold: 0
/usr/openv/netbackup/bin/admincmd/bpduplicate -number_copies 1 -dstunit Test_Su2_temp -dp Test_Dp2_temp -backupid jpvm126_1485283746 -pt Standard -st FULLAlthough this did work but not as expected, it didn't copy the images from STS_C to STS_B, then i mentioned the media id for third storage server as -id @aaags but this time it was failed as
[root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpduplicate -number_copies 1 -dstunit Test_Su2_temp -dp Test_Dp2_temp -id @aaags -backupid jpvm126_1485283746 -pt Standard -st FULL Duplicate started 01/25/2017 18:40:05 Activity monitor job id = 14 INF - found no images or media matching the selection criteria
So can you please let me know, where i am going wrong and missing some crucial procedure.
One more thing bpimmedia is displaying the images, but when i am using mediaid, it is showing no image found
[root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid @aaagq no entity was found [root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid @aaagr no entity was found [root@jpvm126 ~]# /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid @aaags no entity was found [root@jpvm126 ~]#
Sorry for my lack of knowledge.
01-25-2017 12:27 AM
Please, any one help on this??
01-25-2017 01:00 AM
bpduplicate is one of those 'trial and error' commands.
I would personally try with less parameters, e.g.
bpduplicate -backupid jpvm126_1485283746 -cn <copy_number> -dstunit Test_Su2_temp
PS:
I am curious about the type of disk pools and storage units you are using?
'Opt-dup' seems to indicate that this is some kind of dedupe storage?
You may want to try bpimmedia with these parameters (again - trial and error):
bpimmedia -stype <Storage Server Type> -dp <disk pool name>
01-25-2017 01:54 AM
Thank you @Marianne Ma'am, So much for your help.
Now i am able to done the duplication from STS_C to STS_B then STS_B to STS_A.
After that STS_A has COPY5, and i changed that image to primary.
Now i am restoring the backup, what i think is as COPY5 is primary so restore should be done through COPY5. So is there any way that i can verify it?
01-25-2017 03:24 AM
I have no idea how anyone can manage NBU without the GUI...
Job details will tell you which storage is used for the restore.
'bpdbjobs -most_columns' perhaps?
01-25-2017 03:42 AM
The bpdbjobs columns are listed here:
https://www.veritas.com/support/en_US/article.000109736
...so maybe you could try:
bpdbjobs -all_columns -jobid 9999 | awk '{print $38}'
...assuming of course that 'restore' jobs do record the copy number being used in field 38.