02-04-2014 11:00 PM
Hi All ,
We taken a Backup type of Hyper-V, the backup get completed sucessfully with the backup selection of all Local Drives.
But at the time of restore it not showing the some drives to view in the Backup & Archive Resotre window.
Details are below.
Master Server :- NBU=7.5.0.6 / OS=Windows2008
Media Server :- NBU= 7.5.05 / OS=Windows2008
VM Host :- NBU=7.5 /
Please let us know if any info required.
Thanks in Advance,
Bharat
02-04-2014 11:16 PM
does that hyper V vm have any pass through disks ?
if yes those are the once that are not visiable...?
02-05-2014 02:59 AM
There is no any pass through disk..
02-05-2014 03:10 AM
does these VMs is in cluster which is having the cluster Drives..in active -passive configuration
did you identify if is not showing only specific Drives for each backup or its random Drives...?
and also not showing in all backup images or random backup images...?
if they are missing for all backup images..
post the output of below command
bppllist <policyname> -L
and also run another Full backup and moniter the detail status and logs.
03-04-2014 08:31 PM
Hi All,
All drives are getting backed up but only one drives are not able to view while performning restore.
I am able to restore the .vhd file but not able to view the granularity for only one drive in bacakup ,archive & restore window while selecting the restore type as a Normal Backup.
Thanks in Adnvance.
Bharat .
03-26-2014 10:33 PM
Is that in vhdx format.If the virtual disk is in the .vhdx format, you can restore the entire virtual machine but not individual files.
Also is the backup completed with status 0 or status 1?
Can you please provide the output of policy details as per Nagalla.
Please close your other thread as it is the same issue .
https://www-secure.symantec.com/connect/forums/not-able-view-drive-restore-pane
03-28-2014 04:46 PM
Hi Sazz ,
Its VHD format and backup completing with 0 status.
C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist G_FILESRV_HYPER-V_IMPP2
2 -U
------------------------------------------------------------
Policy Name: G_FILESRV_HYPER-V_IMPP22
Policy Type: Hyper-V
Active: yes
Effective date: 07/17/2013 03:39:23
File Restore Raw: yes
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: tmpnebkpmed1-hcart-robot-tld-1
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: Gold
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: Windows-x86 Windows2003 abc
Include: ALL_LOCAL_DRIVES
Schedule: Monthly_Full
Type: Full Backup
Maximum MPX: 2
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 5 (3 months)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: Monthly_Full
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 5
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 08:00:00 --> Sunday 20:00:00
Schedule: Weekly_Full
Type: Full Backup
Maximum MPX: 2
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: Weekly_Full
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 1
Sunday, Week 2
Sunday, Week 3
Sunday, Week 4
EXCLUDE DATE 0 - 07/28/2013
EXCLUDE DATE 1 - 08/25/2013
EXCLUDE DATE 2 - 10/27/2013
EXCLUDE DATE 3 - 11/24/2013
EXCLUDE DATE 4 - 01/26/2014
EXCLUDE DATE 5 - 02/23/2014
EXCLUDE DATE 6 - 04/27/2014
EXCLUDE DATE 7 - 05/25/2014
EXCLUDE DATE 8 - 07/27/2014
EXCLUDE DATE 9 - 09/28/2014
EXCLUDE DATE 10 - 10/26/2014
EXCLUDE DATE 11 - 12/28/2014
EXCLUDE DATE 12 - 01/25/2015
EXCLUDE DATE 13 - 02/22/2015
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 08:00:00 --> Sunday 20:00:00
Schedule: Daily_Incr
Type: Differential Incremental Backup
Maximum MPX: 2
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: Daily_Incr
Server Group: (same as specified for policy)
Calendar sched: Enabled
Monday, Week 1
Tuesday, Week 1
Wednesday, Week 1
Thursday, Week 1
Friday, Week 1
Saturday, Week 1
Monday, Week 2
Tuesday, Week 2
Wednesday, Week 2
Thursday, Week 2
Friday, Week 2
Saturday, Week 2
Monday, Week 3
Tuesday, Week 3
Wednesday, Week 3
Thursday, Week 3
Friday, Week 3
Saturday, Week 3
Monday, Week 4
Tuesday, Week 4
Wednesday, Week 4
Thursday, Week 4
Friday, Week 4
Saturday, Week 4
Monday, Week 5
Tuesday, Week 5
Wednesday, Week 5
Thursday, Week 5
Friday, Week 5
Saturday, Week 5
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Monday 08:00:00 --> Monday 20:00:00
Tuesday 08:00:00 --> Tuesday 20:00:00
Wednesday 08:00:00 --> Wednesday 20:00:00
Thursday 08:00:00 --> Thursday 20:00:00
Friday 08:00:00 --> Friday 20:00:00
Saturday 08:00:00 --> Saturday 20:00:00
C:\Program Files\Veritas\NetBackup\bin\admincmd>
03-28-2014 04:50 PM
It is .VHD format and backup completed with 0 status.Find attached policy out-put.
I am able to view for others drive except one drive.
03-28-2014 06:30 PM
Forwarning, I am not yet as familiar with the Hyper-V backups, but I am familiar with Windows backups that exhibit this behaviour, presuming that it is.
The fastest way to check is in the Backup, Archive, and Restore gui.
Navigate down Shadow Copy Components\User Data\Distributed File System Replication\DfsrReplicatedFolder
Here will be share names if configured. Does the share name have the data you are looking for?
This is per the following technote:
http://www.symantec.com/business/support/index?page=content&id=HOWTO65638
07-29-2014 08:29 AM
Hello All ,
Apolgies for the late responce but we are planning to upgrade the OS because we have some disk issue on the server.
Thanks to all...!!