Does Netbackup support FlashBackup volume sets?

[s_p_kvw3000]

Hi all,

Recently I tried to perform FlashBackup on Storage Foundation volume sets using vxvm method, and after create FlashBackup policy the validation fails. In the same environment a FlashBackup on a volume acts correctly, so I want to know whether Netbackup supports FlashBackup on volume sets. Or I should do some other configuration?

My NetBackup version is 7.1 and Storage Foundation version is 5.1 on SLES 11, the snapshot configuration is made through vxvm commands.

Thanks in advance for all the help.

[Mark_Solutions]

From the guide:

VxFS_Checkpoint and vxvm are the only snapshot methods in Snapshot Client
that support the multi-volume file system (MVS) feature of VxFS 4.0.
The multi-volume file system feature requires aVxVM4.0 volume set. With volume
sets, you can group related volumes into one volume set, and mount a VxFS file
system on it. This means that a VxFS file system can be mounted on more than
one volume. This feature allows file systems to make best use of the different
performance and availability characteristics of the underlying volumes. For
example, file system metadata could be stored on volumes with higher redundancy,
and user data on volumes with better performance.

So it looks OK as long as the server is using the VxFS

What error do you get?

[Marianne]

If I'm not mistaken, vxvm snapshot means Full volume snapshot utilizing FlashSnap license.

This means that you need a fully syncronized snap-mirror.

Does 'vxprint -ht' output reflect snap-ready mirror?

Rather choose 'Auto' method, enable bpfis log and see which method is chosen.

[s_p_kvw3000]

Thanks for reply. I had set the backup selections to /dev/vx/rdsk/sfsdg/fs_0, while fs_0 is the name of volume sets. The volume sets is formatted and mounted with vxfs. I prepared the volume sets using space-optimized instant snapshots. The commands is: # vxassist -g sfsdg make nbu_cachevol_0 5g init=active # vxmake -g sfsdg cache NBU_CACHE cachevolname=nbu_cachevol_0 # vxcache -g sfsdg start NBU_CACHE # vxsnap -g sfsdg prepare fs_0 # vxsnap -g sfsdg make source=fs_0/newvol=SNAP_fs_0_NBU/cache=NBU_CACHE In the policy validation, the error message is ‘Snapshot could not be created with auto method’, and the backup fail with status code 20, detailed status is like this: 10/24/2011 2:56:24 AM - begin Create Snapshot 10/24/2011 2:56:24 AM - Info bpfis(pid=16621) Backup started 10/24/2011 2:56:34 AM - Critical bpbrm(pid=3400) from client vxvm-38: FTL - snapshot method: vxvm abort - does not support non file system backup 10/24/2011 2:56:34 AM - Critical bpbrm(pid=3400) from client vxvm-38: FTL - runtime_check() failed, status 20 10/24/2011 2:56:34 AM - Warning bpbrm(pid=3400) from client vxvm-38: WRN - /dev/vx/rdsk/sfsdg/fs_0 is not frozen 10/24/2011 2:56:34 AM - Info bpfis(pid=16621) done. status: 20 10/24/2011 2:56:34 AM - end Create Snapshot; elapsed time: 00:00:10 10/24/2011 2:56:35 AM - end writing Status 20 And with auto method,the detailed status is like this: 10/24/2011 3:42:00 AM - begin Create Snapshot 10/24/2011 3:42:01 AM - Info bpfis(pid=8415) Backup started 10/24/2011 3:42:14 AM - Critical bpbrm(pid=2892) from client vxvm-38: FTL - No snapshot method available for /files1 10/24/2011 3:42:14 AM - Critical bpbrm(pid=2892) from client vxvm-38: FTL - Cannot process raw device /dev/vx/rdsk/sfsdg/fs_0 10/24/2011 3:42:14 AM - Critical bpbrm(pid=2892) from client vxvm-38: FTL - process_fs_list() failed, status 20 10/24/2011 3:42:14 AM - Info bpfis(pid=8415) done. status: 20 10/24/2011 3:42:14 AM - end Create Snapshot; elapsed time: 00:00:14 10/24/2011 3:42:16 AM - end writing Status 20 This job has no bpfis log generated.

[Marianne]

bpfis process was called on the client:

"Info bpfis(pid=16621) Backup started".
and again on 2nd backup attempt: "bpfis(pid=8415)".

Did you create bpfis folder on the client under /usr/openv/netbackup/logs?

Please post your policy config as well:
bppllist <policy-name> -L

[s_p_kvw3000]

Sorry, I used to find logs in the server. The vxprint result is: # mount /dev/vx/dsk/sfsdg/fs_0 on /files1 type vxfs (rw,delaylog,largefiles,ioerror=mwdisable) # vxsnap -g sfsdg print NAME SNAPOBJECT TYPE PARENT SNAPSHOT %DIRTY %VALID vol01 -- volume -- -- -- 100.00 SNAP-vol01_snp volume -- SNAP-vol01 0.01 -- SNAP-vol01 vol01_snp volume vol01 -- 0.01 0.00 # vxprint Disk group: sfsdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg sfsdg sfsdg - - - - - - vt SNAP_fs_0_NBU - ENABLED - - ACTIVE - - v SNAP-vol01 SNAP_fs_0_NBU ENABLED 2097152 - ACTIVE - - pl SNAP-vol01-P01 SNAP-vol01 ENABLED 2097152 - ACTIVE - - sc SNAP-vol01-S01 SNAP-vol01-P01 ENABLED 2097152 0 - - - dc SNAP-vol01_dco SNAP-vol01 - - - - - - v SNAP-vol01_dcl gen ENABLED 544 - ACTIVE - - pl SNAP-vol01_dcl-01 SNAP-vol01_dcl ENABLED 544 - ACTIVE - - sd sde-01 SNAP-vol01_dcl-01 ENABLED 544 0 - - - sp vol01_snp SNAP-vol01 - - - - - - vt fs_0 - ENABLED - - ACTIVE - - v vol01 fs_0 ENABLED 2097152 - ACTIVE - - pl vol01-01 vol01 ENABLED 2097152 - ACTIVE - - sd sdb-01 vol01-01 ENABLED 2097152 0 - - - dc vol01_dco vol01 - - - - - - v vol01_dcl gen ENABLED 544 - ACTIVE - - pl vol01_dcl-01 vol01_dcl ENABLED 544 - ACTIVE - - sd sdd-01 vol01_dcl-01 ENABLED 544 0 - - - sp SNAP-vol01_snp vol01 - - - - - - co NBU_CACHE - ENABLED - - ACTIVE - - v nbu_cachevol_0 NBU_CACHE ENABLED 10485760 - ACTIVE - - pl nbu_cachevol_0-01 nbu_cachevol_0 ENABLED 10485760 - ACTIVE - - sd sdc-01 nbu_cachevol_0-01 ENABLED 10485760 0 - - - The policy is: Policy Name: test_02 Options: 0x0 template: FALSE audit_reason: ? Names: (none) Policy Type: FlashBackup (20) Active: yes Effective date: 10/21/2011 10:37:26 File Restore Raw: yes Mult. Data Stream: no Perform Snapshot Backup: yes Snapshot Method: vxvm Snapshot Method Arguments: async_resync=0,max_snapshots=1,sync_wait=1,num_sync_v ols=1,iosize=1,slow=0 Perform Offhost Backup: no Backup Copy: 0 Use Data Mover: no Data Mover Type: 2 Use Alternate Client: no Alternate Client Name: (none) Use Virtual Machine: 0 Hyper-V Server Name: (none) Enable Instant Recovery: no Policy Priority: 0 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Collect BMR Info: no Keyword: (none specified) Data Classification: - Residence is Storage Lifecycle Policy: no Client Encrypt: no Checkpoint: no Residence: - Volume Pool: NetBackup Server Group: *ANY* Granular Restore Info: no Exchange Source attributes: no Exchange 2010 Preferred Server: (none defined) Application Discovery: no Discovery Lifetime: 28800 seconds Generation: 23 Ignore Client Direct: no Client/HW/OS/Pri: vxvm-38 Linux SuSE2.6.16 0 0 0 0 ? Include: /dev/vx/rdsk/sfsdg/fs_0 Schedule: FULL Type: FULL (0) Frequency: 7 day(s) (604800 seconds) Maximum MPX: 1 Synthetic: 0 PFI Recovery: 0 Retention Level: 1 (2 weeks) u-wind/o/d: 0 0 Incr Type: DELTA (0) Alt Read Host: (none defined) Max Frag Size: 0 MB 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: Day Open Close W-Open W-Close Sunday 000:00:00 000:00:00 And the bpfis log is: 22:30:31.037 [10898] <2> logparams: bpfis create -nbu -owner NBU -id vxvm-38_1319553026 -bpstart_to 300 -bpend_to 300 -backup_copy 0 -ru root -pt 20 -clnt vxvm-38 -rg other -fim vxvm:max_snapshots=1,sync_wait=1,num_sync_vols=1,iosize=1,slow=0 -class test_02 -sched FULL -fso -S master34 22:30:31.037 [10898] <2> bpfis main: received FIM as [64] vxvm:max_snapshots=1,sync_wait=1,num_sync_vols=1,iosize=1,slow=0 22:30:31.038 [10898] <4> bpfis: INF - BACKUP START 10898 22:30:31.040 [10898] <2> bpfis main: receive filelist: 22:30:31.040 [10898] <2> bpfis main: receive filelist: 22:30:31.040 [10898] <2> bpfis main: receive filelist: 22:30:31.061 [10898] <2> read_vfm_conf: options=0x2 22:30:31.061 [10898] <2> read_vfm_conf: Reading file: /usr/openv/netbackup/vfm.conf 22:30:31.061 [10898] <2> read_vfm_conf: Found FIM: FlashSnap 22:30:31.061 [10898] <2> read_vfm_conf: Found library: /usr/openv/lib/libfi_FlashSnap.so 22:30:31.062 [10898] <2> parse_ssm_parms: Found keyword keep_fi …… 22:30:31.071 [10898] <2> vnet_pbxConnect: pbxConnectEx Succeeded 22:30:31.071 [10898] <2> logconnections: BPRD CONNECT FROM 129.111.15.38.56274 TO 129.111.15.34.1556 fd = 5 22:30:40.563 [10898] <4> bpfis: INF - FIS_ID=vxvm-38_1319553026 22:30:40.576 [10898] <32> bpfis: FTL - snapshot method: vxvm abort - does not support non file system backup 22:30:40.576 [10898] <16> bpfis: FTL - runtime_check() failed, status 20 22:30:40.576 [10898] <4> bpfis: INF - Thawing /dev/vx/rdsk/sfsdg/fs_0 using snapshot method vxvm. 22:30:40.576 [10898] <8> bpfis: WRN - /dev/vx/rdsk/sfsdg/fs_0 is not frozen 22:30:40.576 [10898] <8> bpfis: WRN - snapshot delete returned status 20 22:30:40.577 [10898] <4> bpfis: INF - EXIT STATUS 20: invalid command parameter 22:30:46.349 [10910] <2> logparams: bpfis delete -nbu -id vxvm-38_1319553026 -bpstart_to 300 -bpend_to 300 -clnt vxvm-38 -S master34 22:30:46.356 [10910] <2> vnet_pbxConnect: pbxConnectEx Succeeded 22:30:46.357 [10910] <2> logconnections: BPRD CONNECT FROM 129.111.15.38.39420 TO 129.111.15.34.1556 fd = 4 22:30:51.656 [10910] <4> bpfis: INF - BACKUP START 10910 22:30:51.656 [10910] <32> bpfis: FTL - cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.vxvm-38_1319553026.0 22:30:51.657 [10910] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed

[Marianne]

This error is really confusing:

22:30:40.576 [10898] <32> bpfis: FTL - snapshot method: vxvm abort - does not support non file system backup

As per the extract from the Guide in Mark's post, multi-volume filesystems seems to be supported, but when I look at the compatibility guide, this combination is listed under Arrays, Disk, Local Disk, Solaris (p. 541):

I can't find similar compatibilty under SLES, in fact, there is no SLES heading in this section, only RHEL.

In all honesty, I find this doc ( nbu_7x_SNC_scl_2011_07_06.pdf ) with it's 1922 pages difficult to read, but from what I can see, your setup is possibly not supported on your OS...

Maybe best to log a Support call with Symantec for a definite answer.

*** EDIT ***

picture went missing from original post....

[Mark_Solutions]

I agree with Marianne - the Status 20 indicates a configuration error which indicates an unsupported version of the file system (unless your file system is not at the same version level as volume manager?)

One part also mentions the system being raw - so something is mixed up somewhere.

Log a call for a definitive answer and please let us know the result

[Marianne]

Have you contacted Support yet?

We are curious to know the outcome.

[s_p_kvw3000]

I’m currently calling for support, it may take some time, and I’ll let you know after I got the reply.

[Marianne]

Any feedback from Support yet?