Create a Bootable Windows PE RAM Disk on CD-ROM (Mini OS CD) - Walkthrough

This walkthrough describes how you can create a bootable Windows® PE RAM disk on CD or DVD. Windows PE RAM enables you to start a computer for the purposes of deployment and recovery. Windows PE RAM boots directly into memory, enabling you to remove the Windows PE media after the computer boots.

Step 1: Set up a Windows PE build environment

In this step, you create a required directory structure that supports building a Windows PE image.

To set up a build environment

1. On your technician computer, click Start, point to All Programs, point to Windows OPK or Windows AIK, right-click Deployment Tools Command Prompt, and then select Run as administrator.
   The menu shortcut opens a Command Prompt window and automatically sets environment variables to point to all the necessary tools. By default, all tools are installed at C:\Program Files\<version>\Tools, where <version> can be Windows OPK or Windows AIK.
2. At the command prompt, run the Copype.cmd script.
   The script requires two arguments: hardware architecture and destination location. For example,
   copype.cmd <architecture> <destination>
   where <architecture> can be x86, amd64, or ia64, and <destination> is a path to a local directory. For example,
   copype.cmd x86 C:\winpe_x86
   The script creates the following directory structure and copies all the necessary files for that architecture. For example,
   \winpe_x86
   \winpe_x86\ISO
   \winpe_x86\mount
3. Copy the base image (Winpe.wim) to the \Winpe_x86\ISO\sources folder and rename the file to Boot.wim.
   copy C:\winpe_x86\winpe.wim C:\winpe_x86\ISO\sources\boot.wim
   
   

Step 2: Add additional customizations

This step is optional, but recommended. Using ImageX, you can add applications and scripts to your Windows PE image that you might need while working in Windows PE. ImageX is a tool for capturing and applying images during deployment scenarios.

To add an application or script

• At a command prompt, enter the following ImageX command:
  copy "C:\program files\<version>\Tools\<architecture>\imagex.exe" C:\winpe_x86\ISO\
  
  

  where <version> can be Windows OPK or Windows AIK, and <architecture> can be x86, amd64, or ia64. In both of the previous examples, the tools are not loaded into memory during a Windows PE RAM boot. The media must be available to access the tools.

Step 3: Create a bootable CD or DVD

To create a bootable CD, you must use CD-recording software that unpacks the .iso file and burns it to a CD. Merely copying the .iso file to the CD will not work.

Note: The Oscdimg tool is not supported on an Itanium-based computer running Windows Server 2003.

To create a CD or DVD

1. On your technician computer, enter the following command to create an image (.iso) file for a BIOS-based computer. For example:
   Oscdimg -n -bC:\winpe_x86\Etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpex86.iso
   
   

   where C:\winpe_x86\ISO is the location of the source files, and C:\winpe_x86\winpex86.iso is the destination .iso file.
   -or-
   For UEFI, replace Etfsboot.com with Efisys.bin, specify the EF platform ID, and add the following Universal Disk Format (UDF) options. For example:
   Oscdimg -bC:\winpe_x86\Efisys.bin -pEF -u2 -udfver102 C:\winpe_x86\ISO C:\winpe_x86\winpex86uefi.iso
   
   

   -or-
   For either BIOS or UEFI, enter the following command. For example:
   Oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bC:\winpe_x86\Etfsboot.com#pEF,e,bC:\winpe_x86\Efisys.bin C:\winpe_x86\ISO C:\winpe_x86\winpex86uefi.iso
   
   

   where this command starts the Etfsboot.com boot file for a BIOS image, and then starts the Efisys.bin boot file for a UEFI image.
2. Burn the image onto a CD or DVD.

Next Step

You can also place Windows PE RAM on other bootable media, such as a USB flash drive or hard disk.

Source

PART3 - INTERVIEW QUESTIONS OF - HP DATA PROTECTOR

PART3 - INTERVIEW QUESTIONS OF - HP DATA PROTECTOR

HP Data Protector - Frequently asked Questions. Find some below most repeted interview questions as a starter of HP Data protector Interview Questions Sets. This will be a Set 1 as we add more pages with many more Interview questions as soon as possible,

Check Here for more upcoming Interview Questions on - HP Data protector X.X

Find the Answers below for each question at the end of this page.

---

Question: 1 To use the same device with different media pools, what must be created?

A. a new media agent 

B. media rotation policies 

C. a media specification 

D. backup specification

---

Question: 2 Which input parameters are common for all Data Protector notifications? Select THREE.

A. Name 
B. Session ID 
C. Device 
D. Message Level 
E. Trap number 
F. Send Method

---

Question: 3 What is the full path to the Data Protector Web reporting Java applet on a UNIX Client?

A. /opt/omni/java/sbin/WbReporting.html 
B. /opt/omni/java/bin/WebReporting.html 
C. /etc/opt/omni/java/sbin/WebReporting.html 
D. /opt/omni/bin/java/WebReporting.htm

---

Question: 4 Data Protector provides an event driven notification system. Which notification methods are available? Select TWO.

A. filter 
B. paging 
C. store to database 
D. broadcast 
E. email

---

Question: 5 What should you verify if the command "omnidbutil -merge mmdb CellServer3" fails?

A. that you have run the "omnidbutil -merge mmdb" command on CellServer3 
B. that you have configured centralized licensing before you merge 
C. that you have exclusive access to the database on CellServer3 
D. that no other cell can communicate with the MoM cell server

---

Question: 6 

Which Data Protector GUI context allows the supervision and administration of currently running backup and restore sessions?

A. Notify 
B. Reporting 
C. View 
D. Monitor

---

Question: 7 What is the minimum number of obsolete filenames that must exist on a Data Protector client to initiate purging from the internal database?

A. 500,000 
B. 200,000 
C. 1,000,000 
D. 100,000

---

Question: 8 When using the Restore from Media option, which configuration guideline should you consider regarding the required memory?

A. number_of_files multiplied by 200 bytes 
B. number_of_files multiplied by 100 bytes 
C. number_of_directories multiplied by 200 bytes 
D. number_of_directories multiplied by 100 bytes

---

Question: 9 What can Data Protector use to generate the media label during media initialization?

A. media type 
B. serial number of the drive used for initialization 
C. barcode label of the media 
D. unique number issued by the internal database

---

Question: 10 What are the advantages of split-mirror backups when instant recovery is enabled compared to standard backups? Select THREE.

A. minimal impact on applications during backup 
B. tapeless backup capability 
C. more efficient restore from a session 
D. serverless backup 
E. higher space efficiency due to using block level maps

---

Say special thanks to Dealdimer.com

Find the Answers :

Question 1: Answer: D
Question 2: Answer: A, D, F
Question 3: Answer: B
Question 4: Answer: D, E
Question 5: Answer: C
Question 6: Answer: D
Question 7: Answer: C
Question 8: Answer: A
Question 9: Answer: C
Question 10: Answer: A, B, C

Check Here for more upcoming Interview Questions on - HP Data protector X.X

PART2 - INTERVIEW QUESTIONS OF - HP DATA PROTECTOR

HP Data Protector - Frequently asked Questions. Find some below most repeted interview questions as a starter of HP Data protector Interview Questions Sets. This will be a Set 1 as we add more pages with many more Interview questions as soon as possible,

Check Here for more upcoming Interview Questions on - HP Data protector X.X

Find the Answers below for each question at the end of this page.

---

Question: 1 Which Data Protector daemons must be up and running on a HP-UX Cell Manager? Select THREE.

A. Cell Request Server service (CRS) 
B. Media Management Daemon 
C. Solid Database Server (SDS) 
D. Host Agent service (HA) 
E. Raima Database Server (RDS) 

---

Question: 2 Which inode time is used to detect files for incremental backups?

A. de fragmentation time 
B. access time 
C. creation time 
D. modification time 

---

Question: 3 Which command starts a backup from the command line?

A. omnibck 
B. omnicellbck 
C. omnib 
D. omnimm 

---

Question: 4 Which Disaster Recovery (DR) option is supported on an HP-UX Cell Manager?

A. Disk Delivery (DD) 
B. Enhanced Automated Recovery (EAR) 
C. Manual DR 
D. Assisted Manual DR 
E. One Button Disaster Recovery (OBDR) 

---

Question: 5 Which action is performed when you recycle a media?

A. reset of the media condition factors to zero 
B. state change of the media condition from poor to fair 
C. reinintialization of the media to store new backups 
D. data protection removal from all backed up data 

---

Question: 6
Your backup strategy runs one full backup per week as well as numerous incremental backups. Between the full backup and latest incremental backup, several files in a given directory have been deleted. When using the GUI to restore this directory, which option allows you to skip these files and only restore to the most recent point in time?

A. restore sparse files 
B. move busy files 
C. omit un required incremental 
D. omit deleted files 

---

Question: 7 What happens if the backup chain is broken and you start a restore?

A. The restore aborts. 
B. A warning message displays. 
C. Only the full backup is restored. 
D. It is not possible to browse the restore GUI. 

---

Question: 8 Which restriction applies to One Button Disaster Recovery (OBDR)?

A. only supported for Linux on Integrity systems 
B. currently not supported on Windows clusters 
C. only supported for HP-UX on Integrity systems 
D. currently not supported on UNIX systems 

---

Question: 9 
After installation, which Data Protector components must be installed manually regardless of the Cell Manager platform? Select TWO.

A. NetWare Agents 
B. Windows 2000 Agents 
C. Solaris Agents 
D. Application Agents 
E. Installation Servers

---

Question: 10 What is required to perform backups on unsupported UNIX platforms? 

A. CIFS 
B. NFS 
C. FTP 
D. DFS 

---

Say special thanks to Dealdimer.com

Find the Answers :

Question 1: Answer: A, B, E
Question 2: Answer: D
Question 3: Answer: C

Question 4: Answer: C

Question 5: Answer: D

Question 6: Answer: D

Question 7: Answer: B

Question 8: Answer: D

Question 9: Answer: A, E

Question 10: Answer: B

Check Here for more upcoming Interview Questions on - HP Data protector X.X

HP Data Protector - [61:12500] cannot connect to inet for getting file system list on host

Sample Error Log :

[Critical] From: BSM@cellsrv01.in.com "backup_spec_01” Time: 8/16/2014
[61:12500] cannot connect to inet for getting file system list on host" winclnt01.in.com".

Reason may Caused by:

Host may be down or Data protector client services (Inet) down.

Resolution :

Troubleshooting steps for Windows clients are as follows:

1. Check if the client (i.e. winclnt01.in.com in above error) is pinging from the cell manager, if not check the issue with platform team.

2. If the server is pinging, telnet the client using port 5555 

#Telnet <Client name> 5555(eg: #telnet 5555 cellsrv01.in.com)

3. If the telnet failed, login to the windows client and check whether “Data protector Inet” service is running or not. If not start the “Data Protector Inet” service, Just by right clicking the service and restart it.

4. If the Data protector service is not listed in the “services.msc”, the DP agent might be removed from the client. Push the DP agents on this client from cell server.

5. If the telnet failed using port 5555 even data protector service running, check with platform team to open the port.

Troubleshooting steps for UNIX clients are as follows:

1. Follow the steps 1 and 2 as explained above.

2. If the telnet failed, login to the UNIX client and check for the Omni entries in /etc/services and /etc/inetd.conf using the commands below. If not found, DP client needs to be reinstalled.

[root@unxclnt01:/root]

# egrep omni /etc/services

omni 5555/tcp # DATA-PROTECTOR

[root@unxclnt01:/root]

# egrep omni /etc/inetd.conf

omni stream tcp nowait root /opt/omni/lbin/inet inet -log /var/opt/omni//log/inet.log

3. Check if the port 5555 is listening using the command below. If not, raise a request to platform team to enable the port and start the inetd daemon.

[root@unxclnt01:/root] # netstat -an | grep 5555

tcp 0 0 *.5555 *.* LISTEN

4. Check if the ‘inetd’ daemon is running, if not start it using the below commands:

[root@unxclnt01:/root] # ps -ef | grep inetd

root 2144 1 0 Aug 10 ? 7:20 /usr/sbin/inetd

# /etc/inetd –s

Follow above steps to Solve iNet issue easily .. Good Day..:)

HP Data Protector - TSM Insufficient system resources exist to complete the requested service

Sample Error Log :

ANS9999E ntrc.cpp(928): Received Win32 RC 1450 (0x000005aa) from FileRead(): ReadFile '\\xxxx\. Error description: Insufficient system resources exist to complete the requested service.

Solution:

>> Edit the dsm.opt file by adding the param "MEMORYEFFICIENTBACKUP YES".

>> Save it.

>> Try a manual backup and check if the backup completes.

If not, this error needs attention from platform end.

>> Windows OS has the paging file space memory that needs attention.

>> Issue can be resolved by adding/modifying "PoolUsageMaximum & PagedPoolSize" in registry

For more info, please refer the article from microsoft.

http://support.microsoft.com/kb/304101

Your backup should be successful, once this is fixed.

Hp Data Protector - [81:52] Not a valid mount point => aborting [Solved]

Sample Error Log :

[Critical] From: VBDA@winsrv01 "winsrv01 [/F]" Time: 5/26/2014 9:28:58 AM
[81:52] /F
Not a valid mount point => aborting.

An attempt to backup the specific drive (F:/ in this example) connected to the DP client machine was failed and no data will be backed up by DP.

Solution :

In Windows :

Login to the windows client machine and check if the drive is accessible.

Check if the drive is local drive or zoned drive and the zoning still exists.

In case the zoned drive no more exists, you can exclude it in the backup spec.

If the drive exists on the server and it is accessible, try deleting files under the \tmp folder on the windows client machine and rerun the backup.

Default path to tmp folder for windows 2003/NT/XP:

C:\Program Files\OmniBack\tmp

Default path to tmp for windows 2008:

"C:\ProgramData\Omniback\tmp"

Zero KB Archive backup from a Specified Linux [Resolved]

Archive backup of all the databases from a specific linux server was completing successfully with 0 bytes of data backed up.

Example Error Log :

[Normal] From: BSM@cellsrv01.in.com "dbclient01_DB01_AR" Time: 03/03/14 07:15:23

Backup session 2014/03/03-86 started.

[Normal] From: BSM@cellsrv01.in.com "dbclient01_DB01_AR" Time: 03/03/14 07:23:36

OB2BAR application on "dbclient01.in.com" successfully started.

[Normal] From: BSM@cellsrv01.in.com "dbclient01_DB01_AR" Time: 03/03/14 07:23:36

OB2BAR application on "dbclient01.in.com" disconnected.

[Normal] From: BSM@cellsrv01.in.com "dbclient01_DB01_AR" Time: 03/03/14 07:23:37

Backup Statistics:

Session Queuing Time (hours) 0.00

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

Completed Disk Agents ........ 0

Failed Disk Agents ........... 0

Aborted Disk Agents .......... 0

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

Disk Agents Total ........... 0

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

Completed Media Agents ....... 0

Failed Media Agents .......... 0

Aborted Media Agents ......... 0

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

Media Agents Total .......... 0

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

Mbytes Total ................. 0 MB

Used Media Total ............. 0

Disk Agent Errors Total ...... 0

What was causing this??

Is there any transactions happening in these DBs or not??

Any patching on server or DB that prevents the data transfer??

Why DP doesn't err anything??

No idea until we checked the seaudit log. The inet service was restarted from an local admin account, from then onwards the DP processes were lacking the root access rights which prevented from reading the data.

05 Mar 2014 04:47:42 D SURROGATE useradm1 Read 69 2 USER.oradba /opt/omni/lbin/inet 198.10.10.2 root

Solution:

Once again the inet daemon was restarted from root.

Commands to restart the DP inet service from Linux client:

#/etc/init.d/omni stop

#/etc/init.d/omni start