Sebastian,

Hello.  Version A.09.00, internal build 88

Best regards,

Don

You should consider upgrading to A.09.07. There where some runtime issues in the AppServer causing the directory to grow over time. It this works ok, please mark this topic as resolved and assigning a Kudo.

Regards,
Sebastian Koehler

thank you Sebastian. 

Works now.

I increased the inactivity timeout from 8400 seconds to 16800 and also ensured the following options were set:

"display statistical information" is unticked

"Do not preserve access time attributes"

set logging to log files

Thank you very much. 

Don't use Log Files! There is currently a restore issue with the logging options Log Files and Log Dir. Please use Log All or No Log instead.

If you find our assistance useful, please don't forget to assign Kudos.

Regards,
Sebastian Koehler

Hi,

I see that this is related to source device selection in case the sources are tagged and policies for copy/restore are in place. Have there been changes to more basic device locking in 9.0x? I'm asking because, in a DP installation upgraded from 8.12 to 9.06 a month ago, I'm seeing some chains of backup and copy taking days longer than they used to take before. Investigating, I've found:

• A copy session waiting with [64:18] despite both the source and destination drive not being in use (no active session is either reading or writing to any of the drives);
• The destination drive of said session claimed to be "Already in use" from the source drive view of copy specs;
• Trying to scan a medium using that drive fails telling me it's already in use by someone else, even though it's idle;
• The drive in question being on the lock list of omnidbutil -show_locked_devs
• The PID of the lock pointing to a CSM of a copy session which is currently queued to write to this drive, but is waiting too because its source drive, in turn, is truly in use by someone else.

So what it comes down to is a session that is not running but just qeueing holds a lock on the drive in question, so no other session that could run (because its source drive is available) is allowed to start writing there. I think that's wrong, and that's new behavior after the upgrade (hard to say now just from session logs, though). I was pleased that DP 9.06 scheduling of backups and copies to devices seemed to be way more deterministic than earlier versions, where any session could grab a device that just got free, with a tendency for older sessions to starve for days and maybe even run into a timeout even though the latter was bumped up to 7 days already. Now I realize the determinism of the old jobs getting done mostly in sequence before the newer ones might just have been a result of the oldest job in town locking its destination drive so noone else could run earlier - with the side effect of locking out sessions with different source devices as well.

Are these issues related? Am I missing something (as ususal)?

TIA,
Andre.

---

tabrez16 wrote:

I want to do purge and readdb and write DB.

---

Why? Cargo cult?

The whole raison d'être for the IDB change between 7.0 and 8.0 was to get rid of the very reasons that made this procedure necessary before. The old IDB had a file name part that managed to reduce the total space necessary for storing every single path name in all of the backups, mainly by having every unique name stored just once and optimized further by chopping them up into path components of various lenghts. The disadvantage was that environments with a large influx of new (never seen before) path names and - as a result - a large rate of path names getting obsoleted when backups expired, would accrete a pile of filename junk in that part of the IDB. So much you had to regularly purge it. And that alone would only make things worse, as the resulting comb of a fragmented DB table, when filled again from the beginning, would turn into a tragic source of random read access on every following IDB check or backup, with times required for these operations exploding into multiple hours. So to get rid of the fragmentation caused by purge, you had to dump and restore the IDB in place, as this would compact it down to the remaining filename entries and make it more linear access, specifically when it started to grow again.

Now all this is thankfully gone. The PostgreSQL part is just the client, object, session, device and media metadata and even with vast numbers of media, it is of a trivial size and doesn't need any significant maintenance. The filenames are now part of the DCBFs which has one drawback: They are now much larger. There is no more filename deduplication as we had it before. But this also means that filenames are coming (with backups) and going (with recycling of expired media) fully automatically as DCBFs are coming and going. There is no more explicit maintenance here, it's implicit in the DCBF lifecycle. A classic time-space-tradeoff in the end. And we're speaking of human time here, given how long a purge/writedb/readdb maintenance operation could take and occupy my full attention (lest I wreck the entire installation with a wrong spell). Now we have something else to find to do with this time. Luckily, there's enough other issues in DP8/9 to waste it with ;)

HTH,
Andre.

Hi sebastian,

Our concerning VM’s Hardware version is 10. During full backup we also get these two alerts: [Warning] From: VEPALIB_VMWARE@dse-backup.dftp.com "/DSE DC" Time: 7/15/2016 12:00:32 AM [172:390] Virtual Machine 'ProdZabbix': User Snapshot(s) found. Changed Block Tracking cannot be enabled. [Warning] From: VEPALIB_VMWARE@dse-backup.dftp.com "/DSE DC" Time: 7/15/2016 12:00:32 AM Virtual Machine 'ProdZabbix': Changed Block Tracking will not be used.

Hi Sebastian,

I have checked properly but don't identified any error.

Please response to me ASAP.

Most likely the VM has a very old VMware snapshot attached that must be removed first. From vCenter delete all snapshots attached to the VM and retry backup afterwards.

Regards,
Sebastian Koehler

Please check the attachment.

 no. 1 screenshot is before delete.

and no. 2 screenshot is after delete.

still we have 1 snapshot.

Seems the VM is running from this snapshot. Have you used the Delete All function in the Snapshot manager?

Regards,
Sebastian Koehler

Hi team,

all backups are completing with completed/errors.but we are geting below errors can you please help me on this error

kindly fins the below section logs.

[Normal] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:00:05 PM
 Backup session 2016/07/16-14 started.

[Normal] From: BMA@uscarbku01.us.oup.com "HP:Ultrium 5-SCSI_1_usbku01"  Time: 7/16/2016 2:00:07 PM
 STARTING Media Agent "HP:Ultrium 5-SCSI_1_usbku01"

[Normal] From: BMA@uscarbku01.us.oup.com "HP:Ultrium 5-SCSI_1_usbku01"  Time: 7/16/2016 2:00:10 PM
 => UMA@uscarbku01.us.oup.com@Changer0:0:4:1
 Loading medium from slot 4 to device Tape0:0:4:0C

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:01:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:01:45 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:01:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:01:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/CONFIGURATION]"  Time: 7/16/2016 2:01:52 PM
 STARTING Disk Agent for usncvbku01.us.oup.com:/CONFIGURATION "usncvbku01.us.oup.com [/CONFIGURATION]".

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:01:52 PM
 STARTING Disk Agent for usncvbku01.us.oup.com:/C "usncvbku01.us.oup.com [/C]".

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 2:01:53 PM
 STARTING Disk Agent for usncvbku01.us.oup.com:/D "usncvbku01.us.oup.com [/D]".

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 2:02:32 PM
 VSS Writer 'System Writer':Component 'System Files' successfully added in the snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 2:02:32 PM
 VSS option was specified. Attempting to create snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 2:02:54 PM
 Clearing archive flags is not applicable with Volume Shadow Copy backup.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:06 PM
 VSS Writer 'System Writer':Component 'System Files' successfully added in the snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:06 PM
 VSS Writer 'ASR Writer':Component 'BCD' successfully added in the snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:06 PM
 VSS Writer 'Registry Writer':Component 'Registry' successfully added in the snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:06 PM
 VSS Writer 'COM+ REGDB Writer':Component 'COM+ REGDB' successfully added in the snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:06 PM
 VSS Writer 'WMI Writer':Component 'WMI' successfully added in the snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:06 PM
 VSS option was specified. Attempting to create snapshot.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:03:32 PM
 Clearing archive flags is not applicable with Volume Shadow Copy backup.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/CONFIGURATION]"  Time: 7/16/2016 2:03:55 PM
 Successfully collected system recovery data.

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/CONFIGURATION]"  Time: 7/16/2016 2:03:55 PM
 Collecting Automatic DR data. This may take a few minutes...

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/CONFIGURATION]"  Time: 7/16/2016 2:03:57 PM
 Backup Profile:

  Run Time ........... 0:01:35
  Backup Speed ....... 20.11 MB/s

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/CONFIGURATION]"  Time: 7/16/2016 2:03:57 PM
 Filesystem Statistics:

  Directories ........      2832
  Regular files ......      4471
  ------------------------------
  Objects Total ......      7303
  Total Size .........   1.87 GB

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/CONFIGURATION]"  Time: 7/16/2016 2:03:58 PM
 COMPLETED Disk Agent for usncvbku01.us.oup.com:/CONFIGURATION "usncvbku01.us.oup.com [/CONFIGURATION]".

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:18:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:18:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:18:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:18:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:21:46 PM
 Backup Profile:

  Run Time ........... 0:17:41
  Backup Speed ....... 19.90 MB/s

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:21:46 PM
 Filesystem Statistics:

  Directories ........     17136
  Regular files ......     90593
  ------------------------------
  Objects Total ......    107729
  Total Size .........  20.61 GB

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/C]"  Time: 7/16/2016 2:21:48 PM
 COMPLETED Disk Agent for usncvbku01.us.oup.com:/C "usncvbku01.us.oup.com [/C]".

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:35:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:35:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:35:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:35:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:52:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:52:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:52:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 2:52:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:09:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:09:08 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:09:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:09:50 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:26:37 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:26:37 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:27:19 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:27:19 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:43:37 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:43:37 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:44:19 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host Unknown.
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Major] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:44:19 PM
[61:3003]   Lost connection to Unknown named "noname"
 on host .
 Ipc subsystem reports: "IPC Invalid Packet Size"

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 3:51:17 PM
 Backup Profile:

  Run Time ........... 1:48:18
  Backup Speed ....... 37.58 MB/s

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 3:51:17 PM
 Filesystem Statistics:

  Directories ........       868
  Regular files ......     10444
  ------------------------------
  Objects Total ......     11312
  Total Size ......... 238.50 GB

[Normal] From: VBDA@usncvbku01.us.oup.com "usncvbku01.us.oup.com [/D]"  Time: 7/16/2016 3:51:18 PM
 COMPLETED Disk Agent for usncvbku01.us.oup.com:/D "usncvbku01.us.oup.com [/D]".

[Normal] From: BMA@uscarbku01.us.oup.com "HP:Ultrium 5-SCSI_1_usbku01"  Time: 7/16/2016 3:51:58 PM
 Tape0:0:4:0C
 Medium header verification completed, 0 errors found.

[Normal] From: BMA@uscarbku01.us.oup.com "HP:Ultrium 5-SCSI_1_usbku01"  Time: 7/16/2016 3:52:18 PM
 Ejecting medium '4'.

[Normal] From: BMA@uscarbku01.us.oup.com "HP:Ultrium 5-SCSI_1_usbku01"  Time: 7/16/2016 3:52:18 PM
 => UMA@uscarbku01.us.oup.com@Changer0:0:4:1
 Unloading medium to slot 4 from device Tape0:0:4:0C

[Normal] From: BMA@uscarbku01.us.oup.com "HP:Ultrium 5-SCSI_1_usbku01"  Time: 7/16/2016 3:52:49 PM
 COMPLETED Media Agent "HP:Ultrium 5-SCSI_1_usbku01"

[Normal] From: BSM@uscarbku01.us.oup.com "Cary File Systems - Weekly_Full_Part2_C"  Time: 7/16/2016 3:52:50 PM

 Backup Statistics:
         
  Session Queuing Time (hours)         0.00       
  -------------------------------------------     
  Completed Disk Agents ........          3         
  Failed Disk Agents ...........          0         
  Aborted Disk Agents ..........          0         
  -------------------------------------------     
  Disk Agents Total  ...........          3         
  ===========================================     
  Completed Media Agents .......          1         
  Failed Media Agents ..........          0         
  Aborted Media Agents .........          0         
  -------------------------------------------     
  Media Agents Total  ..........          1         
  ===========================================     
  Mbytes Total .................  267687 MB       
  Used Media Total .............          1         
  Disk Agent Errors Total ......          0   

Hi

i would like to add the new VM's to  exisitng data protector9.0.  which is running on Hyper-v Platform. can i know the steps to import or add client in DP for Hyper-v 

currently my old VM are already configured and running in DP9.  

Thank you 

Hi PSPKR,

seems the BMA process on the uscarbku01.us.oup.com crashs. You can try to restart the system and retry the backup with the same or a different drive. If it fails you should upgrade to the latest Data Protector patches and contact support if the issue persists.

Regards,
Sebastian Koehler

If you're already doing HyperV backups the only thing required would be to edit the existing backup spec and include the new VMs. If this is a new setup you need to deploy the VEPA integration to a Windows client (this is your data mover, backup host) and import the HyperV host(s) using Import Client, Type HyperV to the cell. Please refer to the Integration.pdf in the Docs folder for full details.

HyperV backups require one Windows/Linux Online Integration license per HyperV host.

Regards,
Sebastian Koehler

 Hi

Thanks for your post,  yes i do have exsisting VM backup configured once i edit any backup i can see the new VMS showing in the cluster, so in this case do i need to do COPY AS to an exisiting backup and select the VM which i need to take backup.

Note : i have installed Disk Agent, VSS, VEagent to client VM.

thank you 

This depends on the backup requirements for the new VMs. In case they should be backed up similar to the existing ones you should tick the new VMs in the existing backup spec and hit apply. Also creating a new backup spec (using copy as or create new) is possible if you have different backup requirements for the new VMs.

Regards,
Sebastian Koehler

Do you have any idea ? =(

Hi Sebastian,

only for sure - if I choose 1 VTL and 1 LTO jukebox (physical tapes) in Backup spec - Destination, I supposse it will be the same situation as I wrote about it in previous post (in case of 3 VTLs) - I mean if available space will be 0 on the VTL,  HP DP will send request for mounting and won't use LTO jukebox (physical tapes). Am i right?

Thank you very much