Quantcast
Channel: Symantec Connect - Backup and Recovery - Articles
Viewing all 240 articles
Browse latest View live

Steps to change Tape drive density name in Netbackup 7

0
0

Steps to change Tape drive density name in Netbackup 7

The below steps by step information on how to change a tape drive density name from HCART to HCART2/HCART3

Note: It is advisable that you stop all the ongoing backup?restoration before proceeding as this required media manager services restart

 

Step 1: Login to you Netbackup Java console

a.jpg

 

Step 2: Expand the devices option under Media and Device management

b.jpg

 

Step 3 : Select the Drives under devices and you will be able to see the list of drives configured

c.jpg

 

Step 4: Right click the drive whose media density name has to be changed and select change

d.jpg

 

Step 5:No you will have the Change Drive window to change the drive information.

On this below the drive information you can find the option Drive type, click on the drop-down button and select the name that had to set to the drive

e.jpg

f.jpg

Step 6: Check the option Drive is in a robotic library and select the robot name that controls the drive

g.jpg

 

Step 7: Now you will be requested to restart the Media manager services , press ok to restart

h.jpg

 

You can see the drive set with the new density

i.jpg

 

 


Using LiveUpdate to Upgrade Netbackup client from 7.1.0.4 to 7.5

0
0

When LiveUpdate is used to Upgrade the Netbackup client version, you might be seeing issues that LiveUpdate is failing with the message:

"20.06.2013, 12:25:58 GMT -> HttpSendRequest (status 304): Request succeeded - File up to date so download is not required" in log.liveupdate or in the NetBackup job details you also can find the information "No Updates found".

This problematic you can only find when the Upgrade to the version 7.1.0.4 was done with LiveUpdate. LiveUpdate always downloads newer files than this what it has already in its local cache directory:  f.e. "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"

When the LiveUpdate prepares to download f.e. symantec$20netbackup$20x86$20windows_7.1_english_livetri.zip  the files is always checks for the time stamp and when this file is already present in the local cache with a newer modification date, than LiveUpdate wont download this file.

As Netbackup 7.5 was released erlier than the Netbackup 7.1.0.4 its LU files has as well the older time stamp.

Netbackup 7.1.0.4 LiveUpdate bundle:
19/03/2012  16:56       185,068,179 1332171690jtun_nb_7.1.0.4.winnt.x86.zip
19/03/2012  16:57        45,624,044 1332171690jtun_nb_jav_7.1.0.4.winnt.x86.zip

Netbackup 7.5 LiveUpdate bundle:
08/02/2012  19:27       225,661,095 1328614459jtun_nb_7.5.winnt.x64.zip
08/02/2012  19:27       166,592,635 1328614459jtun_nb_7.5.winnt.x86.zip  
08/02/2012  19:29       2,978 nbclient$5fhp$2dux$2dia64_7.1_english_livetri.zip

As those files for Netbackup 7.5 are older, LiveUpdate will not download them and finish with the above messages.

Workaround 1: Remove / Delete the content in the folder C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads on each remote client where they are present.

Workaround 2: Delete / remove the LiveUpdate cache on remote clients (Control Panel > LiveUpdate -> Cache)

Workaround 3: Change the Modification date of the "Netbackup 7.5 LiveUpdate bundle files" to be newer than the files from Version 7.1.0.4

So the Workaround 3 is just one change in the LiveUpdate repository which will resolve those issues on all remote clients automatic when the criteria are matching the above scenario.

As well the pre requirements for the above steps is the Netbackup LiveUpdate Guide

Troubleshoot NetBackup Status Code: 99

0
0

Permanent link

 

Problem:  How to troubleshoot NetBackup for NDMP Backup failures when status code: 99 (NDMP backup failure) is reported.  Includes logging instructions.
 

Error:  STATUS CODE: 99
 

Cause:  Status 99 in NDMP backups is generic. Further troubleshooting is required.
 

Solution:

During regular (standard) NDMP backups, avoid potential NDMP communications failures between NetBackup media servers and the Network Attached Storage (NAS) host.

The following troubleshooting steps may help isolate the root cause of NDMP backup issues. If they do not, proceed with logging instructions in Step 8.

NOTE:  Terminology for the types of NDMP backups can be confusing:

  • Remote NDMP:  The backup is performed on the media server, using the device paths defined to the media server.
  • Local:  The backup is performed using the device paths attached/zoned to the NAS host.
  • 3-Way:  The backup of a NAS host is performed using the device paths attached/zoned to another NAS host

To isolate the root cause of a NDMP backup failure:

1. On the media server, test the connection to the NAS device on the NDMP port (10000) by typing the telnet command.  Try both the hostname and its IP address.  For example: telnet ndmp_host 10000

2. To test connectivity and credentials of the NDMP host and its devices:

  •  Type tpautoconf -verify [NAS hostname]
  •  Type tpautoconf -probe [NAS hostname] to  probe the scsi bus for devices (local or 3-Way only).
  •  On another master or media server, type the above two commands to check for another route or network path.
  • Compare the probe results with the native NAS commands:

          NetApp:  sysconfig -t
          EMC Celerra:  server_devconfig [datamover name] -l -s -n  (list, scsi, non-disk)
         Other:  See system documentation

3. On the NAS, and type the command ndmpd status to verify that the NDMP daemon is running.  If it is not, enable the ndmp daemon and verify again by typing the command ndmpd status.  For information on starting the ndmp daemon, see the NAS system documentation.

4. For EMC Celerra devices, ensure that the SnapSure feature is enabled.  See TECH170310 for information on SnapSure and other considerations.

5. On the media or master server, type the telnet and tpautoconf command tests again from Step 1 to test connectivity, credentials, and devices.

6.  If Local or 3-Way backup, do the following to verify that the volume can be accessed and backed up:

  • First, mount a scratch tape in the drive using robtest or some other means and perform a backup.
  • On the NAS device, type the appropriate native command:

Network Appliance (NetApp): dump 0uf nrst0a /<file system> (Substitute the proper non-rewind device path if it is not nrst0a as in this example).

This command will write data from the specified file system on the Network Appliance server directly to tape. If this dump does not complete successfully, then the problem is most likely a NetWork Appliance problem. To resolve the issue, open a call with Network Appliance technical support. If the dump does complete successfully, open a call with NetBackup support.

For EMC Celerra, refer to the server_archive command in the system documentation.

NOTE:  The Backup Path specified in the NetBackup policy must be the exact case-sensitive path as the filer sees it.

7.  For performance issues, try backing up the path in the policy to a null device and note the timing:

NetApp:  dump 0f null /vol/volname
EMC Celerra:  server_archive <datamover name> -w -f /dev/null/ -J <file path>

8. Based on your findings, proceed with any required configuration changes or, if there are no changes, begin backups or restores.

9.  If none of the above troublesooting steps resolve the issue, enable debug logging on the NetBackup media server and on the NAS device.

To enable debug logging:

1. Depending on your media server platform, do the following:

For Windows media server: 

  • On the NetBackup console, go to Host Properties --> Media Server and double-click the media server that services this backup to open the Properties dialog box. If this media server is the same as the master server, go to Master Server instead.
  • Go to the Logging section and change the global logging level to 5 (maximum).
  • Click OK to exit.

For UNIX media server: 

  • Add VERBOSE to the /usr/openv/netbackup/bp.conf file in the following format:  VERBOSE = 5

2. Make sure that the following legacy log directories exist on the media server that services the backup:

For Windows media server:
\NetBackup\logs\bpbrm
\NetBackup\logs\bptm
\NetBackup\logs\ndmpagent

For Unix media server:
/usr/openv/netbackup/logs/bpbrm
/usr/openv/netbackup/logs/bptm
/usr/openv/netbackup/logs/ndmpagent

3. Run the following commands on the media server that services this backup to increase the unified logging levels:

For Windows media server:
\NetBackup\bin\vxlogcfg -a -p 51216 -o 134 -s DebugLevel=6
\NetBackup\bin\vxlogcfg -a -p 51216 -o 151 -s DebugLevel=6
\NetBackup\bin\vxlogcfg -a -p 51216 -o 134 -s DiagnosticLevel=6
\NetBackup\bin\vxlogcfg -a -p 51216 -o 151 -s DiagnosticLevel=6

For Unix media server:
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 134 -s DebugLevel=6
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 151 -s DebugLevel=6
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 134 -s DiagnosticLevel=6
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 151 -s DiagnosticLevel=6

4. Enable ndmpd debug logging on the NAS device:

  • For Network Appliance NAS, type the following to enable ndmpd debug logging:  ndmpd debug 70
  • EMC Celerra:  Enable debug logging on the datamover as described in Article TECH150646
  • For other NAS devices, see the vendor documentation.

5. Reproduce the error.

6.  Disable logging:

  • For Network Appliance NAS, type the following to disable ndmpd debug logging:  ndmpd debug 0
  • EMC Celerra, see the disable commands in TECH150646.
  • For other NAS devices, see the vendor documentation.

7. Retrieve the bpbrm, bptm, ndmpagent logs from the NetBackup media server for today's date. 

8. Do one of the following to retrieve logs from the NAS device:

  • Pull the datamover server_log from the EMC Celerra:  server_log server_2 -a -s > /output.file  (assumes ‘server_2’ is the datamover name)
  • Pull the system log and the ndmpdlog from the Network Appliance NAS:
    • /vol/etc/messages
    • <volume>/etc/log/ndmpdlog (/vol/etc/log/mlog in DataOnTap 8)

9. Type the commands on the media server to disable logging:

For Windows media server:

<install path>\NetBackup\bin\vxlogcfg -a -p 51216 -o 134 -s DebugLevel=0
<install path>\NetBackup\bin\vxlogcfg -a -p 51216 -o 151 -s DebugLevel=0
<install path>\NetBackup\bin\vxlogcfg -a -p 51216 -o 134 -s DiagnosticLevel=0
<install path>\NetBackup\bin\vxlogcfg -a -p 51216 -o 151 -s DiagnosticLevel=0

For Unix media server:

/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 134 -s DebugLevel=0
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 151 -s DebugLevel=0
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 134 -s DiagnosticLevel=0
/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 151 -s DiagnosticLevel=0

10. Create a temp directory.
 For example: C:\temp\vxul or /tmp/vxul

11. Run the following command to retrieve all unified logs for today's date:

For Windows media server: <install path>\NetBackup\bin\vxlogmgr -c -t 1 -f c:\temp\vxul

For Unix meda server: /usr/openv/netbackup/bin/vxlogmgr -c -t 1 -f /tmp/vxul

Where the '-t 1' value will retrieve the unified logs from the last hour.  Adjust the value as appropriate to go back past the beginning of the job.

12. Compress the temp directory (Zip for Windows, tar for Unix) and send to Symantec NetBackup Support along with the legacy logs and the NAS logs.

13. To create a long listing of the policy, run the following comand on the NetBackup master server: 

Windows master server: <install path>\NetBackup\bin\admincmd\bppllist <name of policy> -L

Unix master server: /usr/openv/netbackup/bin/admincmd/bppllist <name of policy> -L

14. On the media server, on the command line, run the nbsu tool as follows to create the output file:

Windows media server: 

  • In a command window, change the directory to <install path>\NetBackup\bin\support
  •  Type the following command:  nbsu -c -t -nozip

Unix media server: 

  • Type the following command: /usr/openv/netbackup/bin/support/nbsu -c -t

The script will create an output file and tell you where it was stored.

15. Cut and paste the Job Details for the job in the Activity Monitor during the backup attempt.  Send that to Symantec Support along with the nbsu output file and the bppllist output.

Related Articles:

 

 

BE 2012 und MS Windows 2012

0
0

Hallo! Wir sind gerade dabei einen Windows Server 2012 Std. in Betrieb zu nehmen. Bisher haben wir eine ältere Version von BE zur Sicherung im Einsatz und wollten nun auf die Version 2012 wechseln. Dabei mussten wir feststellen, das scheinbar keine Unterstützung von Server 2012 vorhanden ist. Gibt es inzwischen eine Lösung? Ansonsten müssen wir uns von Backeup Exec trennen, was wir eigentlich wollten.

Netbackup 7.5 - VMware Options short explained

0
0

Here is a short information about the Option available in Netbackup for VMware.

VMware Credentials in Netbackup:

  1. Click Media and Device Management > Credentials > Virtual Machine Servers.
  2. Click Actions > New > New Virtual Machine Server.
  3. On the Add Virtual Machine Server dialog, enter the name of a virtual machine server (vCenter server or ESX server).

Note: The credentials for ESX or vSphere client are needed that Netbackup can create and access the virtual machine Snapshots.

VMware backup host

  • Backup Media Server: This option allows a Windows media server that is selected in the policy to operate as the backup host. (Selection of the media server is determined by the specified storage unit.) To operate as the backup host, the Windows media server must contain NetBackup client software.
    Note: The storage unit that is specified in the policy must be unique to your Windows media servers. If the storage unit is also available on a UNIX media server, the snapshot cannot succeed.
    Note: When the Backup Media Server option is selected, NetBackup cannot determine a host to perform policy validation. To validate the policy, temporarily select one of the possible media servers as the backup host (do not select Backup Media Server). When the policy validates successfully, reset the backup host to Backup Media Server.
  • backup_host_name: Select a particular backup host to perform the backup.
    Note: The backup hosts (but not backup media servers) must be identified in the Administration Console as follows: Go to Host Properties > Master servers > double-click the master server > Master Server Properties > VMware Access Hosts.

Enable file recovery from VM backup

  • Enable recovery of individual files.
  • all the files inside the virtual machines can be restored in the virtual machine or 2 different location
  • still the full VM can be restored to the ESX / vSphere server

Enable block-level incremental backup

  • For block-level backups of the virtual machine. This option reduces the size of the backup image.

Exclude deleted blocks

  • Reduces the size of the backup image by excluding any unused or deleted blocks within the file system on the virtual machine. This option supports the following file systems: Windows NTFS, and Linux ext2, ext3, and ext4.
  • This option uses proprietary mapping technology to identify vacant sectors (allocated but empty) within the file system.
    To back up a virtual machine that contains Veritas Storage Foundation Volume Manager volumes, disable this option. Also make sure that the Enable file recovery from VM backup option is disabled.

Exclude swapping and paging files

  • Reduces the size of the backup image by excluding the data in the guest OS system paging file (Windows) or the swap file (Linux).
  • Note: This option does not exclude the swapping and paging files from the backup: it only excludes the data in those files. If the files are restored, they are restored as empty files

Primary VM Identifier

  • VM hostname:  The network host name for the virtual machine. (This option is the default.) NetBackup obtains the host name by means of a reverse lookup on the virtual machine's IP address. If no host name can be found, the IP address is used as the host name.
  • VMware display name: The name of the virtual machine as displayed in the VMware interface. A display name is assigned to the virtual machine when the virtual machine is created. When virtual machines are included in a NetBackup policy, restrictions apply to the characters that are allowed in the virtual machine display name. Note: The restrictions also apply to other vSphere objects, such as floppy image name, parallel port or serial port file name, and CD-ROM ISO name. Each display name must be unique in your VMware environment.
  • VMware BIOS UUID: The ID assigned to the virtual machine when the virtual machine is created. This ID may or may not be unique, depending on whether the virtual machine has been duplicated. This option is included for compatibility with the existing policies that use the older VM UUID identifier.
  • VM DNS Name: The VMware DNS Name of the virtual machine. In vSphere Client, this name appears on the virtual machine's Summary tab.
    Note: This name may or may not be associated with the virtual machine's IP address. VMware Tools obtains this name from the host name that is configured in the virtual machine. For further information on this name, refer to the documentation for the guest operating system.
  • VM instance UUID: The globally unique ID assigned to the virtual machine when the virtual machine is created. This ID uniquely identifies the virtual machine within a vCenter server. Even if the virtual machine has been duplicated (such as within a vCloud), only the original virtual machine retains this instance ID. (The virtual machine duplicates are assigned different instance UUIDs.) This option applies only to backup hosts (NetBackup clients) at 7.5 or later. If your backup host is 7.5 or later, this option is recommended instead of the VMware BIOS UUID option.
    Note: VM instance UUIDs are not available for standalone ESX 3.5 or ESXi 3.5 servers or for servers that VirtualCenter 2.5 manages.

 Orphaned Snapshot Handling

  • Ignore: NetBackup ignores any existing virtual machine snapshots (including snapshots previously created by NetBackup) and proceeds with snapshot creation and the backup.
  • Abort: If any snapshot exists on the virtual machine, NetBackup aborts the job for that virtual machine only.
  • Remove NBU: If a virtual machine snapshot exists that a NetBackup backup previously created: NetBackup removes the old snapshot, creates an updated snapshot, and proceeds with the virtual machine backup. (This option is the default.)

Enable Exchange Recovery

  • This option enables recovery of the Exchange databases or mailbox messages from the virtual machine backups. If this option is disabled, you can recover the entire virtual machine from the backup, but you cannot recover the databases or mailbox messages individually.

Enable SQL Server Recovery

  • This option enables recovery of individual files from Microsoft SQL data in the virtual machine backup. If this option is disabled, you can recover the entire virtual machine from the backup, but you cannot recover the SQL files individually.

Enable SharePoint Recovery

  • This option enables recovery of SharePoint objects from the virtual machine backup. If this option is disabled, you can recover the entire virtual machine from the backup, but you cannot recover the SharePoint objects individually.

For Exchange, SQL and Sharepoint Recovery are the following notes:

To use the Enable SharePoint Recovery option, note:

  • The Enable file recovery from VM backup option must be enabled.
  • The Enable block-level incremental backup option must be disabled.

Transport Modes

  • san: For unencrypted transfer over Fibre Channel (SAN) or iSCSI.
  • hotadd: Lets you run the VMware backup host in a virtual machine. This feature requires ESX 3.5 Update2 or later.For instructions on this transport mode and on installing the backup host in a VMware virtual machine, refer to your VMware documentation.
  • nbd: For unencrypted transfer over a local network that uses the Network Block Device (NBD) driver protocol. This mode of transfer is usually slower than Fibre Channel.
  • nbdssl: For encrypted transfer (SSL) over a local network that uses the Network Block Device (NBD) driver protocol. This mode of transfer is usually slower than Fibre Channel.
  • Move Up, Move Down: Use these buttons to change the order in which NetBackup tries each selected mode. Highlight a mode and click Move Up or Move Down.For example: assume that all four transport modes are selected, and the order is san, hotadd, nbd, and nbdssl. If one of the virtual disks cannot be accessed using san, the san transport mode is not used for any of the virtual machine's disks. NetBackup then tries to use the hotadd mode for all the disks. NetBackup continues to try each mode until it finds one that succeeds for all the disks.

"Media In Use" when running a restore

0
0

Assumptions:
NetBackup 7+, Unix master server

Intro:
If you are restoring a file recently written to tape, there's a fair chance that the tape will still be in use.
If the restore job is time-sensitive (and, really aren't they all?) here is a procedure I've tried to release
the tape (at the expense of killing the jobs that were writing to it).
I'll refer to the tape mediaID as "<mediaID>", replace this with the ID of your media - say AH0101.

 

  1. From master server – suspend ALL scheduling  
    master#   /usr/openv/netbackup/bin/admincmd/nbpemreq -suspend_scheduling

 

  1. Dump the current job that is using that media
    master# /usr/openv/netbackup/bin/admincmd/nbrbutil  -listActiveMediaJobs <MediaId>

    If that fails, you can try an older invocation
    master# /usr/openv/netbackup/bin/admincmd/nbrbutil -dump | grep <MediaID>  | sed 's/.*firstuserid//;s/(Media_Drive_Allocation_Record.*//' | grep jobid

     

  2. Try  /usr/openv/netbackup/bin/admincmd/nbrbutil   -releaseMedia   <MediaID>

    Else cancel the jobs that are using it. 
     master#  bpdbjobs -cancel 397341,23422,43224  (sample unix process IDs)
     

  3. Wait five minutes until the jobs are done.
     
  4. Suspend the tape so that other jobs don’t grab it and start writing to it.
     master#  bpmedia –suspend   -m <MediaID> -h  auspcrpbak01  –v
      (only needed on the media server that had grabbed the allocation of that media. Exit status = 0 )

 

  1. Resume scheduling jobs to the media server
     master#  /usr/openv/netbackup/bin/admincmd/nbpemreq -suspend_scheduling
     
  2. Resume the restore job. Restore jobs will still use suspended media.
     
  3. Once the restore completes, unsuspend the media  <MediaID>.  But if we forget to do this, the tape will be recycled into the pool once data on it expires.

 

Accelerator backup of Windows Cluster systems

0
0

So you have a Windows clustered file server, and want to use Accelerator.....but what about Windows Change Journals and NetBackup Track files?

  • Windows Change Journals follow the file system, so what happens when it’s moved to the new node?
  • NetBackup Track files are put on the local file system (c:\Program Files….).

Did some trial-and-error and found the following solution, I have performed several tests and have not found anything wrong with it:

  1. Add all physical nodes to a policy which backs up C:\ and System State.
     
  2. Enable Change Journal in Host Properties for the client.
     
  3. Create a NetBackup Policy for the cluster file system.
    Attributes: Enable Accelerator, Target must be MSDP (or other supported)
    Client: Virtual hostname for the file system
    Backup Selection: T:\ (or whatever the file system is mounted as on the cluster nodes)
     
  4. Run a manual first backup of the file system with “Accelerator Forced Rescan” schedule.
    Verify the track log is generated on client in:
    C:\Program Files\VERITAS\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>\<backup selection>\track_journal.v?.dat”

    Verify change journal is enabled:
    fsutil usn queryjournal t:
     

  5. Create a directory on the shared file system drive:
    T:\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>
    Move the content of:
    C:\Program Files\VERITAS\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>\
    to
    T:\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>

    Then link to the shared path:
    mklink /D “C:\Program Files\VERITAS\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>” “T:\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>”

    Verify the link works using cd in CLI or explorer.

    Run an incremental backup and verify that it works:
    03-09-2013 16:14:38 - Info bpbkar(pid=5272) change journal enabled for <T:\>       
    03-09-2013 16:14:39 - Info bpbkar(pid=5272) using change journal data for <T:\>

     

  6. Failover the cluster service to next cluster node and perform the following actions:
    Create the directory structure in local file system:
    mkdir C:\Program Files\VERITAS\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\

    Then create the same link here:
    mklink /D “C:\Program Files\VERITAS\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>” “T:\NetBackup\track\<master server hostname>\<media server hostname>\<cluster node>\<policy name>”

    Verify the link works using cd in CLI or explorer.

    Open the cluster policy and close it again (the policy verification seems to sometimes contact the client and “let NBU client know that there is Change Journal enabled for this file system).
    Restart the “NetBackup Client Service” on the node (this is not always necessary but better to be safe than sorry J ).

    Run an incremental backup. First time it returns with this messages, I think its because Windows has lost track of the USN count when the file system was moved):
    03-09-2013 16:19:53 - Info bpbkar(pid=3676) change journal enabled for <T:\>       
    03-09-2013 16:19:53 - Info bpbkar(pid=3676) NOT using change journal data for <T:\>: unable to locate journal data

    Rerun the incremental and 2nd attempt should state OK:
    03-09-2013 16:27:37 - Info bpbkar(pid=4788) change journal enabled for <T:\>       
    03-09-2013 16:27:38 - Info bpbkar(pid=4788) using change journal data for <T:\>

    Repeat this section for each cluster node.
     

  7. Configure the master server alternate restore permissions. On the master server update the file(s):
    …\Veritas\NetBackup\db\altnames\<physical cluster node name>
    and insert the virtual cluster node name(s) on a separate line.

 

Results:

So what’s the point if it loses track after failover anyway?

I used 133.000 files, 34.000 folders, 23Gb data for the test.

 

“server1” active, first full backup already done, no real change to files.

03-09-2013 16:14:38 - Info bpbkar(pid=5272) change journal enabled for <T:\>       

03-09-2013 16:14:39 - Info bpbkar(pid=5272) using change journal data for <T:\>      

03-09-2013 16:15:04 - Info bpbkar(pid=5272) accelerator sent 70023680 bytes out of 249973760 bytes to server, optimization 72.0%

03-09-2013 16:15:04 - Info bptm(pid=32083) waited for full buffer 6 times, delayed 1988 times   

03-09-2013 16:15:13 - Info bptm(pid=32083) EXITING with status 0 <----------       

03-09-2013 16:15:13 - Info dkaarnbume01(pid=32083) StorageServer=PureDisk:dkaarnbume01; Report=PDDO Stats for (dkaarnbume01): scanned: 244142 KB, CR sent: 15348 KB, CR sent over FC: 0 KB, dedup: 93.7%

1:35 minutes, Full Accelerator support....

 

Failed over the file service to “server2”, and ran the incremental:

03-09-2013 16:19:53 - Info bpbkar(pid=3676) change journal enabled for <T:\>       

03-09-2013 16:19:53 - Info bpbkar(pid=3676) NOT using change journal data for <T:\>: unable to locate journal data

03-09-2013 16:20:57 - Info bpbkar(pid=3676) 5000 entries sent to bpdbm       

03-09-2013 16:21:12 - Info bpbkar(pid=3676) 10000 entries sent to bpdbm       

03-09-2013 16:21:32 - Info bpbkar(pid=3676) 15000 entries sent to bpdbm       

03-09-2013 16:22:24 - Info bpbkar(pid=3676) 20000 entries sent to bpdbm       

03-09-2013 16:22:42 - Info bpbkar(pid=3676) 25000 entries sent to bpdbm       

03-09-2013 16:23:07 - Info bpbkar(pid=3676) 30000 entries sent to bpdbm       

03-09-2013 16:23:28 - Info bpbkar(pid=3676) accelerator sent 188777472 bytes out of 366990336 bytes to server, optimization 48.6%

03-09-2013 16:23:28 - Info bptm(pid=529) waited for full buffer 233 times, delayed 12480 times   

03-09-2013 16:23:38 - Info bptm(pid=529) EXITING with status 0 <----------       

03-09-2013 16:23:39 - Info dkaarnbume01(pid=529) StorageServer=PureDisk:dkaarnbume01; Report=PDDO Stats for (dkaarnbume01): scanned: 358418 KB, CR sent: 20429 KB, CR sent over FC: 0 KB, dedup: 94.3%

4:51 minutes. Yes it was slower, but notice that it only scanned approx. 30.000 entries, I believe this is because of the shared NetBackup Track file.

 

Second incremental on “server2”:

03-09-2013 16:27:37 - Info bpbkar(pid=4788) change journal enabled for <T:\>       

03-09-2013 16:27:38 - Info bpbkar(pid=4788) using change journal data for <T:\>      

03-09-2013 16:28:01 - Info bpbkar(pid=4788) accelerator sent 70024704 bytes out of 249974784 bytes to server, optimization 72.0%

03-09-2013 16:28:01 - Info bptm(pid=1808) waited for full buffer 9 times, delayed 991 times   

03-09-2013 16:28:09 - Info bptm(pid=1808) EXITING with status 0 <----------       

03-09-2013 16:28:09 - Info dkaarnbume01(pid=1808) StorageServer=PureDisk:dkaarnbume01; Report=PDDO Stats for (dkaarnbume01): scanned: 244143 KB, CR sent: 15429 KB, CR sent over FC: 0 KB, dedup: 93.7%

1:32 minutes, So it’s already working normally again.

 

Ran an full rescan backup on “server2” as a reference, which shows what the backup time would have been without any accelerator working:

03-09-2013 16:29:45 - Info bpbkar(pid=5824) change journal enabled for <T:\>       

03-09-2013 16:29:45 - Info bpbkar(pid=5824) NOT using change journal data for <T:\>: checksum validation requested  

03-09-2013 16:30:17 - Info bpbkar(pid=5824) 5000 entries sent to bpdbm       

03-09-2013 16:30:31 - Info bpbkar(pid=5824) 10000 entries sent to bpdbm       

--cut--

03-09-2013 16:41:18 - Info bpbkar(pid=5824) 160000 entries sent to bpdbm       

03-09-2013 16:41:44 - Info bpbkar(pid=5824) 165000 entries sent to bpdbm       

03-09-2013 16:42:13 - Info bpbkar(pid=5824) accelerator sent 797236224 bytes out of 24888171520 bytes to server, optimization 96.8%

03-09-2013 16:42:14 - Info bptm(pid=4467) waited for full buffer 1318 times, delayed 41120 times   

03-09-2013 16:42:49 - Info bptm(pid=4467) EXITING with status 0 <----------       

03-09-2013 16:42:49 - Info dkaarnbume01(pid=4467) StorageServer=PureDisk:dkaarnbume01; Report=PDDO Stats for (dkaarnbume01): scanned: 24309036 KB, CR sent: 54489 KB, CR sent over FC: 0 KB, dedup: 99.8%

14:01 minutes, It scanned all entries and ran for much longer period, like a normal backup.

Announcing the 3.10 Version of SORT - Now With NetBackup 7.6 Support

0
0

 The Symantec Operations Readiness Tools (SORT) team is pleased to announce that the new SORT 3.10 release includes support for the upcoming NetBackup 7.6 release.

The list below highlights the NetBackup-specific updates to SORT for this release:

General

  • Support for NetBackup 7.6!
  • Standardize OS and CPU architecture names across SORT for integration into the new Product and Platform Lookup widget
    https://sort.symantec.com/productmatrix/platform
  • Incorporate updates from changes to all NetBackup compatibility lists (Operating System (SCL) and associated features, Hardware (HCL), etc.)
  • Data collectors/custom reports and Installation & Upgrade Checklist
  • Incorporate updates for the Hot Fix / EEB Release Auditor

Installation and Upgrade Custom Report

  • Support for NetBackup 7.6
  • New checks and reporting for NetBackup 7.6 system requirements
  • New check and reporting of a remote/shared EMM server environment which is no longer supported in NetBackup 7.6
  • Inclusion of the latest NetBackup & OpsCenter hot fix information
  • Incorporates updates for the Hot Fix / EEB Release Auditor

Installation and Upgrade Checklist

  • Support for NetBackup 7.6
  • Created separate System Requirements section for Master and Media servers for better utilization of differing requirements
  • Update to the Master and Media Server System Requirements sections for NetBackup 7.6
  • Inclusion of the latest NetBackup, NetBackup Appliance and OpsCenter hot fix information
  • Support for the Windows Server 2012 platform as a Master Server
  • Support for the Ubuntu 13.04 platform
  • Support for Oracle Linux 5 and 6 as an OpsCenter Server platforms 

Visit SORT to see the value we provide to thousands of Symantec customers.


setting for synology backup symantec

Ältere Backups werden nich löscht/überschrieben

0
0

Hallo,

wir verwenden Symantec Backup Exec 2012 Version 14.0 1798.1244 (64 Bit), installierte Updates: Servicepack 2 / + Hotfix 209149

Folgende Sicherungkonfiguration: Sicherung auf B2D welche sich auf einem NAS befinden.
gesichert sollte jeden Tag werden, wobei die Sicherung nach einer Woche überschrieben werden sollte.
Unter den Einstellungen/Speicher ist unter Medienüberschreibstufe: Keine eingestellt

Aufbewahrungszeit bei Sicherungsauftrag: 1 Stunde

Doch leider werden am NAS die älteren Backupaufträge nicht überschrieben, bis das NAS voll ist und die Backups manuell gelöscht werden müssen.

gibt es noch eine Einstellung, wo man sagen muss, dass überschrieben werden soll?

danke für die Hilfe

 

Netbackup on Virtual infrastructure with VTLs

0
0

Hello Folks,

 

Please find the detailed technical documentation configuring Netbackup using Firestreamer and Starwind VTLs

A Newbie's Introduction to Backup Exec Pt. 2

0
0

It’s been a while since I last wrote an article, and almost a year since I wrote the first part of what was going to be a 2-part introduction to Backup Exec for newbies. Now’s as good a time as any to write it…

To recap, read the first part on the link below:

https://www-secure.symantec.com/connect/articles/newbies-introduction-backup-exec-pt-1

It ended off with budgets, implementation timelines, and decommissioning old software. This article will deal with types of hardware to use, virtual/physical media servers, and some of the technologies to look at:

 

  1. Backup Hardware to Use

Almost every hardware vendor (HP, IBM, EMC, NetApp) has either disk-based, or tape-based, or both, backup options. There has been a big push for disk being the primary backup target to completely replace tape, but tape is still a developing technology with LTO7 and LTo8 on the radar. So tape isn’t dead, and tape won’t be replaced anytime soon.

Disk-based backups have tremendous benefits, which would include more concurrent jobs to the array/NAS, holding more data more readily, and faster restores. However, arrays tend to be expensive.

Tape can backup TBs now with LTO5 and LTo6. However, it can’t do dedupe backups direct to tape for instance, while GRT-based backups to tape require staging (either manually or automatically) to disk. However, cost-wise they can be cheaper than an array.

Carefully consider the hardware you want to purchase, and don’t over-purchase. By this I mean don’t let someone trying to make a sale, sell you something you don’t need which inflates the costs; costs which can be spent elsewhere to maybe optimise your environment. If you have hardware that exists, and you’ve just taken this over, make sure you come to grips with how it works, how it all fits together, and how you can perhaps even improve your backup flow.

 

  1. Virtual or Physical Media Server?

BIG consideration here…there are a lot of queries on Connect around having a virtual media server, and Symantec’s position on this is clear: it’s considered an alternative configuration and, as such, is not supported. However, there are also some comments doing the rounds where it has been stated that some form of support might be given.

This was tried in an environment I looked after. 2 servers acting as ESX hosts with no shared storage. 1 host had the virtual media server with SCSI pass-through to an HP StorageWorks MSL2024 G3 tape library. This setup worked like a charm…until it glitched. Backup Exec would lose connectivity to the host. Troubleshooting revealed ESX lost connectivity to the library, and this ended up leading to a host reboot and unnecessary downtime. Even with shared storage, and using SCSI pass-through (which on later versions of ESX is no longer supported), the media server wouldn’t be able to migrate between hosts.

Using a virtual media server when backing up to disk is probably a better option, especially if this is simply presented from a datastore. It would save on costs as physical hardware would not be required.

When considering whether or not to go virtual, or stay physical, seriously consider the implications from a Symantec perspective…there’s nothing worse than not having support if you are in dire straits…

 

  1. Some of Backup Exec’s Technologies

Used to doing normal backups to disk or tape? What about deduplication? Used to manage multiple servers by connecting into each and every one of them? What about CASO (Enterprise Server Option if you’re using Backup Exec 2012)?

There are a number of options within Backup Exec that can be used to improve your environment, be it backup speeds, management or redundancy. Take the time to check out the various functionalities that BE can offer your environment. While this would lead to costs incurred, it could end up making your life easier.

 

Some other advice…play around with the software, especially if you are new, and when new versions get released, trial them first. Virtual platforms running on your desktop/workstation are able to run a Windows Server-based server on which you can install the trial software.

And lastly…any questions, come to Connect. There are lots of people here willing, and eager to help find answers!

TYPES OF STATUS CODES WITH SLIGHTLY DIFFERENT DEFINITIONS

0
0

Hi All,

 

I found very helpful list of NETBACKUP STATUS CODES with slightly different definitions.

http://senthil-it-infrastructure.blogspot.com/2012/07/netbackup-status-codes.html
 

NetBackup Status Codes

 
0 the requested operation was successfully completed
1 the requested operation was partially successful
2 none of the requested files were backed up
3 valid archive image produced, but no files deleted due to non-fatal problems
4 archive file removal failed
5 the restore failed to recover the requested files
6 the backup failed to back up the requested files
7 the archive failed to back up the requested files
8 unable to determine the status of rbak
9 an extension package is needed, but was not installed
10 allocation failed
11 system call failed
12 file open failed
13 file read failed
14 file write failed
15 file close failed
16 unimplemented feature
17 pipe open failed
18 pipe close failed
19 getservbyname failed
20 invalid command parameter
21 socket open failed
22 socket close failed
23 socket read failed
24 socket write failed
25 cannot connect on socket
26 client/server handshaking failed
27 child process killed by signal
28 failed trying to fork a process
29 failed trying to exec a command
30 could not get passwd information
31 could not set user id for process
32 could not set group id for process
33 failed while trying to send mail
34 failed waiting for child process
35 cannot make required directory
36 failed trying to allocate memory
37 operation requested by an invalid server
38 could not get group information
39 client name mismatch
40 network connection broken
41 network connection timed out
42 network read failed
43 unexpected message received
44 network write failed
45 request attempted on a non reserved port
46 server not allowed access
47 host is unreachable
48 client hostname could not be found
49 client did not start
50 client process aborted
51 timed out waiting for database information
52 timed out waiting for media manager to mount volume
53 backup restore manager failed to read the file list
54 timed out connecting to client
55 permission denied by client during rcmd
56 client's network is unreachable
57 client connection refused
58 can't connect to client
59 access to the client was not allowed
60 client cannot read the mount table
61 wbak was killed
62 wbak exited abnormally
63 process was killed by a signal
64 timed out waiting for the client backup to start
65 client timed out waiting for the continue message from the media manager
66 client backup failed to receive the CONTINUE BACKUP message
67 client backup failed to read the file list
68 client timed out waiting for the file list
69 invalid filelist specification
70 an entry in the filelist expanded to too many characters
71 none of the files in the file list exist
72 the client type is incorrect in the configuration database
73 bpstart_notify failed
74 client timed out waiting for bpstart_notify to complete
75 client timed out waiting for bpend_notify to complete
76 client timed out reading file
77 execution of the specified system command returned a nonzero status
78 afs/dfs command failed
79 unimplemented error code 79
80 Media Manager device daemon (ltid) is not active
81 Media Manager volume daemon (vmd) is not active
82 media manager killed by signal
83 media open error
84 media write error
85 media read error
86 media position error
87 media close error
88 Auspex SP/Backup failure
89 fatal error in Unitree file system
90 media manager received no data for backup image
91 fatal NB media database error
92 media manager detected image that was not in tar format
93 media manager found wrong tape in drive
94 cannot position to correct image
95 requested media id was not found in NB media database and/or MM volume database
96 unable to allocate new media for backup, storage unit has none available
97 requested media id is in use, cannot process request
98 error requesting media (tpreq)
99 NDMP backup failure
100 system error occurred while processing user command
101 failed opening mail pipe
102 failed closing mail pipe
103 error occurred during initialization, check configuration file
104 invalid file pathname
105 file pathname exceeds the maximum length allowed
106 invalid file pathname found, cannot process request
107 too many arguments specified
108 invalid date format specified
109 invalid date specified
110 Cannot find the NetBackup configuration information
111 No entry was found in the server list
112 no files specified in the file list
113 unimplemented error code 113
114 unimplemented error code 114
115 unimplemented error code 115
116 unimplemented error code 116
117 unimplemented error code 117
118 unimplemented error code 118
119 unimplemented error code 119
120 cannot find configuration database record for requested NB database backup
121 no media is defined for the requested NB database backup
122 specified device path does not exist
123 specified disk path is not a directory
124 NB database backup failed, a path was not found or is inaccessable
125 another NB database backup is already in progress
126 NB database backup header is too large, too many paths specified
127 specified media or path does not contain a valid NB database backup header
128 unimplemented error code 128
129 unimplemented error code 129
130 system error occurred
131 client is not validated to use the server
132 user is not validated to use the server from this client
133 invalid request
134 unable to process request because the server resources are busy
135 client is not validated to perform the requested operation
136 unimplemented error code 136
137 unimplemented error code 137
138 unimplemented error code 138
139 unimplemented error code 139
140 user id was not superuser
141 file path specified is not absolute
142 file does not exist
143 invalid command protocol
144 invalid command usage
145 daemon is already running
146 cannot get a bound socket
147 required or specified copy was not found
148 daemon fork failed
149 master server request failed
150 termination requested by administrator
151 Backup Exec operation failed
152 required value not set
153 server is not the master server
154 storage unit characteristics mismatched to request
155 unused b
156 unused f
157 unused d
158 failed accessing daemon lock file
159 licensed use has been exceeded
160 authentication failed
161 Evaluation software has expired. See www.veritas.com for ordering information
162 unimplemented error code 162
163 unimplemented error code 163
164 unable to mount media because its in a DOWN drive or misplaced
165 NB image database contains no image fragments for requested backup id/copy number
166 backups are not allowed to span media
167 cannot find requested volume pool in Media Manager volume database
168 cannot overwrite media, data on it is protected
169 media id is either expired or will exceed maximum mounts
170 unimplemented error code 170
171 media id must be 6 or less characters
172 cannot read media header, may not be NetBackup media or is corrupted
173 cannot read backup header, media may be corrupted
174 media manager - system error occurred
175 not all requested files were restored
176 cannot perform specified media import operation
177 could not deassign media due to Media Manager error
178 media id is not in NetBackup volume pool
179 density is incorrect for the media id
180 tar was successful
181 tar received an invalid argument
182 tar received an invalid file name
183 tar received an invalid archive
184 tar had an unexpected error
185 tar did not find all the files to be restored
186 tar received no data
187 unimplemented error code 187
188 unimplemented error code 188
189 the server is not allowed to write to the client's filesystems
190 found no images or media matching the selection criteria
191 no images were successfully processed
192 unimplemented error code 192
193 unimplemented error code 193
194 the maximum number of jobs per client is set to 0
195 client backup was not attempted
196 client backup was not attempted because backup window closed
197 the specified schedule does not exist in the specified class
198 no active classes contain schedules of the requested type for this client
199 operation not allowed during this time period
200 scheduler found no backups due to run
201 handshaking failed with server backup restore manager
202 timed out connecting to server backup restore manager
203 server backup restore manager's network is unreachable
204 connection refused by server backup restore manager
205 cannot connect to server backup restore manager
206 access to server backup restore manager denied
207 error obtaining date of last backup for client
208 failed reading user directed filelist
209 error creating or getting message queue
210 error receiving information on message queue
211 scheduler child killed by signal
212 error sending information on message queue
213 no storage units available for use
214 regular bpsched is already running
215 failed reading global config database information
216 failed reading retention database information
217 failed reading storage unit database information
218 failed reading class database information
219 the required storage unit is unavailable
220 database system error
221 continue
222 done
223 an invalid entry was encountered
224 there was a conflicting specification
225 text exceeded allowed length
226 the entity already exists
227 no entity was found
228 unable to process request
229 events out of sequence - image inconsistency
230 the specified class does not exist in the configuration database
231 schedule windows overlap
232 a protocol error has occurred
233 premature eof encountered
234 communication interrupted
235 inadequate buffer space
236 the specified client does not exist in an active class within the configuration database
237 the specified schedule does not exist in an active class in the configuration database
238 the database contains conflicting or erroneous entries
239 the specified client does not exist in the specified class
240 no schedules of the correct type exist in this class
241 the specified schedule is the wrong type for this request
242 operation would cause an illegal duplication
243 the client is not in the configuration
244 main bpsched is already running
245 the specified class is not of the correct client type
246 no active classes in the configuration database are of the correct client type
247 the specified class is not active
248 there are no active classes in the configuration database
249 the file list is incomplete
250 the image was not created with TIR information
251 the tir information is zero length
252 unused TIR error 2
253 unused TIR error 1
254 server name not found in the bp.conf file
255 unimplemented error code 255
 
 
 

 

 
 

Netbackup Forum 2013

Backup Exec 2012 Hyper V /VMware Application GRT demystified.

0
0

Backup Exec 2012 Hyper V /VMware Application GRT demystified.

Before we move ahead to understand how Virtual Application GRT works, let me give a short description on How application GRT Works.

In general when an application (exchange, AD, SharePoint) server is backed up with GRT enabled, there are two distinct phases of the backup.

1.            Data moved from application server to the Backup Exec media server

2.            Data is cracked open and analyzed for content, the same is being recorded and and saved in the catalogs.(In a layman’s term)

When the target media is disk storage, the data moves from the application server (The server which is being backed up.) to an IMG folder on the media server, data on the media server is cracked open and analyzed for content to build the catalogs.

 

Whereas when the target media is tape device, the data moves from the application server to the tape.  , the data residing in snapshot on the application server is cracked open and analyzed for content.

 

For example, the backup of an Exchange server would result in an IMG folder containing files similar to those listed below. 

 

You can see the Exchange LOG files and the EDB file.  Also note, the PDI.TXT and PDI_STRM.BIN files , these two files contain information about the structure of the Exchange Info-Store, for example, where the files are located on the Exchange server, the various file permissions, etc…

 

There is an IMG folder created for each application entity that is backed up.  For example, there would be an IMG folder for each Exchange Info-Store, one for each instance of SQL for AppGRT, one for Active Directory and one for each SharePoint item (ie: DLE), provided that item supports GRT.

Application GRT Backup, with Virtualization.(using VMware or Hyper-V):

Now talking about the Virtual agent backup process, a virtual agent like VMware /Hyper-V must drive the application agent like SQL Agent, Exchange Agent, and Active Directory Recovery Agent (ADRO) etc. through its phases to build its GRT view.

In order to gather all of the META DATA (necessary application information and status from the virtual machine), following conditions needs to be fulfilled.

  • Remote agent of the identical version of Backup Exec must be installed and running on it.
  • All of the application’s services must be up and running. 

The virtual backup must drive the application agent through its phase of META DATA collection before the VHD / VMDK are transferred to the media server. 

The backup process goes through the following steps, before the snapshot of the Virtual machine is taken.

  • .            Establish a connection from the media server(bengine) to the Backup Exec Remote Agent (beremote) running inside of the guest Virtual machine, selected to be backed up.
  • .            Logon to the guest with the provided credentials.
  • .            Request the Backup Exec Remote Agent running inside the Guest Virtual Machine to :

a.            take the snapshot of the necessary guest drives using the available VSS framework.

b.            Drive each application agent through a pseudo Backup, so that only Meta data of the backup is collected required for the GRT Process.

c.            Delete the snapshot of the Guest Machine Drives.

  • .            Return status information to the Backup Exec Media Server.

The process discussed above takes place much before the snapshot of the virtual machine is taken by the respective virtual agent.(VMware or Hyper-V).

And the UI displays “Preprocessing” during this stage of the virtual backup. 

During this phase, a small amount of data is generated and is stored inside the guest virtual machine.

Thus when the VHD / VMDK files are transferred to the media server, this data is transferred as well. 

And it also provides additional advantage that this data is always kept in synch with the application’s data stored inside of the VHD / VMDK files. 

This data is stored in the LOGS directory inside the guest and is deleted from the gust machine after a successful snapshot.

Phase 2:

The credentials used to logon to the guest are set for the VM resource under the virtual host. 

It is not possible to set application specific credentials. 

In other words, if you have an SQL instance that uses SQL authentication or if the application implements access permissions such that the user is unable to access the application, you will be unable to perform Virt-App GRT for the application. 

If all of four of the application GRT options are disabled (ie: unchecked) the entire metadata collection process is skipped. 

Disabling an application GRT option means that application will be silently skipped during the metadata collection process inside of the guest.

Note:

 The entire metadata process is silently skipped if the VM is powered off.

Once the VHD / VMDK files have been transferred to the media server, GRT processing begins.  GRT processing in this context means   file and folder GRT processing as well as Virt-App GRT processing.

In order to perform any sort of GRT processing, the VHD / VMDK files must be mounted so that they can be scanned for content and have that content added to the catalogs.

For VMware, the VMDKs are always mounted on the ESX server.(data store.)

For Hyper-V, the VHDs that are mounted for GRT operations depend on the target media.(Tape or disk.)

 If the target is disk, the VHDs that are mounted are the VHDs that reside on the media server. 

If the target is tape, the VHDs that are mounted are the VHDs that reside in the snapshot on the Hyper-V host.

Once the VHD / VMDK files are mounted, following things are done:

  • Registry information on the mounted guest are queried for the drive identification, (e.g assigned drive letter, boot records and so on)
  • After the VHD / VMDK files are mounted and the driver letter mapping determined, the “guest” volumes appear as “local” volumes.  So for file and folder GRT, the NTFS doesn’t actually backup any data, the only thing that happens for the “guest” volumes is that every file in the VHD / VMDK gets “cataloged” under the drive letter used by the guest.
  • Once file and folder GRT is completed, Virt-App GRT processing is started.
  • So processing starts with application discovery. 
  • PDI.TXT and PDI_STRM.BIN files inside the VHD / VMDK (These were created during the phase 1, as discussed above.) are opened and analyzed, the locations of the files inside of the VHD / VMDK files are recorded to be used while creating the soft links.
  •  In this case the links are Windows symbolic links, but depending on the Operating System and virtualization type (ie: Hyper-V vs. VMware) the links might be VLINK generated by VFF.
  • The application agent catalogs everything In other words, regardless of what the application agent supports for restore browse, all of the data in the restore browse view is coming out of the catalogs.

Once this phase is completed, the normal VERIFY job is executed and the status is updated in the database.

  • With regards to restores, the VHD / VMDK files are mounted, but not all of the VHD / VMDK files may need to be mounted.  If the VM has 2 VHD / VMDK files and the “item” to be restore  is in the first VHD / VMDK, then only the first VHD / VMDK is mounted.

Kind Regards,

S

 


Solution-Robots with missing path (nbu 7.5.0.6)

opscenter Data Collection Issue--Solution

0
0

OpsCenter  Ver 7.5.0.3

(No data in reports error fixed summary)

 

 

 

 

Phase 1

 

 

àFroze the cluster and stopped Ops center.

 

àBacked up database

   D:\program files\symantec\opscenter\bin> dbbackup

 

àBacked up the opscenterserversrv.xml file

 

àChanged "-Xmx " from 4096M to 6144M (from 4GB to 6GB) in opscenterserversrv.xml file

 

 

àSimplified the database server startup and corrected a type (of the extra -m)

   File: Server_db_conf_server.conf

 

 

From

 

-n Opscenter_usclusrpt01 -x tcpip(LocalOnly=YES;ServerPort=13786) -gd DBA -gk DBA -gl DBA –gp

 4096 -ti 0 -c 8G -ch 20G  -cl 4G -zl -os 1M -m -o

"D;\Program Files\symantec\Opscenter\server\db\log\server.log" -m

 

To

 

-n Opscenter_usclusrpt01 -x tcpip(LocalOnly=YES;ServerPort=13786) -gd DBA -gk DBA -gl DBA -gp

4096 -ti 0 -c  20G  -cs -os 1M -m -o

"D;\Program Files\symantec\Opscenter\server\db\log\server.log"

 

Increased Database memory from 8GB to 20GB (Total physical Memory 32GB)

2GB for GUI

 

 

 

 

 

 

Phase 2

 

àRemoved VMware access hosts name usvhildcms02 from master server

 

 

àIncreased client timeout from 10 mins to 1 hour,

    by adding below line in /opt/SYMCOpsCenter/config

             Nbu.scl.requestTimeoutlnMillis=3600000

Opscenter\Server\config\scl.conf

 

 

 

 

 

àRestarted Opscenter

   D:\program files\symantec\opscenter\bin> Opsadmin stop

   D:\program files\symantec\opscenter\bin> Opsadmin start

 

 

àOpscenter web GUI

         Settings à configuration à usvhvoilms001 à Data Collection Disable

                                                                                 à Data Collection Enable

                                                                                  

 

    

àCurrently working on replicate the same settings over to the configuration on the inactive node “usnjnbrpt01”

    After that I will unfreeze the cluster.

 

 

Phase 3

 

Appliance Hardware Data collection Error ---fixed

 

After reviewing logs from master server and Opscenter, data collection on appliance hardware is failing because an invalid appliance hostname “nb-appliance” was added in the appliance media server list

-------------------------------------------------------------------

$ nbemmcmd -listhosts         

NBEMMCMD, Version:7.1

The following hosts were found:

 

media              nb-appliance

---------------------------------------------------------------------

 

$ vmoprcmd -devmon hs   | grep nb-appliance                                                                                    

 

                           HOST STATUS

Host Name                                  Version   Host Status

=========================================  =======   ===========

nb-appliance                               710700    DEACTIVATED

----------------------------------------------------------------------

 

 

We try deactivating but still opscenter trying to get hardware information from master server for the appliance media server “nb-appliance”

 

After confirming from Mila/Cleveland

I deleted the media sever hostname “nb-appliance” with command

 

nbemmcmd –deletehost –machinename nb-appliance –machinetype media

 

 

After deleting, Data collection on appliance hardware is success.

 

 

Backup exec error.

Disk Storage Replication Report

0
0

Please find the Screenshot attached.

Replication Report or Summary

Based on my experience I have inputted the 3 options to generate total Data Replication report

Option: 1

-->login to Datadomain web GUI http://<storagename> press enter

-->Click on Storage Server

--> Click on Replication

-->if DDboost, Click on DDboost

-->Click on File Replication

-->select the Duration

--> there you can find the total Replication size in 24 hrs

 

 

Option: 2

-->login to Datadomain web GUI http://<storagename> press enter

-->On left bottom, click on report,

--> Select replicationSummary --> select duration --> click on create

 

 

Option: 3 opscenter

-->Click on Report

-->Click on New Custom Report

 

  • Select Ranking

 

àSelect Duration

àSelect Master server if any in particular

àUnder Disk please select Storage server name or Disk Volume name if you looking for any specific

 

Select Report on: “Disk Volume Name” or Storage Server Name

y-axis Display name

Select Report Data: “Disk Volume Replication “

Select Count

Select time basis as “Job End Time”

Click on Next

 

After clicking next you will get the report based on Disk volume name and Disk Replication Count in form on Ranking

 

 

 

 

Click next to save

 

 

 

After Save, open report and click on “show chart as Table”

A table will pop up with all values

 

 

Sharepoint backup fails with error

0
0

V-79-57344-33967 - Snapshot Technology: Initialization failure on: "Search instance\Search-DB 1 (Sharepoint\WSS_Search_Sharepoint)". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE00084AF): The directory or file was not found, or could not be accessed. Check the Windows Event Viewer for details.

Job log.JPG

Windows Event Viewer information

Event ID : 8193
Source : VSS
Error : ConvertStringSidToSid(S-1-5-80-1202657632-534270475-2053275915-3193571600-3895445954.bak), 0x80070539, The security ID structure is invalid.
 

Event ID.JPG

 

Cause
Invalid security ID structure

 

Solution

1)Open regedit on remote server

2)Navigate to HKLM\Software\Microsoft\Windows NT\Current Version\Profile List

3)Right click on Profile list and click Export to take a backup of the registry and save it

4)Look for the invalid SID that is listed in the event viewer (S-1-5-80-1202657632-534270475-2053275915-3193571600-3895445954.bak) and delete it.

SID.JPG

5)Restart the remote server and run the backup again.
 

Viewing all 240 articles
Browse latest View live




Latest Images